Batches

Batch completed

Sent when a batch completes. Return any 2xx response to acknowledge delivery. Slack incoming webhook destinations receive a formatted Slack message instead of this event envelope.

postWebhookbatchCompleted

Headers

User-Agentstring required

Example:Context.dev-Webhooks/1.0

Identifies the Context.dev webhook sender.

X-Context-Event'batch.completed' required

Which final status the batch reached. Matches the event field in the request body.

X-Context-Idstring required

Example:evt_123

Unique event ID. Matches the top-level id field in the request body.

X-Context-Delivery-Idstring

Example:whd_0123456789abcdef0123456789abcdef

Delivery ID for status checks and retries.

X-Context-Attemptinteger

Attempt number, starting at 1.

X-Context-Signaturestring

Example:t=1783620012,v1=087d98aada1e39f9d24d65951f51e672da12b2f9ea1c02c7c8c5ef254f5d4068

t=<unix>,v1=<hmac>: SHA-256 HMAC of t.rawRequestBody, keyed with the webhook secret. Verify with a constant-time comparison and reject stale timestamps.

Payload

event'batch.completed' required

Which final status the batch reached. Mirrors the X-Context-Event header.

idstring required

Unique event ID. Mirrors the X-Context-Id header.

created_atstring date-time required

When the batch reached its final status.

Response

Webhook accepted.

Changes

Webhooks have no change history: a webhook is keyed by its event name rather than a path and method, so no recorded change can name it.