Skip to Content
Copy and personalization

Copy checks

Email copy lints check an email step's copy against Kenso's rules for cold email: length, links, tokens, the opening line and spam words. The check runs in code without an AI model, so the same copy always gets the same result. Nothing is saved, and calls do not count toward any limit.

Copy and personalization1 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.

Lint an email step

POST/v1/email-copy-lintsemail-copy-lints.lint
Permission
Campaigns view
Rate limit
4,800 requests a minute per API key

Try it on developer.ken.so

Checks one email step's subject and body against every rule and returns each rule's result, with the text it matched. Send the step's stepOrder so the first email and follow-ups get their own rules.

Each rule is pass, fail or skipped. A failed rule has a severity: reject means the copy should not go out as it is, and flag means a person should look at it. passed is false when any rule failed with reject. The rules come back in the same order every time.

The lint does not judge whether a claim is true or the offer is clear. For a read of the copy itself, use POST /v1/email-copy-grades.

The rules, which reject unless marked as a flag:

  • subject_length: the subject has 1 to 60 characters.
  • body_words: the body has 40 to 180 words.
  • static_words: the words you wrote, without the greeting, AI variable lines, signature and P.S., number 50 to 80 on the first email and 30 to 60 on a follow-up. Over the range rejects, and under it flags.
  • em_dash: no em dashes.
  • links: at most one link, https only, no link shortener, and no web address as the link text.
  • placeholders: no text in square brackets, and no TODO or TBD.
  • merge_fields: every {token} is one a sequence step accepts, and a custom variable key counts only when customVariableKeys lists it. No {a|b} spintax and no {sender_signature}.
  • blank_merge_fields (flag): no contact fields that are often blank.
  • ai_variables: every {{AI variable}} is named in variables. Skipped when you omit variables.
  • first_line_fact (flag), first_line_first_person, first_line_praise, first_line_hedging and first_line_length (flag): on the first email, the opening sentence names a number, a name or a place, uses no first person (I, me, we, our), holds no praise or hedging, and has 8 to 20 words. Skipped on a follow-up and when the opener is an AI variable.
  • bridge (flag): on the first email, the sentence after the opener does not jump to a generic statement.
  • spam_never: no word from the never tier and no fake Re: or Fwd: subject.
  • spam_high: one high-tier word flags, and two or more reject.
  • spam_medium: three or more medium-tier words reject. With isFinanceVertical, finance words do not count.
  • spam_subject: the subject has no word from any tier, no $ or %, and no stacked numbers.
  • spam_structure: no word in all caps, at most one ! per email, and no !!! or ???.

Errors:

  • 400 validation_failed: body is blank or over 20,000 characters, subject is over 1,000 characters, stepOrder is outside 1 to 30, or variables or customVariableKeys lists more than 100 entries or an entry over 200 characters.

Requires Campaigns view.

Request body

application/json, optional.

The step's copy and context.

FieldTypeRequiredDescription
subjectstringoptionalThe step's subject line, at most 1,000 characters. An empty subject fails subject_length.
bodystringrequiredThe step's body, as plain text or the editor's HTML. Required, at most 20,000 characters.
stepOrderinteger (int32)optionalThe step's place in the sequence, from 1 to 30: 1 (the default) is the first email, and 2 and up are follow-ups.
variablesarray of stringoptionalThe names of the campaign's AI variables that have a personalization prompt, such as First Line. Omit it to skip the ai_variables rule. At most 100 names of up to 200 characters each.
customVariableKeysarray of stringoptionalThe campaign's custom variable keys, such as industry_note. A {key} token passes merge_fields only when its key is listed. At most 100 keys of up to 200 characters each.
isFinanceVerticalbooleanoptionalTrue when the sender's business is in finance, insurance, real estate or lending. Then insurance, mortgage, loans, investment and rates do not count toward spam_medium. Defaults to false.
Request
curl -X POST "https://api.ken.so/v1/email-copy-lints" \
  -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 '{
  "subject": "string",
  "body": "string",
  "stepOrder": 1,
  "variables": [
    "string"
  ],
  "customVariableKeys": [
    "industry_note"
  ],
  "isFinanceVertical": true
}'

Response 200

data is a EmailCopyLint.

Show the 8 response fields and an example

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


On this page