Skip to main content
Use the webhooks API to programmatically manage your event endpoints. You can register multiple endpoints with different event subscriptions — for example, one endpoint for ATS sync and another for Slack notifications.

List Webhooks

Retrieve all webhook endpoints registered for your organization.
cURL
Response

Register a Webhook

Subscribe a new HTTPS endpoint to one or more event types.

Request Body

string
required
The HTTPS URL that will receive webhook events. The endpoint must be publicly accessible and respond to POST requests.
array of strings
required
List of event types to subscribe to. See the Webhook Events Reference for all valid values.
string
A custom signing secret used for HMAC-SHA256 signature verification. If omitted, Cutshort generates a secret automatically and returns it in the response.

Example Request

Response
Store the secret field immediately — it is only shown in full at creation time. You will need it to verify webhook signatures on every incoming request.

Delete a Webhook

Permanently remove a registered webhook endpoint. Cutshort will stop delivering events to it immediately.
cURL
Returns 204 No Content on success with an empty response body.

Verifying Signatures

Every webhook request Cutshort sends includes an X-Cutshort-Signature header:
To verify a request is genuine, compute the HMAC-SHA256 of the raw request body using your webhook secret, then compare it to the hash in the header. Always use a constant-time comparison to prevent timing attacks.

Retry Behavior

When a webhook delivery fails — either a non-2xx response or no response within 10 seconds — Cutshort retries the delivery up to 5 times on an exponential schedule:After 5 consecutive failures the endpoint is automatically disabled. To re-enable it, either use your Cutshort dashboard or send a PATCH request to /v1/webhooks/{id} with "status": "active".