# Webhooks
URL: https://docs.awellhealth.com/api-reference/guides/webhooks

> For the complete documentation index, see [llms.txt](https://docs.awellhealth.com/llms.txt).



A care flow can call out to your systems as it runs, for example to notify you when an
activity completes. Awell records each of these as a **webhook call** you can inspect and retry
through the API.

## Inspecting and retrying webhook calls [#inspecting-and-retrying-webhook-calls]

The API exposes webhook calls as data you can query and act on:

* Query them with `webhookCall`, `webhookCalls`, and related operations. See
  [API calls & webhooks](/api-reference/reference/api-calls-and-webhooks).
* Retry failed deliveries with `retryWebhookCall` and the bulk `retryAll…` mutations.
* Subscribe to `webhookCallCreated` and `webhookCallUpdated` for real-time updates. See
  [Subscriptions](/api-reference/reference/subscriptions).

## Receiving and verifying webhooks [#receiving-and-verifying-webhooks]

Configuring, receiving and verifying are covered in full elsewhere on this site rather than repeated
here — this page is about the webhook calls the API exposes as data.

| To do this                                               | Go to                                                                                                     |
| -------------------------------------------------------- | --------------------------------------------------------------------------------------------------------- |
| Build the endpoint, verify the signature, handle repeats | [Receive webhook events](/docs/automate-with-events/receive-webhook-events)                               |
| See what each event reports, and what it does not        | [Webhook event catalog](/docs/automate-with-events/webhook-event-catalog)                                 |
| See the shape of what arrives                            | [Webhook payloads](/api-reference/guides/webhook-payloads)                                                |
| Turn webhooks on for one care flow                       | [Configure webhooks in Studio](/docs/automate-with-events/configure-webhooks-in-studio)                   |
| Turn them on for every published care flow at once       | [Configure webhooks for all care flows](/docs/automate-with-events/configure-webhooks-for-all-care-flows) |

Before you build the receiving end: payloads carry **identifiers, not clinical detail**, so you fetch
what you need through the API using them. Delivery also repeats and can arrive out of order, so the
endpoint has to be idempotent.

## Related [#related]

* [API calls & webhooks reference](/api-reference/reference/api-calls-and-webhooks)
* [Subscriptions reference](/api-reference/reference/subscriptions)