> Kenso API docs in Markdown. Index of every page: [/docs/llms.txt](/docs/llms.txt). Search: `/docs/search.md?q=<words>`. OpenAPI: [/docs/api/signals/openapi.json](/docs/api/signals/openapi.json). CLI docs offline: `kenso docs <topic>`.
> Last updated: 2026-11-22.

# Signals: Send test signals

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

## Send test signals

`POST /v1/signals` - operationId `signals.create`

| Permission | Rate limit |
| --- | --- |
| Search edit | 480 requests a minute per API key |

Queue up to 100 test signals for this workspace, to check that a test campaign's triggers fire on them.

Send `signals`, a list of 1 to 100 signals. Each signal takes:

- `type`: the signal type in lowercase snake_case, such as `email_opened`, `link_clicked`,
`reply_received`, `job_change` or `fundraising`. Required.
- `source`: where the signal came from, in lowercase snake_case, such as `client_api`. Omitted means
`internal_email_engagement`.
- `contactId`, `campaignId` and `campaignSegmentId`: what the signal is about. Each must be in this
workspace.
- `payload`: the signal's details, a JSON object of at most 16 KB.
- `occurredAt`: when the event happened. Omitted means now.
- `dedupKey`: up to 200 characters, with no control characters. Kenso skips a signal whose
`dedupKey` it queued in the last 24 hours.

The answer holds `acceptedCount`, the signals queued, and `duplicateCount`, the signals skipped for their
`dedupKey`. Every signal counts against the workspace's signal quota, which allows 200 signals a minute and
2,000 a day.

Errors:

- `400 validation_failed`: the list is empty or has more than 100 signals, a `type` or `source` is
unknown, a field is not valid, or a contact, campaign or segment is not in this workspace. For a field that is not
valid, `details[0].field` names the signal and the field, such as `signals[2].type`.
- `429 rate_limited`: the workspace sent its 200 signals this minute or 2,000 today. Wait for the time in
`Retry-After`.
- `503 service_unavailable`: Kenso could not queue every signal, and the message says how many it queued.
Send the list again with the same `dedupKey` values, so the queued ones are skipped.

Requires Search edit.

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

### 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 |
| --- | --- | --- | --- |
| `isSynthetic` | boolean | no | Has no effect: Kenso stores every signal you send as a test signal. |
| `signals` | array of CreateSignalRequest | no | The signals, from 1 to 100. |

### Response 200

`data` is a `SignalIntake`.

| Field | Type | Description |
| --- | --- | --- |
| `acceptedCount` | integer (int32) | Signals queued by this call. |
| `duplicateCount` | integer (int32) | Signals skipped because their `dedupKey` was queued in the last 24 hours. |
| `isSynthetic` | boolean | True when the signals were stored as test signals, which is always the case here. |

### Request

```bash
curl -X POST "https://api.ken.so/v1/signals" \
  -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 '{
  "isSynthetic": true,
  "signals": [
    {
      "type": "email_opened",
      "source": "client_api",
      "contactId": 812,
      "campaignId": 812,
      "campaignSegmentId": 812,
      "payload": null,
      "occurredAt": "2026-09-23T15:02:11Z",
      "dedupKey": "string"
    }
  ]
}'
```

### Example response

```json
{
  "success": true,
  "data": {
    "acceptedCount": 1,
    "duplicateCount": 1,
    "isSynthetic": true
  }
}
```

## Types

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

### CreateSignalRequest

One test signal.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `type` | string | yes | The signal type in lowercase snake_case, such as `email_opened` or `job_change`. Required. |
| `source` | string | no | Where the signal came from, in lowercase snake_case, such as `client_api`. Omitted means `internal_email_engagement`. |
| `contactId` | integer (int64) | no | The contact the signal is about. It must be in this workspace. |
| `campaignId` | integer (int64) | no | The campaign the signal is about. It must be in this workspace. |
| `campaignSegmentId` | integer (int64) | no | The campaign segment the signal is about. It must be in this workspace. |
| `payload` | object | no | The signal's details, a JSON object of at most 16 KB. |
| `occurredAt` | string (date-time) | no | When the event happened. Omitted means now. |
| `dedupKey` | string | no | A key of up to 200 characters, with no control characters. Kenso skips a signal whose key it queued in the last 24 hours. |
