Webhooks
Rotate A Webhook Signing Secret
Mint a fresh signing secret while the previous one keeps signing during a grace window.
POST
Permission Required
This endpoint requires thewebhooks.manage permission (the { kind: "webhook" } scope) on your API key, plus the webhooks feature. Webhooks are gated to api_pro or higher plans: a key on a free plan receives 403 error_api_feature_required.
Access / Membership Rules
Webhooks are owner-scoped. The{id} must resolve to an endpoint in your key’s own derived scope (user, game, or league, depending on your key type). An endpoint owned by another scope - or an unknown id - is reported as 404 error_webhook_not_found.
What’s Returned
Returns{ id, signingSecret, secretPrefix }. signingSecret is the new plaintext secret and secretPrefix is its first 8 chars (display only). Rotating also resets the endpoint’s failure count.
The previous secret keeps signing deliveries for a 24-hour grace window after rotation, so your
consumers can roll over to the new secret without missing or rejecting deliveries. Verify
signatures against both secrets until you have finished updating, then drop the old one. For the
full signature scheme and header details, see the Webhooks guide.
Authorizations
Send your API key as: Authorization: Bearer tb_
Path Parameters
Webhook endpoint id.