Ecwid webhooks are **automatic real-time notifications** for apps about different events in the store. Webhooks are always sent as **POST requests** from Ecwid API to your server when something happens in a store, allowing you to automate practically any business process.
To receive webhooks, you need a self-hosted endpoint working on your side called `webhookUrl`:
Webhooks must be delivered as quickly as possible, so they only carry essential data about the event, for example, event details, store and item ID, timestamp, etc.
When you receive a webhook from Ecwid API, you must send back a confirmation to stop Ecwid API from sending it again.
### See also
[How to process webhooks](/webhook-automations/setup-webhooks/how-to-process-webhooks.md)
[Event data in webhooks](/webhook-automations/learn-ecwid-webhooks/event-data-in-webhooks.md)
[List of webhook events](/webhook-automations/learn-ecwid-webhooks/list-of-webhook-events.md)
---
# 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.ecwid.com/webhook-automations/webhook-automations-overview.md?ask=
```
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.