Skip to main content
POST
Rotate the signing secret
Returns a new signing secret, once. For 24 hours after the rotation, each delivery carries two comma-separated signatures in X-Qwairy-Signature: the new one first, then the previous one. Receivers can deploy the new secret without losing events. See Verify signatures. Integration webhooks require an active Business, Agency Business or Enterprise plan. Changing an endpoint also requires an API token with write access enabled by an Owner or Manager. See Integration webhooks and Writing data.
string
required
Bearer token for your team.
string
required
Unique key for this operation, at most 255 characters. Completed responses replay for 24 hours.
string
required
Endpoint identifier.

Response

Returns 200, the new ETag and the endpoint with its new secret. previousSecretExpiresAt gives the time when the previous secret stops being used. The other fields are described in List webhook endpoints.

Synthetic request and response

Errors

See Error codes for authentication, plan, idempotency and server errors. A token without write access returns 403 API_KEY_READ_ONLY. On 429, honor Retry-After. If the write limiter is unavailable or writes are suspended, the request returns 503 SERVICE_UNAVAILABLE and nothing changes.