Rotate the signing secret

POST 
/v1/projects/:project_id/webhooks/:webhook_id:rotate-secret

Issues a new signing secret for the same endpoint and returns it — the second and last time a secret is ever returned. This is the …:rotate-secret action; the path segment is {webhook_id}:rotate-secret. The change takes effect on the next delivery, including retries of deliveries already queued, so roll the new secret out to your receiver promptly. There is no overlap window in which both secrets verify.

Request

Responses

200

A new signing secret was issued.

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.