Rotate a webhook signing secret
Rotate a webhook signing secret.
Credential: Partner secret
Before you call
- A server-side partner secret for the owning partner. Do not send an Origin header.
- An active integration that your partner credential permits.
- Set an Idempotency-Key and reuse it for an identical retry.
Rotate signing secret; keep at most two versions
overlapSeconds is 0 or 86400. During a 86400-second overlap, another overlapping rotation returns 409 ROTATION_IN_PROGRESS. With 0 the previous key stops immediately. A new secret is returned once; an idempotent repeat has secretReturned false.
Server-only partner credential access: a 403 means the integration is unauthorized or inactive. Mutations share 60/min per partner; test and replay allow 5/min each per endpoint, rotation 1/min per endpoint. Only committed changes count; identical idempotent replays within 24 hours do not. A 429 includes retryAfter. Conflict details.kind can include IDEMPOTENCY_CONFLICT, ENDPOINT_DELETED, ENDPOINT_LIMIT, REVISION_CONFLICT, VERIFICATION_REQUIRED, ROTATION_IN_PROGRESS or REPLAY_UNAVAILABLE. Webhook availability depends on environment readiness; confirm it with Sinbad.
Webhook delivery must be available in the selected environment. Confirm readiness with Sinbad.
Errors
Authentication
Bearer authentication of the form Bearer <token>, where token is your auth token.
Path parameters
Headers
Required on mutations. Same key/body returns safe original results for 24 hours. Signing secrets are never returned again.
Request
Response headers
no-store