Service health updated
Fires whenever the operational status of a CDP service or operation changes — an outage begins, its severity changes, or it recovers to operational. Subscribe to react to CDP disruptions in real time.
Authorizations
HMAC-SHA256 signature supplied on every webhook delivery. The signature is computed from the raw request body using the webhook secret supplied during creation of the webhook subscription.
Webhook receivers can cryptographically verify this header before processing the event to ensure the authenticity of the webhook delivery.
Refer to the verify signatures documentation to learn details about the full payload and the exact verification algorithm.
X-Hook0-Signature is deprecated and will eventually be removed. Use X-Webhook-Signature going forward. Both headers are sent with identical values and use the same verification algorithm and webhook secret.
This scheme applies to webhook delivery (outbound POSTs from CDP to your endpoint), not to inbound CDP API requests.
Headers
HMAC-SHA256 signature supplied on every webhook delivery. The signature is computed from the raw request body using the webhook secret supplied during creation of the webhook subscription.
Webhook receivers can cryptographically verify this header before processing the event to ensure the authenticity of the webhook delivery.
Refer to the verify signatures documentation to learn details about the full payload and the exact verification algorithm.
X-Hook0-Signature is deprecated and will eventually be removed. Use X-Webhook-Signature going forward. Both headers are sent with identical values and use the same verification algorithm and webhook secret.
This scheme applies to webhook delivery (outbound POSTs from CDP to your endpoint), not to inbound CDP API requests.
HMAC-SHA256 signature supplied on every webhook delivery. The signature is computed from the raw request body using the webhook secret supplied during creation of the webhook subscription.
Webhook receivers can cryptographically verify this header before processing the event to ensure the authenticity of the webhook delivery.
Refer to the verify signatures documentation to learn details about the full payload and the exact verification algorithm.
X-Hook0-Signature is deprecated and will eventually be removed. Use X-Webhook-Signature going forward. Both headers are sent with identical values and use the same verification algorithm and webhook secret.
This scheme applies to webhook delivery (outbound POSTs from CDP to your endpoint), not to inbound CDP API requests.
Body
The health.status.updated webhook event payload.
Unique identifier for this logical webhook event. Webhooks are delivered at least once, so your endpoint may receive duplicate deliveries for the same event. Use this eventId as the idempotency/deduplication key.
"9d3f2b1a-6e4c-4a8b-9f1d-2c7a5e8b4f60"
The UTC ISO 8601 timestamp at which this event's transition occurred, not the time at which this webhook was delivered.
"2026-04-21T14:32:00.000Z"
The type of webhook event.
health.status.updated "health.status.updated"
The health status of a service or operation. See HealthStatusValue for the severity ladder this moves along, and under_maintenance's special computed-status behavior.
Response
Webhook received and processed successfully.