> For the complete documentation index, see [llms.txt](https://docs.ecwid.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ecwid.com/webhook-automations/setup-webhooks/set-up-webhooks-for-your-app.md).
# Set up webhooks for your app
Setting up webhooks requires you to add two settings to your Ecwid app:
* **List of webhook events**
* **Self-hosted `webhookUrl` endpoint**
{% hint style="info" %}
If you don't yet have an app for Ecwid API access, start with the following [instructions](https://app.gitbook.com/s/uOzT5egoVTAjMJwRuMQT/get-started/set-up-your-dev-environment-in-ecwid#step-2.-get-your-first-application).
{% endhint %}
Everything that happens in the store has its **webhook event**. The event describes the affected entity and action in the `entity.action` format.
For example, `order.created` webhooks notify about any new orders in the store:
* Placed by customers on the storefront.
* Created by the store owner through the mobile app.
* Synced through applications with REST API.
We recommend you avoid enabling all webhook events for your app. Check out available events and choose the ones you need. [List of webhook events](/webhook-automations/learn-ecwid-webhooks/list-of-webhook-events.md)
Your `webhookUrl` endpoint must work through HTTPS and must be able to receive POST requests and respond to them with HTTP `200 OK` status.
Once you have both the `webhookUrl` and a list of events, request an application update.
If you need additional authentication on your side, you can set up custom headers for your `webhookUrl`. Learn more about [custom headers](/webhook-automations/customize-webhooks/pass-additional-data-through-webhooks.md).
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.ecwid.com/webhook-automations/setup-webhooks/set-up-webhooks-for-your-app.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.