> For the complete documentation index, see [llms.txt](https://help.openloyalty.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.openloyalty.io/technical-guide/webhooks/best-practices.md).
# Best Practices
Implement the following best practices for effective [webhook integration](https://help.openloyalty.io/webhooks):
* **Retry Mechanisms and Handling Failures:** Implement retry mechanisms to account for temporary issues, such as network errors or server downtime. Use exponential backoff and jitter to space out retry attempts and minimize the risk of overloading the receiving system.
* **Scalability and Performance:** Optimize webhook handling by using queuing systems (e.g., RabbitMQ or Apache Kafka) or background processing libraries (e.g., Celery for Python or Bull for Node.js) to process events asynchronously, ensuring high throughput and low latency.
* **Verification Tokens:** Use a shared secret (verification token) to validate incoming webhook requests, ensuring that they originate from the intended sender.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://help.openloyalty.io/technical-guide/webhooks/best-practices.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
