Actuallycare Com Webhooks

generated: '2026-10-31'
method: searched
generator: extract-docs-artifacts.py (local)
source: https://docs.actuallycare.com/api/reference/webhooks.md
sources:
- https://docs.actuallycare.com/api/reference/webhooks.md
- https://docs.actuallycare.com/concepts/webhooks.md
- https://docs.actuallycare.com/guides/webhook-setup.md
- https://docs.actuallycare.com/api/reference/webhooks
description: ActuallyCare webhooks deliver JSON payloads via HTTPS POST. Each delivery includes three headers – `X-Webhook-Event`, `X-Webhook-Timestamp`
  and `X-Webhook-Signature` – and is signed with an HMAC‑SHA256 using the secret supplied when the webhook was created. Deliveries are retried
  up to three times (four attempts total) after 1, 5 and 15 minutes if the response is a network error or an HTTP 5xx, 408 or 429 status; other
  4xx responses are not retried.
events:
- event: escrow.created
  description: A new escrow is opened.
- event: escrow.updated
  description: An escrow's details change.
- event: lead.created
  description: A new lead enters the pipeline.
- event: lead.status_changed
  description: A lead's status changes.
- event: client.created
  description: A new client relationship is created.
- event: listing.updated
  description: A listing's details change.
- event: appointment.status_changed
  description: An appointment's status changes (including cancellations).
- event: care_status.changed
  description: A relationship's follow‑up health changes.
delivery:
  auth: 'JWT bearer token (Authorization: Bearer <token>)'
  signature: X-Webhook-Signature header containing `sha256=` followed by the hex‑encoded HMAC‑SHA256 of the raw JSON body using the webhook secret
  content_type: application/json
note: The `X-Webhook-Event` header contains the event name and the `X-Webhook-Timestamp` header mirrors the `timestamp` field in the payload;
  both are unchanged on retries.
docs: https://docs.actuallycare.com/api/reference/webhooks.md