POST
Issue a new signing secret for a webhook endpoint

Authorizations

Authorization
string
header
required

A secret API key. Publishable keys cannot reach this API. A key may carry an expiry, and an expired key is refused exactly like an unknown one, with a 401 that names no reason; check the key's expires_at in the dashboard rather than inferring it from a response. When a merchant rolls a key's secret they choose a grace window of up to 3 days, and for its duration BOTH the new secret and the one it replaced authenticate, so an integration moves over on its own deploy schedule instead of at the instant the button is pressed. Move before the window closes: after it, the old secret is refused. Nothing else about this contract moves with a roll. The key keeps its id and its scopes, so the only thing an integration updates is the credential itself.

Headers

Idempotency-Key
string
required

A unique key per logical write. Replaying a request with the same key returns the first response byte for byte instead of applying the write twice.

Path Parameters

webhookEndpointId
string
required

Body

application/json

Takes no parameters, and an empty body is expected. The response is the new secret, shown once. IT IS NOT A CUTOVER. For seven days both the old and the new secret sign every delivery, so you redeploy your receiver on your own schedule rather than at the instant of this call. Rotating again inside that window is refused with 409 rotation_in_progress, because it would discard the secret you may not have replaced yet. This is also the recovery path if the create response was lost: it keeps the endpoint and its id, which deleting and recreating would not.

Response

Success

data
object