#ronny_webhooks
novel cargoBOT
đ 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/1347354807056466040
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
leaden sky
Hello! For those properties all you need to listen for is customer.subscription.updated. Our *.updated Events have a previous_attributes property that shows you the previous value, so you can see what changed to what easily.
warped badge
Ah, I see. Does this mean that an event like customer.subscription.deleted also triggers a customer.subscription.updated? If all I care about is this particular subset of properties from the Subscription object, then there's no need to listen for events that effectively provide redundant information?
leaden sky
Correct.
Give it a try in test mode and make sure it works as you expect and that it will be appropriate for your use case.
warped badge
Will do. Thanks!