Create a webhook

POST 
/v1/projects/:project_id/webhooks

Register an endpoint and subscribe it to one or more event types. The response carries secret — the signing key, in plaintext. This is the only time it is returned. Store it where your receiver can read it; if you lose it, rotate rather than re-create, so the endpoint keeps its delivery history. Returns 501 on a deployment with no credential-sealing key configured, since the secret could not then be stored safely.

Request

Responses

201

Webhook created. The signing secret is included, once.

400

The request was malformed or failed validation.

401

Missing or invalid credentials.

404

The resource does not exist (existence is not leaked).

501

The requested path is not enabled on this deployment — a webhook secret cannot be stored where no credential-sealing key is configured.