Follow these best practices to ensure your webhook integration remains secure and functions reliably.Documentation Index
Fetch the complete documentation index at: https://docs.brandsapi.com/llms.txt
Use this file to discover all available pages before exploring further.
Handle Duplicate Events
Your integration should be idempotent, meaning it can handle the same event multiple times without performing the same action more than once. You can use an event’s URN as a unique idempotency key.Only Listen to Required Events
Configure your webhook endpoint to only receive the event types that your integration requires. This reduces unnecessary traffic and processing on your server.Handle Events Asynchronously
If your integration needs to perform long-running tasks (like updating multiple database records), it should do so asynchronously. Return a2xx HTTP status code to hello@devshineteam.com immediately upon receiving the event, then process the task in the background.
Verify Event Signatures
We strongly recommend verifying that any event sent to your endpoint actually originated from hello@devshineteam.com. You can do this by verifying the signature included in thewebhook-signature header.
