#brian_webhooks
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/1404654986864099348
đ 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.
- brian_api, 6 hours ago, 8 messages
(I'm trying to anticipate race conditions for what I'm working on - if there are any guarantees it would make things a lot simpler for me)
If I understand you correct, yes each call of GET (either GET entitlements or GET subscriptions) should give you the latest state of the object in Stripe API. But if you ask about guarantee to not be changed in a few secs later, no it won't be guaranteed.
Talking purely from Stripe object perspective
One a webhook event came, the Stripe object available in Stripe API should have reflected that change. The tricky part is event is sent async, so event sent later can arrive first (depends on how the internet package works, if they are sent almost at the same time)
But normally, once webhook event came, any GET request made subsequently should have reflected that change (because the change is done on Stripe side, and is broadcasting to you)
Got it, so basically all Stripe webhook events that are sent (from a trigger, such as the subscription being updated), are sent at the same time?
Yep
awesome, thanks!