#ali_api
1 messages ยท Page 1 of 1 (latest)
๐ Welcome to your new thread!
โฒ๏ธ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
โฑ๏ธ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
๐ This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1400160371112677396
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
Looking at the call, it appears you're attempting to update the subscription?
Also, can you provide Request IDs for the failures?
coupon is still valid btw.
That's right! I am attempting to update a subscription. Let me find the request IDs.
Nice, it's good that coupon is still valid.
๐ Just taking over for my colleague, getting caught up on the conversation.
Do you have an account id I can use to look up those errors? Or an example request id. I don't see any active incidents that would suggest there was an issue at that moment but sometimes that information trickles in later.
I am trying to find the request ids. Those calls were made to our Stripe dev env.
If you have an account id I can help look ๐
Here is the dev environment accoutn id:
acct_1GIGBBDAWTp2PXOw
Sorry, wrong account number. We have a seperate instance for our tests
Correct account number:
acct_1Dsy3yBEIZKO4QrA
Request IDs:
req_YUqAUjxBjNgm49
req_MJBN3rP7dKKf8C
req_cmNS4oxD5RhYzH
Hrm, do you have an example of this test passing?
Yep, I'll send that shortly.
Here is a request in acct_1GIGBBDAWTp2PXOw
req_VtOVWWyQaSOutM
Here is another example in acct_1Dsy3yBEIZKO4QrA
req_6JhFNlKa1Tasm1
Hi there ๐ apologies for the delay, I'm jumping in as my teammate needed to step away.
Thanks for those examples of requests that succeeded vs those that returned an error. I'm taking a closer look through them.
coupon is being deprecated, and support for it is beginning to be removed from endpoints. It would be a decent time to consider making the move to using discount instead.
And I can confirm that the behavior you're referring to, where we began throwing an error when you passed an empty string to the coupon parameter, was a bug on our end and that behavior was adjusted shortly after we became aware of it.
Thanks Toby, we started replacing coupon with discount in our most recent developments. I will modify my current test to use discount as well. I was mainly interested to see what is going on. Thanks for the confirmation.
Any time! Glad I could help provide that