sequences

Check a drafted message for deliverability risks

Rule-based findings on the given subject and body: risky phrases, link density, shouting, punctuation, length, and for an email the variables, emoji and blanks left from a starter, with what passes. The text is the composer's: {{Column}} is a variable and {{spin: a | b}} a rotation. Deterministic and free; pure text analysis, nothing is stored.

post/sequences/spam-check/

Request

  • Base URL: https://api.getoneprofile.ai (the document declares no server; this is the origin it was published from)
  • URL: https://api.getoneprofile.ai/sequences/spam-check/
  • Auth: one of:
    • API key in header X-API-Key
    • HTTP bearer

Request body

bodystring
opens_threadboolean

Whether the email starts a thread of its own. A first email is held to a cold email's length, 25 to 200 words; a reply in a thread may be short. Read for an email only.

scope'email' | 'signature'

What kind of text the deliverability check is reading.

The rules are not all portable. Length is the one that isn't: a cold email under eight words really is a filter pattern, and a signature is ALWAYS under eight words (a name and a role is four). Run the email rules over a signature and every sender is told to pad theirs into "a sentence of substance", directly contradicting the guidance printed above the box that tells them to keep it to a name, a role, and one link.

Everything else (trigger phrases, link density, shouting, punctuation) means the same thing wherever the text ends up, and runs for both.

subjectstring

Response

Successful Response

passesstring[]

What an email passes, each with its value: "2 variables", "75 words", "No links", "1 emoji". Empty for a signature, and for an email with nothing in it yet.

Changes

No recorded changes to this operation across all 1 revision of this API.