#utkarsh-upadhyay_api

1 messages · Page 1 of 1 (latest)

worn wharfBOT
#

đź‘‹ 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/1288518760084537434

đź“ť Have more to share? Add more details, code, screenshots, videos, etc. below.

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

blazing latch
#

Hello, that does not exist for the billing portal as there isn't really a success state or a cancel action for it. Can you tell me more about what you are trying to do here?

glossy vortex
#

I have created specific portal configurations where a user can click a button on my website to add a seat and I take them directly to

      type: "subscription_update"
}```
#

And now I want to know if they went through it or not somehow from the portal session

#

Even if I could attach some kind of metadata to that session somehow

#

I could fetch that on the return url page on my website

#

to confirm if they went through with the upgrade or not

blazing latch
#

Gotcha, unfortunately there isn't a way to have the customer portal save metadata like that. I think what you will need to do is cache info about these subscriptions on your side and then retrieve the customer's subscriptions when they get to your return URL to check if anything has changed (while also listening to customer.subscription.updated events for redundancy).

worn wharfBOT
glossy vortex
#

For how long should I be polling this to check if there was any change?

eager onyx
#

Hello! I'm taking over and catching up...

#

You shouldn't need to poll at all. When your customer hits the return_url fetch their Subscription(s) from the API and check for any changes. You can also list recent customer.subscription.updated Events if you want the detail in those (like the previous attributes). None of that would require polling though.

glossy vortex
#

So, the change happens instantaneously, and if it doesn’t change then that means there was no update initiated from customer’s side