# Rotate a signing secret

> Page: https://docs.flung.dev/reference/api/post-v1-webhook-endpoints-id-rotate-secret. Index of every page: https://docs.flung.dev/llms.txt

Issues a new secret.

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

## TL;DR

| Question | Answer |
|---|---|
| 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`](https://docs.flung.dev/reference/api/schemas.md#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](https://docs.flung.dev/reference/api/errors.md). |

## 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

**curl**

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

**TypeScript**

```ts
import { Flung } from '@flung.dev/sdk'

const flung = new Flung({ apiKey: process.env.FLUNG_API_KEY! })
const result = await flung.webhookEndpoints.rotateSecret({
  id: 'whe_aaaaaaaaaaaaaaaaaaaaaaaa',
})
```

**fetch**

```js
const response = await fetch('https://api.flung.dev/v1/webhook-endpoints/whe_aaaaaaaaaaaaaaaaaaaaaaaa/rotate-secret', {
  method: 'POST',
  headers: {
    'Authorization': `Bearer ${process.env.FLUNG_API_KEY}`,
  },
})
if (!response.ok) throw new Error((await response.json()).error.message)
const result = await response.json()
```

A successful answer looks like this:

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

## Path parameters

| Field | Type | Required | Description |
|---|---|---|---|
| `id` | `string` | yes |  |

## Responses

| Status | Meaning | Body |
|---|---|---|
| 200 | The new secret. | [`RotatedSecret`](https://docs.flung.dev/reference/api/schemas.md#rotatedsecret) |
| 401 | Missing, unknown, revoked or expired API key. | [`Error`](https://docs.flung.dev/reference/api/schemas.md#error) |
| 404 | No such endpoint in this workspace. | [`Error`](https://docs.flung.dev/reference/api/schemas.md#error) |
| 422 | The request failed validation. | [`Error`](https://docs.flung.dev/reference/api/schemas.md#error) |
| 429 | Too many requests for this credential; wait for `retry-after` seconds. | [`Error`](https://docs.flung.dev/reference/api/schemas.md#error) |

## Response body

A 200 answer has the type [`RotatedSecret`](https://docs.flung.dev/reference/api/schemas.md#rotatedsecret).

| Field | Type | Required | Description |
|---|---|---|---|
| `secret` | `string` | yes | The new signing secret. Shown only in this response. |
| `previousSecretExpiresAt` | `string` | yes | Until then, deliveries carry signatures from both secrets. |

## See also

| Doc | Why |
|---|---|
| [API reference](https://docs.flung.dev/reference/api.md) | Every endpoint |
| [Schemas](https://docs.flung.dev/reference/api/schemas.md) | Every request and response type |
| [Errors](https://docs.flung.dev/reference/api/errors.md) | Every error code and what to do about it |