#yesmeno
half capeBOT
Hello! We'll be with you shortly. 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.
- yesmeno-price-api, 2 days ago, 6 messages
- yesmeno, 3 days ago, 22 messages
- yesmeno, 4 days ago, 12 messages
- yesmeno, 4 days ago, 18 messages
- yesmeno, 5 days ago, 14 messages
feral sedge
Hello
Yes customer.subscription.updated is reliable for this.
Ordering of webhooks is not guaranteed, so when you create a Subscription it is possible that you might receive the customer.subscription.updated Event prior to the customer.subscription.created
But yeah, if the status is active within customer.subscription.updated then you should provision
native hedge
Thanks @feral sedge ! I think it would help if this was added to the docs.
So I would need to check if the status is trialing, active or past_due to see if the subscription is active, right?
native hedge
The fact that customer.subscription.updated fires every time. It isn't clear to me (from the docs) that this event also fires when a subscription is created for example.
feral sedge
Yes those are the statuses you would want.
It doesn't fire when it is created
It fires when anything changes
Which oftentimes happens immediately upon creation -- that depends on your integration flow
native hedge
Ah ok... because I think I also didn't get an update event when the subscription was cancelled just now when testing this. Is this possible?