#mattmiller_webhooks
ivory micaBOT
👋 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/1339323690294181991
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
uncut mortarBOT
shut raptor
Hi there 👋
The ID of the Event object itself is the right ID to check to make sure you aren't processing an Event you've already handled.
The verbiage in that second line is a bit weird. What I think it's advising about, is how a single action may result in multiple Events being generated and sent to you, and how you may not need all of those every time. For instance, paying an Invoice results in an invoice.paid Event, an invoice.payment_succeeded one, and a payment_intent.succeeded one. Depending on the Event types you're listening for, you may receive all of those but not always need to process all of them.
dry stump
Okay, great. Thanks for clearing that up.