> 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: Send a test event

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

## Send a test event

`POST /v1/webhook-endpoints/{webhookEndpointId}/test` - operationId `webhook-endpoints.test`

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

Sends the sample body of one event type to this endpoint only, and waits up to 5 seconds for the first attempt.
Use it to check that your endpoint receives and accepts Kenso's deliveries.

`eventType` can be any event type available to the workspace, or its alias, even one the endpoint does not
receive or filters out. It defaults to the first event type the endpoint receives, or `reply.received` when
the endpoint receives every type. A batched endpoint gets the `<type>.batch` sample of a high-volume
type, and `eventType` in the response says so. A `2026-12` endpoint gets the `2026-12` sample.

Errors:

- `400 validation_failed`: `eventType` is not available to the workspace.
- `404 not_found`: the workspace has no endpoint with this id.
- `409 invalid_state`: the endpoint is disabled. Enable it first.
- `429 rate_limited`: the workspace reached its limit of 30 test sends a minute or 1,000 a day. Wait the
seconds in `Retry-After` 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/test)

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

### Request body

`application/json`, optional.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `eventType` | string | no | The event type or its alias to send. Any type available to the workspace works, even one the endpoint does not receive. Omitted: the first type the endpoint receives, or `reply.received` when it receives every type. |

### Response 200

`data` is a `WebhookEndpointTest`.

| Field | Type | Description |
| --- | --- | --- |
| `messageId` | string | The id of the test message, a string that starts with `msg_`. |
| `eventType` | string | The event type Kenso sent. A batched endpoint gets `<type>.batch` for a high-volume type. |
| `attempt` | WebhookEndpointTestAttempt | The first delivery attempt, read for up to 5 seconds. Omitted when Kenso made none by then. |

### Request

```bash
curl -X POST "https://api.ken.so/v1/webhook-endpoints/ep_2bX9kq4LmR7tW3vY/test" \
  -H "Authorization: Bearer $KENSO_API_KEY" \
  -H "Ken-Version: 2026-11-02" \
  -H "X-Ken-Workspace-Id: $KENSO_WORKSPACE_ID" \
  -H "Content-Type: application/json" \
  -d '{
  "eventType": "reply.classified"
}'
```

### Example response

```json
{
  "success": true,
  "data": {
    "messageId": "msg_2bKqB7dE9fG1hI3jK5lM7nO9pQ1",
    "eventType": "reply.classified",
    "attempt": {
      "status": "success",
      "responseStatusCode": 200,
      "occurredAt": "2026-10-14T09:44:03Z"
    }
  }
}
```

## Types

Each named type the tables above use, nested ones included.

### WebhookEndpointTestAttempt

The first attempt to deliver a test event.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `status` | string | no | The attempt's result: `success`, `pending` or `fail`. |
| `responseStatusCode` | integer (int32) | no | The HTTP status your endpoint answered. Omitted when it never answered. |
| `occurredAt` | string (date-time) | no | When Kenso made the attempt, in UTC. |
