#navaneedhan_webhooks-entitlements
sonic orchidBOT
đ 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/1291102572588957719
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
storm finch
@simple arrow can you clarify which exact API you are talking about and what you would be changing?
Also the best approach would be to try it for a few minutes and see if multiple Events are emitted or not
navaneedhan_webhooks-entitlements
simple arrow
@storm finch surely, I will try it out.
But I don't find this relevant information in the documentation.
I am currently looking into the API: https://docs.stripe.com/api/product-feature/remove for removing features from one of my offering products.
storm finch
Yeah that's why trying it for a few minutes will answer this question and many more for you versus guessing. I agree our docs are a bit light on the Events that can be emitted
simple arrow
Thank you for your help @storm finch
storm finch
Sure!
simple arrow
@storm finch - out of this context, do you have any recommendation for caching the entitlements? So that we will evaluate that for our implementation?
storm finch
I don't really get what caching means or what's blocking you
By the way I just tried for your first question and no Event is sent in the case where you delete the ProductFeature itself. We assume you would track this yourself
simple arrow
By the way I just tried for your first question and no Event is sent in the case where you delete the ProductFeature itself. We assume you would track this yourself
yes.
We are implementing our product, in such a way that, we will maintain a local copy of this entitlements data. To update our local data, we were looking for the events, so that we will udpate our local data (that is what I called as caching).
We are following the recommendations by the docs: https://docs.stripe.com/billing/entitlements?dashboard-or-api=api#list-active-entitlements
Recommendation
We recommend you persist these entitlements internally for faster resolution.
storm finch
we emit the entitlements.active_entitlement_summary.updated Event for those and you can ingest that. I assumed you knew that already since you were explicitly asking whether an Event would be sent thousands of times (which I confirmed it wouldn't)
simple arrow
The event entitlements.active_entitlement_summary.updated triggers for the customer's subscriptions life cycle changes. We checked for the actions like "removal of feature from product" that impacts that customers - but those events are not triggered.
storm finch
correct, that's what I just explained right? In that case you are deleting the feature yourself so you would know you are doing this, there's no Event for that flow
simple arrow
got it