# Webhook automations overview

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Quickstart with a code:</strong></td><td><a href="setup-webhooks/code-example-for-webhook-handling">code-example-for-webhook-handling</a></td></tr><tr><td><strong>Connect webhooks</strong></td><td><a href="setup-webhooks/set-up-webhooks-for-your-app">set-up-webhooks-for-your-app</a></td></tr></tbody></table>

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`:

<figure><img src="https://4030595190-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQ47kAA1WxNIuWGKG5OiB%2Fuploads%2FzFy0QcdsuHd37YTmbsi2%2Fwebhook_handling_flow.png?alt=media&#x26;token=711cb882-85bb-4cf2-ade7-8a8a7211e181" alt="" width="563"><figcaption></figcaption></figure>

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](https://docs.ecwid.com/webhook-automations/setup-webhooks/how-to-process-webhooks)

[Event data in webhooks](https://docs.ecwid.com/webhook-automations/learn-ecwid-webhooks/event-data-in-webhooks)

[List of webhook events](https://docs.ecwid.com/webhook-automations/learn-ecwid-webhooks/list-of-webhook-events)