Webhook Endpoint Reference

Every endpoint that manages an outbound webhook subscription, and what each one does. Reach for this page when you know what you want to do and need the call; the flow that uses them — subscribing, verifying signatures, testing, rotating, replaying — is in Webhooks & Event Delivery.

Subscription endpoints

Endpoint	Effect
POST /webhooks	Create (returns secret once).
GET /webhooks	List subscriptions in your organisation.
GET /webhooks/{id}	Read one (does not return secret — only last four characters).
PATCH /webhooks/{id}	Merge-patch update (URL, events, filters, custom headers, retry policy).
PUT /webhooks/{id}	Replace (preserves secret).
DELETE /webhooks/{id}	Soft-delete.
POST /webhooks/{id}/enable	Set status to ACTIVE.
POST /webhooks/{id}/disable	Set status to DISABLED.
POST /webhooks/{id}/rotate	Issue a new signing secret.
POST /webhooks/{id}/ping	Fire a synthetic webhook.test event.
GET /webhooks/{id}/deliveries	Delivery history.
POST /webhooks/{id}/redrive	Replay failed deliveries.
GET /webhooks/events	Live event catalogue.

Replay lives on the recruitment-check resource rather than the webhook, because it re-emits an event rather than re-sending a delivery:

Endpoint	Effect
POST /recruitment-checks/{id}/replay-completion	Re-emit one completion event. Writes nothing.
POST /recruitment-checks/replay-completions	The same for an explicit list of ids. Dry run by default.

Every endpoint requires a Bearer token authorized for the webhook entity — see Authentication & Tokens.

Where to go next

• Webhooks & Event Delivery — the end-to-end setup flow these endpoints serve
• Webhook Payload Reference — the delivery envelope and every event type's data body
• Recovering a Broken Webhook Endpoint — the six-step runbook for after an outage
• API Reference — every field and query parameter