Webhook event types
The event types you can subscribe to.
Headers
The endpoints on this page take these headers. Each endpoint's curl shows the ones it sends.
| Name | In | Type | Required | Description |
|---|---|---|---|---|
Ken-Version | header | string, one of: 2026-11-02, 1.1 | optional | 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 date that is not a version answers 400 unsupported_version; any other value that is not a version is treated as legacy. |
X-Ken-Workspace-Id | header | integer (int64) | optional | 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. |
List webhook event types
/v1/webhook-event-typeswebhook-event-types.list- Permission
- The
integrationspermission - Rate limit
- 12,000 requests a minute per API key
Returns every event type the workspace can receive, in display order. Use the names in a webhook endpoint's events.
Each type has its group, a description, the delivery filters it supports (campaign, classification, channel), whether it is high-volume, and a sample body. aliases lists other names that subscribe to the same type: the ten types named before the dotted convention, such as email_sent, each have a dotted alias, such as email.sent. Types with mcp set to true can also be polled with GET /v1/event-occurrences and subscribed to with POST /v1/event-subscriptions. Kenso lists a type that is still rolling out only to the workspaces that have it.
Requires the integrations permission.
Parameters
| Name | In | Type | Required | Description |
|---|---|---|---|---|
limit | query | integer (int32) | optional | Items per page, from 1 to 200. Omit limit and cursor to get every item in one response, as before; with only cursor, 50 per page. |
cursor | query | string | optional | The nextCursor of the previous page. Omit it for the first page. |
curl -X GET "https://api.ken.so/v1/webhook-event-types?limit=1" \
-H "Authorization: Bearer $KENSO_API_KEY" \
-H "Ken-Version: 2026-11-02" \
-H "X-Ken-Workspace-Id: $KENSO_WORKSPACE_ID"Response 200
data is a list of WebhookEventType. Each item has these fields. The response also carries pagination.
Show the 9 response fields and an example
The fields and an example are also on this endpoint's Markdown page.
Get a webhook event type's payload schema
/v1/webhook-event-types/{eventType}/schemawebhook-event-types.get-schema- Permission
- The
integrationspermission - Rate limit
- 12,000 requests a minute per API key
Returns the JSON Schema (draft 2020-12) of one event's body for an event type, for the schemaVersion in the response. Every event body carries its schemaVersion; changes that keep a schema version only add keys, so accept keys a schema does not list. A key the schema lists in required is always sent, as null when its type admits null; any other key is left out when it does not apply. A batched endpoint receives a wrapper whose events holds the event bodies: validate each element against its own type's schema, not the wrapper.
Pass schemaVersion=2026-12 for the body an endpoint that opted into 2026-12 receives: workspaceId for clientId, the dotted eventType, snake_case labels, and no key sent as null.
Errors:
400 validation_failed:schemaVersionis not2026-11or2026-12.404 not_found: the workspace cannot receive an event type with this name.
Requires the integrations permission.
Parameters
| Name | In | Type | Required | Description |
|---|---|---|---|---|
eventType | path | string | required | The event type's name, as listed by GET /v1/webhook-event-types, or its dotted alias (email.sent). |
schemaVersion | query | string | optional | The body's schemaVersion: 2026-11 (the default) or 2026-12. |
curl -X GET "https://api.ken.so/v1/webhook-event-types/email.sent/schema" \
-H "Authorization: Bearer $KENSO_API_KEY" \
-H "Ken-Version: 2026-11-02" \
-H "X-Ken-Workspace-Id: $KENSO_WORKSPACE_ID"Response 200
data is a WebhookEventSchema.
Show the 3 response fields and an example
The fields and an example are also on this endpoint's Markdown page.
More in Integrations:Webhook endpointsWebhook deliveriesEventsInbound webhooksCRM connectionsCRM syncCRM field mappingsCRM fieldsCRM importsCRM listsCRM pipelinesCRM recordsCRM sync issuesTriggersTrigger firingsTrigger schemasEvent subscriptionsEvent logAll resources