Skip to main content
WEBHOOK

Authorizations

X-Hook0-Signature
string
header
required

HMAC-SHA256 signature of the raw request body, computed using your webhook secret. Webhook receivers should always verify this header before processing the event. The header value is hex-encoded and prefixed by the algorithm and timestamp, e.g. t=1700000000,v1=abc123... (refer to the Webhook Security docs for the exact verification algorithm).

This scheme applies to webhook delivery (outbound POSTs from CDP to your endpoint), not to inbound CDP API requests.

Body

application/json

The health.maintenance.completed webhook event payload.

Common fields included in every maintenance event payload.

eventId
string<uuid>
required

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.

Example:

"9d3f2b1a-6e4c-4a8b-9f1d-2c7a5e8b4f60"

timestamp
string<date-time>
required

The UTC ISO 8601 timestamp at which this event's transition occurred, not the time at which this webhook was delivered.

Example:

"2026-04-21T14:32:00.000Z"

eventType
enum<string>
required

The type of webhook event.

Available options:
health.maintenance.completed
Example:

"health.maintenance.completed"

data
object
required

Fired when a maintenance window ends normally. The affected service's or operation's effective health status is recomputed and returns to operational, unless an organic outage remains in progress, which continues to take priority.

Example:

Response

Webhook received and processed successfully.