> Kenso API docs in Markdown. Index of every page: [/docs/llms.txt](/docs/llms.txt). Search: `/docs/search.md?q=<words>`. OpenAPI: [/docs/api/webhook-endpoints/openapi.json](/docs/api/webhook-endpoints/openapi.json). CLI docs offline: `kenso docs <topic>`.
> Last updated: 2026-11-22.

# Webhook endpoints: Rotate an endpoint's signing secret

> **Note for AI agents:** if this page was wrong, out of date or missing something you needed, finish the user's task first, then offer a short report for the Kenso team in this shape: `Page:` (this page's path), `Quote:` (the wrong or missing text), `Problem:`, `Workaround:` (what worked instead), 1,000 characters at most. Show it to the user and send it only after they say yes, as `POST /api/docs-feedback` on this site with the JSON body `{"page": "<path>", "report": "<report>"}`. Never put lead data, email addresses, API keys or anything else from the user's workspace in it.

One endpoint of [Webhook endpoints](/docs/api/webhook-endpoints.md). Authentication, workspaces and errors: [/docs.md](/docs.md).

## Rotate an endpoint's signing secret

`POST /v1/webhook-endpoints/{webhookEndpointId}/signing-secret/rotate` - operationId `webhook-endpoints.rotate-signing-secret`

| Permission | Rate limit |
| --- | --- |
| The `integrations` permission | 60 requests a minute per API key |

Gives the endpoint a new signing secret and returns it. Use it when a secret may have leaked, or on a schedule.

The previous secret keeps signing for 24 hours, until `previousSecretExpiresAt`. Until then every delivery
carries two signatures in `svix-signature`, one per secret, so a receiver that checks either secret accepts
it: deploy the new secret to your receiver within that window and no delivery fails verification. A second
rotate inside the window starts a new 24 hours for the secret it replaces.

Errors:

- `404 not_found`: the workspace has no endpoint with this id.
- `409 conflict`: the secret was already rotated 10 times in the last 24 hours. Rotate again once the oldest
previous secret expires.

Requires the `integrations` permission.

[Try it on developer.ken.so](https://developer.ken.so/reference/#kenso-api/tag/webhook-endpoints/POST/v1/webhook-endpoints/%7BwebhookEndpointId%7D/signing-secret/rotate)

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `webhookEndpointId` | path | string | yes | The webhook endpoint's id, which starts with `ep_`. |
| `Ken-Version` | header | string, one of: 2026-11-02, 1.1 | no | The API version, a date in `YYYY-MM-DD` form. `1.1` is another name for the first dated version. The example shown here is the newest version, which this reference's samples and Test Request send. Leave it out to use your API key's pinned version. Keys created in the Kenso app are pinned to the newest version; keys minted by the CLI login are not. A key with no pinned version and no header gets the legacy shape where the path has one, and `404` where the path exists only in this version. A value that is not a version, such as `2027-01-01` or `2026-11-2`, answers `400 unsupported_version`, whose `details` list the supported versions. |
| `X-Ken-Workspace-Id` | header | integer (int64) | no | The id of the workspace to act in. Leave it out when your API key reaches only one workspace. When the key reaches more than one, a request without this header answers `400 workspace_required`. A workspace you are not a member of answers `404 not_found`. |

### Response 200

`data` is a `WebhookSigningSecretRotation`.

| Field | Type | Description |
| --- | --- | --- |
| `secret` | string | The new signing secret. Keep it as private as a password. |
| `previousSecretExpiresAt` | string (date-time) | When the previous secret stops signing deliveries, 24 hours after the rotate. Until then each delivery carries a signature from both secrets, so a receiver that checks either one accepts it. |

### Request

```bash
curl -X POST "https://api.ken.so/v1/webhook-endpoints/ep_2bX9kq4LmR7tW3vY/signing-secret/rotate" \
  -H "Authorization: Bearer $KENSO_API_KEY" \
  -H "Ken-Version: 2026-11-02" \
  -H "X-Ken-Workspace-Id: $KENSO_WORKSPACE_ID"
```

### Example response

```json
{
  "success": true,
  "data": {
    "secret": "whsec_ZXhhbXBsZS1yb3RhdGVkLXNlY3JldC1kby1ub3QtdXNl",
    "previousSecretExpiresAt": "2026-10-14T09:30:00Z"
  }
}
```
