Auto-pauses
Inboxes, domains and campaigns Kenso paused on its own, and why.
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 auto-pauses
/v1/auto-pausesauto-pauses.list- Permission
- Campaigns view
- Rate limit
- 12,000 requests a minute per API key
Lists the pauses Kenso applied on its own, newest first. Use it to find out why an inbox, domain or campaign stopped sending.
Kenso pauses a target when a bounce, complaint, Gmail spam or sender rejection rate crosses its threshold, a placement test lands in spam, a domain is on a URI blocklist, Kenso cannot read an inbox's replies, or Microsoft blocks the sending tenant. Pauses you set yourself are not listed.
Repeated hard send failures do not pause a campaign: it keeps sending, its sendingError describes the failures, and the Kenso team gets an alert.
The list holds every pause that started at or after since, plus any older pause that is still active. A block that Kenso renewed before it lifted counts as one pause. isActive is true while the target is still paused. Page with limit and cursor.
Errors:
400 validation_failed:limitis not from 1 to 200, orcursoris invalid.
Requires Campaigns view.
Parameters
| Name | In | Type | Required | Description |
|---|---|---|---|---|
since | query | string (date-time) | optional | Earliest pause start to list, an ISO 8601 timestamp that is not in the future. Default 7 days ago, and Kenso reads a time more than 30 days ago as 30 days ago. |
limit | query | integer (int32) | optional | Number of pauses per page, from 1 to 200. Default 50. |
cursor | query | string | optional | The nextCursor from the previous page. Omit it for the first page. |
curl -X GET "https://api.ken.so/v1/auto-pauses?limit=50" \
-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 AutoPause. Each item has these fields. The response also carries pagination.
Show the 16 response fields and an example
The fields and an example are also on this endpoint's Markdown page.
More in Campaigns:CampaignsEmail sequencesLinkedIn sequencesSegment email sequencesSegment LinkedIn sequencesSequence variablesSequences with conditionsSequence importSegmentsLead listsShare linksClient approvalsSending capacityCampaign languagesLocalized stepsText translationMarket packsCountry complianceCampaign imagesAll resources