Skip to content
Connect an agent

Webhooks

Rotate a signing secret

Issues a new secret.

POST/v1/webhook-endpoints/{id}/rotate-secret

TL;DR

QuestionAnswer
What does it do?Rotate a signing secret.
What does it need?An API key or an OAuth access token.
What does it take?id in the path.
What does it return?Status 200 with a body of type RotatedSecret.
In the SDK?flung.webhookEndpoints.rotateSecret()
What can go wrong?401 Missing, unknown, revoked or expired API key; 404 No such endpoint in this workspace; 422 The request failed validation; 429 Too many requests for this credential; wait for retry-after seconds. Every failure has the same error shape.

What it does

Issues a new secret. For 24 hours every delivery is signed with both the new and the old secret, so you can deploy the new one without missing events; after that only the new one signs.

Example

bash
curl -X POST 'https://api.flung.dev/v1/webhook-endpoints/whe_aaaaaaaaaaaaaaaaaaaaaaaa/rotate-secret' \  --header "Authorization: Bearer $FLUNG_API_KEY"

A successful answer looks like this:

json
{  "secret": "string",  "previousSecretExpiresAt": "2026-11-01T09:00:00.000Z"}

Path parameters

FieldTypeRequiredDescription
idstringyes

Responses

StatusMeaningBody
200The new secret.RotatedSecret
401Missing, unknown, revoked or expired API key.Error
404No such endpoint in this workspace.Error
422The request failed validation.Error
429Too many requests for this credential; wait for retry-after seconds.Error

Response body

A 200 answer has the type RotatedSecret.

FieldTypeRequiredDescription
secretstringyesThe new signing secret. Shown only in this response.
previousSecretExpiresAtstringyesUntil then, deliveries carry signatures from both secrets.

See also

DocWhy
API referenceEvery endpoint
SchemasEvery request and response type
ErrorsEvery error code and what to do about it