Skip to Content
Prospecting data

Signals

Queue signals for the current workspace.

Prospecting data1 endpointKen-Version: 2026-11-02AuthenticationWorkspacesErrors
MarkdownOpenAPI

Headers

The endpoints on this page take these headers. Each endpoint's curl shows the ones it sends.

NameInTypeRequiredDescription
Ken-Versionheaderstring, one of: 2026-11-02, 1.1optionalThe 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-Idheaderinteger (int64)optionalThe 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.

Send test signals

POST/v1/signalssignals.create
Permission
Search edit
Rate limit
480 requests a minute per API key

Try it on developer.ken.so

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.

Request body

application/json, optional.

FieldTypeRequiredDescription
isSyntheticbooleanoptionalHas no effect: Kenso stores every signal you send as a test signal.
signalsarray of CreateSignalRequestoptionalThe signals, from 1 to 100.
Request
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"
    }
  ]
}'

Response 200

data is a SignalIntake.

Show the 3 response fields and an example

The fields and an example are also on this endpoint's Markdown page.


On this page