> 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: Create a webhook endpoint

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

## Create a webhook endpoint

`POST /v1/webhook-endpoints` - operationId `webhook-endpoints.create`

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

Registers a URL that receives the event types you list. Kenso starts sending matching events to it right away.

`url` is required. It must use https and resolve to a public address. `events` is required and lists at
least one event type from `GET /v1/webhook-event-types`. A type's alias from that list, such as
`email.sent` for `email_sent`, names the same type, and a type listed twice is subscribed once, so the
endpoint gets each event once. `app` tags the endpoint as `zapier`,
`make` or `n8n`. When you omit `app`, Kenso takes it from the URL host.

`campaignIds` and `classifications` filter deliveries. When both are set, an event must match both. A
filter holds at most 10 campaigns, 10 classifications, or campaigns times classifications up to 10.
`isBatched` sends the high-volume event types in batches, and needs an `events` list.
`schemaVersion` picks the payload schema: `2026-11`, the default, or `2026-12`, which is rolling out
and needs an `events` list and no batch delivery. An enabled endpoint without an `events` list receives
every event type, the `2026-12` deliveries included, so while one is enabled in the workspace a
`2026-12` endpoint is refused.

A workspace holds at most 25 endpoints.

Errors:

- `400 validation_failed`: `url` is missing, not https or not public, an event type is unknown to
the workspace, `app` or a classification is unknown, the filter is too large, batch delivery is not
available to the workspace yet, or `schemaVersion` is unknown or not available to the workspace yet. Also
for `schemaVersion` `2026-12` while another enabled endpoint has no `events` list: give that
endpoint an `events` list first.
- `404 not_found`: a campaign in `campaignIds` is not in the workspace.
- `409 conflict`: the workspace already has 25 endpoints. Delete one first.

Requires the `integrations` permission.

[Try it on developer.ken.so](https://developer.ken.so/reference/#kenso-api/tag/webhook-endpoints/POST/v1/webhook-endpoints)

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `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 |
| --- | --- | --- | --- |
| `url` | string | yes | Required. The https URL that receives events. It must resolve to a public address, and has at most 2,048 characters. |
| `events` | array of string | yes | Required. The event types the endpoint receives, at least one, from `GET /v1/webhook-event-types`. A type's alias names the same type. |
| `description` | string | no | Your own note about the endpoint, at most 500 characters. |
| `app` | string | no | The app the endpoint belongs to: `zapier`, `make` or `n8n`. Omitted: Kenso takes it from the URL host when the host belongs to one of them. |
| `campaignIds` | array of integer (int64) | no | Deliver only events of these campaigns of the workspace. Omitted or empty: every campaign. |
| `classifications` | array of string | no | Deliver only events whose reply has one of these classifications, in snake_case, such as `interested`. Omitted or empty: every classification. |
| `isBatched` | boolean | no | True to receive the high-volume event types in batches. Needs an `events` list. Default false. |
| `schemaVersion` | string | no | The payload schema: `2026-11` (the default) or `2026-12`, which is rolling out and offered only to the workspaces that have it. `2026-12` needs an `events` list and no batch delivery. |

### Response 201

`data` is a `WebhookEndpoint`.

| Field | Type | Description |
| --- | --- | --- |
| `id` | string | The endpoint id, a string that starts with `ep_`. |
| `url` | string | The https URL Kenso sends events to. |
| `events` | array of string | The event types the endpoint receives. Empty means every event type. A `2026-12` endpoint lists the dotted names, such as `email.sent` for `email_sent`. |
| `description` | string | Your own note about the endpoint. Null when none was set. |
| `isDisabled` | boolean | True when delivery to this endpoint is paused. |
| `createdAt` | string (date-time) | When the endpoint was created, in UTC. |
| `app` | string | The app the endpoint belongs to: `zapier`, `make` or `n8n`. Null otherwise. |
| `health` | string | The endpoint's health: `active`, `failing` (the newest attempt failed) or `disabled`. Omitted, together with `lastDelivery` and `failedAttempts`, when Kenso could not read the delivery log. |
| `lastDelivery` | WebhookLastDelivery | The newest delivery attempt. Omitted when there is none yet. |
| `failedAttempts` | integer (int32) | Failed attempts since the newest success, among the latest 10 attempts. 0 unless the endpoint is failing. |
| `campaignIds` | array of integer (int64) | The campaign filter: the endpoint receives only events of these campaigns. Empty means every event. A filtered endpoint never receives an event that has no campaign. |
| `classifications` | array of string | The classification filter, as snake_case reply classifications such as `interested`. The endpoint receives only events whose reply has one of them. Empty means every event. A filtered endpoint never receives an event without a reply classification. With `campaignIds` also set, an event must match both. |
| `isBatched` | boolean | True when the high-volume event types arrive as `<type>.batch` deliveries of up to 100 events (`{eventType, eventId, timestamp, clientId, count, events}`), never one by one. |
| `schemaVersion` | string | The payload schema the endpoint receives: `2026-11`, or `2026-12`, which sends `workspaceId` for `clientId`, leaves out null values, writes enum values in snake_case and names every event type dotted. |

### Request

```bash
curl -X POST "https://api.ken.so/v1/webhook-endpoints" \
  -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 '{
  "url": "https://hooks.example.com/kenso/replies",
  "events": [
    "reply.classified"
  ],
  "description": "Interested replies into our CRM",
  "campaignIds": [
    4821
  ],
  "classifications": [
    "interested"
  ],
  "isBatched": false
}'
```

### Example response

```json
{
  "success": true,
  "data": {
    "id": "ep_2bKq8yZ0aB3cD4eF5gH6iJ7kL8m",
    "url": "https://hooks.example.com/kenso/replies",
    "events": [
      "reply.classified"
    ],
    "description": "Interested replies into our CRM",
    "isDisabled": false,
    "createdAt": "2026-09-23T15:02:11Z",
    "health": "active",
    "lastDelivery": {
      "occurredAt": "2026-10-13T16:22:41Z",
      "status": "success",
      "responseStatusCode": 200,
      "eventType": "reply.classified"
    },
    "failedAttempts": 0,
    "campaignIds": [
      4821
    ],
    "classifications": [
      "interested"
    ],
    "isBatched": false,
    "schemaVersion": "2026-11"
  }
}
```

## Types

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

### WebhookLastDelivery

The newest delivery attempt to an endpoint.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `occurredAt` | string (date-time) | no | When Kenso made the attempt, in UTC. |
| `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. |
| `eventType` | string | no | The event type that was delivered. |
