> 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

> **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.

Delivery attempts to one webhook endpoint, and replaying one.

Integrations. 2 endpoints under `https://api.ken.so`. Every request sends `Authorization: Bearer <your API key>` and `Ken-Version: 2026-11-02`: see [Authentication](/docs/authentication.md), [Workspaces](/docs/workspaces.md) and [Errors](/docs/errors.md). OpenAPI for this resource only: [/docs/api/webhook-deliveries/openapi.json](/docs/api/webhook-deliveries/openapi.json).

Guide: [Webhooks](/docs/webhooks.md) - Receive events, verify their signatures, and handle retries and duplicates.

- `GET /v1/webhook-endpoints/{webhookEndpointId}/deliveries` - List an endpoint's delivery attempts (`webhook-deliveries.list`): [/docs/api/webhook-deliveries/list.md](/docs/api/webhook-deliveries/list.md)
- `POST /v1/webhook-endpoints/{webhookEndpointId}/deliveries/{deliveryId}/resend` - Resend a delivery (`webhook-deliveries.resend`): [/docs/api/webhook-deliveries/resend.md](/docs/api/webhook-deliveries/resend.md)

## List an endpoint's delivery attempts

`GET /v1/webhook-endpoints/{webhookEndpointId}/deliveries` - operationId `webhook-deliveries.list`

| Permission | Rate limit |
| --- | --- |
| The `integrations` permission | 12,000 requests a minute per API key |

Returns the attempts Kenso made to deliver events to this endpoint, newest first, with each attempt's result and
the HTTP status your endpoint answered. Use it to find failed deliveries to resend.

`limit` is from 1 to 200. To read the next page, pass `pagination.nextCursor` as `cursor`.
`createdAfter` and `createdBefore` keep the attempts whose `occurredAt` is in that range, and
`sort` takes `-createdAt` (newest first, the default). A page can hold fewer than `limit`
attempts; keep paging while `hasMore` is true.

Errors:

- `400 validation_failed`: `limit` is out of range, `sort` is not `-createdAt`, or
`createdBefore` is not later than `createdAfter`.
- `404 not_found`: the workspace has no endpoint with this id.

Requires the `integrations` permission.

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

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `webhookEndpointId` | path | string | yes | The webhook endpoint's id, which starts with `ep_`. |
| `limit` | query | integer (int32) | no | Attempts per page, from 1 to 200. Default 50. |
| `cursor` | query | string | no | The `pagination.nextCursor` of the previous page. Omit it for the first page. |
| `sort` | query | string | no | The order, by each attempt's `occurredAt`: only `-createdAt`, newest first, which is also the default. `createdAt` (oldest first) is `400 validation_failed`: the webhook provider lists attempts newest first. |
| `createdAfter` | query | string (date-time) | no | Only attempts made at or after this time (their `occurredAt`), in UTC. |
| `createdBefore` | query | string (date-time) | no | Only attempts made before this time (their `occurredAt`), in UTC. Must be later than `createdAfter`. |
| `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 list of `WebhookDelivery`. Each item has these fields. The response also carries `pagination`.

| Field | Type | Description |
| --- | --- | --- |
| `id` | string | The attempt id, a string that starts with `atmpt_`. |
| `messageId` | string | The id of the delivered message, a string that starts with `msg_`. Every attempt at the same event shares it. |
| `eventType` | string | The event type that was delivered. |
| `status` | string | The attempt's result: `success`, `pending` or `fail`. |
| `responseStatusCode` | integer (int32) | The HTTP status your endpoint answered. Null when it never answered. |
| `occurredAt` | string (date-time) | When Kenso made the attempt, in UTC. |

### Request

```bash
curl -X GET "https://api.ken.so/v1/webhook-endpoints/ep_2bX9kq4LmR7tW3vY/deliveries?limit=50" \
  -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": [
    {
      "id": "atmpt_2bKqA1cD3eF5gH7iJ9kL0mN2pQ4",
      "messageId": "msg_2bKq9xY1zA2bC3dE4fG5hI6jK7l",
      "eventType": "reply.classified",
      "status": "success",
      "responseStatusCode": 200,
      "occurredAt": "2026-10-13T16:22:41Z"
    }
  ],
  "pagination": {
    "nextCursor": "eyJpZCI6ODE1fQ",
    "hasMore": true,
    "total": 1,
    "totalCount": 1,
    "isTotalCapped": true
  }
}
```

## 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"
  }
}
```

All resources: [/docs.md](/docs.md).
