Issue a new signing secret; the previous one keeps signing for 24 h
POST/v1/webhooks/:webhook_id:rotate_secret
At most two secrets are live. While the previous secret is still in its 24-hour overlap the call answers 409 secret_rotation_in_progress (details.previous_secret_expires_at), unless you send expire_previous_now: true: the older secret is then destroyed at once and the current one becomes the previous one (the way back after a lost rotation response). No Idempotency-Key replay: secrets are never stored in a replayable form.
Access: API key scope webhooks:write on a management key; portal users: organization admins and owners; refused for an API key limited to a list of knowledge bases (403 kb_not_in_allowlist).
Request
Responses
- 200
- 403
- 404
- 409
New secret (shown once).
scope_missing (details.required_scope), role_insufficient, kb_not_in_allowlist, integrations_disabled (details.area, details.scope), domain_blocked.
not_found — identical for missing resources and resources of another organization (details.resource).
webhook_limit, secret_rotation_in_progress, domain_exists, redelivery_unavailable, idempotency_key_conflict, idempotency_in_progress.