#devz_event-types
1 messages ¡ Page 1 of 1 (latest)
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.
- devz_best-practices, 1 hour ago, 31 messages
- devz_error, 4 days ago, 97 messages
đ Welcome to your new thread!
â˛ď¸ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).
âąď¸ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can 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/1254774725830508606
đ Have more to share? Add details, code, screenshots, videos, etc. below.
hi! generally you create one endpoint that listens to multiple event types and your code handles them all.
Okay
So i can create just one webhook with all 300 events
And managed them in my code
?
Is it possible ?
yep
Okay got it
Thanks
So i think its better to separate webhooks in groups
Depending on the action
What are the best practices ?
it's up to you. Overall why would you want to use all 300 event types?
usually you pick the subset of events that are relevant to what your integration actually uses, and listen to/handle them. E.g. if you never use our Subscriptions API you don't need the events related to that like customer.subscription.updated, and so on.