#bill92_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/1305739694809681923
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
hello! idempotency keys are meant for API requests made to Stripe. For webhook events, you should use the event id like what our doc mentions
I'm not too sure I understand, are you referring to idempotency keys?
the event id [https://docs.stripe.com/webhooks#handle-duplicate-events], I will store it on a memory store and before processing, I will make sure that it doesn't exist, So I want to set an expiration on these keys
i think 24 hours should be more than sufficient. However, maybe a different question here is what do you really need to do with the event data? If you just want to ensure your DB has the latest information of the object, you can make a request to retrieve the object upon receipt of the event. In this case, you wouldn't even need to store the event id anyway
for this case, I'm keeping track of the trial_will_end event, so I would not want to send more than one email, It might be confusing to the end user
ah i see, but logically you can update in your own DB if you've already sent the email right?
hmm not sure I'm following..
emails will be automatically sent when the trial_will_end is triggered via a webhook, I just want to make sure its sent once