# Getting Started

Webhooks allow your applications to receive information when customer events occur - such as submitting a product review, completing a survey, or earning loyalty points. This enables seamless integration with your existing tools - whether you want to track reviews in your CRM, send data to custom analytics platforms or trigger custom workflows. This documentation will detail how to configure and test webhooks for Okendo.

### Setting Up Webhooks

You can configure webhooks using the [Okendo Merchant REST API](https://docs.okendo.io/merchant-rest-api/endpoints#webhooks). Follow the API documentation to create a webhook subscription.

**Important Notes:**

* **Webhook Ordering:** Delivery order is not guaranteed. However, each webhook includes a `sequenceNumber` that can be used to order events for the same resource type.
* **Response Requirements:** Your server must respond with an HTTP `2xx` status code (e.g., `200 OK`) within 15 seconds of receiving a webhook event.
  * Best practice is to immediately acknowledge receipt and delegate processing to an asynchronous task or queue.

### Verifying Webhooks

For security purposes, we strongly recommend verifying the webhook signature to ensure that the payloads are coming from Okendo and not a malicious third party.

Refer to [this guide](https://www.svix.com/guides/receiving/receive-webhooks-with-svix-cli/) for an example of how to verify webhook signatures using the Svix CLI.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.okendo.io/webhooks/getting-started.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.