> 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-deliveries/openapi.json](/docs/api/webhook-deliveries/openapi.json). CLI docs offline: `kenso docs <topic>`.
> Last updated: 2026-11-22.

# Webhook deliveries: Resend a delivery

> **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 deliveries](/docs/api/webhook-deliveries.md). Authentication, workspaces and errors: [/docs.md](/docs.md).

## Resend a delivery

`POST /v1/webhook-endpoints/{webhookEndpointId}/deliveries/{deliveryId}/resend` - operationId `webhook-deliveries.resend`

| Permission | Rate limit |
| --- | --- |
| The `integrations` permission | 30 requests a minute and 1,000 a day per workspace (Free plan: 3 a minute and 100 a day) |

Sends one event to this endpoint again. The response echoes the id you sent.

`deliveryId` is a delivery's `id` (`atmpt_...`) or its `messageId` (`msg_...`) from
`GET /v1/webhook-endpoints/{webhookEndpointId}/deliveries`. Kenso looks an `id` up among the
endpoint's newest 1,000 deliveries, so resend an older delivery by its `messageId`.

Resends share a workspace limit of 30 a minute and 1,000 a day.

Errors:

- `404 not_found`: the endpoint or the delivery is not found.
- `429 rate_limited`: the workspace reached its resend limit. Wait and try again.

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/deliveries/%7BdeliveryId%7D/resend)

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `webhookEndpointId` | path | string | yes | The webhook endpoint's id, which starts with `ep_`. |
| `deliveryId` | path | string | yes | The delivery's `id` (`atmpt_...`) or its `messageId` (`msg_...`). |
| `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 `WebhookDeliveryResend`.

| Field | Type | Description |
| --- | --- | --- |
| `deliveryId` | string | The delivery id or message id you sent. |

### Request

```bash
curl -X POST "https://api.ken.so/v1/webhook-endpoints/ep_2bX9kq4LmR7tW3vY/deliveries/atmpt_2bX9kq4LmR7tW3vY/resend" \
  -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": {
    "deliveryId": "atmpt_2bKqA1cD3eF5gH7iJ9kL0mN2pQ4"
  }
}
```
