Developers

Compliance

Every call, text and email sent through the API goes through the same checks as the app. A key can't turn them off.

What's checked

  • Do Not Call and Do Not Text. DNC and DNT tags on the lead or its contact, and the account's do-not-call list.
  • Opt-outs. A number that replied STOP gets no texts. An email address that unsubscribed gets no email.
  • Calling hours. Calls and texts go out 8 AM to 9 PM in the lead's own time zone, worked out from the lead's state or address and the number's area code. When a lead spans more than one zone, every zone has to be inside the window. When no zone can be found, the window is 11 AM to 9 PM Eastern. Email has no calling hours.
  • Only numbers on the lead. You can only reach a phone number or email address already on the lead.
No override

Fields that would skip a check, such as force or sendAnyway, are dropped from API key requests. The checks run every time.

A tag can be added through the API (see Tag or untag a lead), but DNC and DNT can only be removed in the app.

What a refusal looks like

Nothing is sent when a check fails. The response says why in plain words, with a code to branch on. Over MCP, the same message comes back as a tool error.

Do Not Call (403)

The lead or the matching contact is tagged DNC, or the number is on the account's do-not-call list. Blocks calls, texts and email.

{
  "error": "This number is marked Do Not Call. It can't be called through the API. Nothing was sent.",
  "code": "do_not_contact",
  "doNotContact": "dnc"
}

Do Not Text (403)

The lead or the matching contact is tagged DNT. Blocks texts and email; calls can still go out.

{
  "error": "This number is marked Do Not Text. It can't be texted through the API. Nothing was sent.",
  "code": "do_not_contact",
  "doNotContact": "dnt"
}

Opted out (403)

The number replied STOP. Blocks texts.

{
  "error": "This number replied STOP to opt out. It can't be texted through the API. Nothing was sent.",
  "code": "do_not_contact",
  "doNotContact": "opted_out"
}

Unsubscribed email (403)

The address unsubscribed, or its domain is on the account's suppressed list.

{
  "error": "seller@example.com has unsubscribed — sending to them is refused.",
  "code": "do_not_email"
}

Outside calling hours (409)

A call or text outside the lead's calling hours. nextOpenAt says when the window opens.

{
  "error": "Outside calling hours: texts go out 8 AM–9 PM in the lead's local time. Nothing was sent.",
  "code": "quiet_hours",
  "zones": [
    "America/Chicago"
  ],
  "zoneSource": "state",
  "nextOpenAt": "2026-10-17T13:00:00.000Z"
}

Number not on the lead (400)

The to number or address isn't on the lead. Add it to the lead or contact in Syntropic first.

{
  "error": "That number isn't on this lead — add it to the contact first.",
  "code": "not_on_lead"
}

Sending line unavailable (409)

A text named a from line this key's teammate can't use, or one that can't send right now. It is never sent from another number.

{
  "error": "That number can't send this text: this key's teammate can't use it, or it's benched, inbound-only, unregistered or not connected. Nothing was sent.",
  "code": "from_unavailable"
}

Send not confirmed (502)

A text with from was handed off for delivery but the result never came back. It may have gone out: confirm it didn't before sending again.

{
  "error": "The text may have been sent. Don't retry until you've confirmed it didn't go out.",
  "code": "send_unconfirmed",
  "deliveryJobId": "job_123"
}

If sending through the API isn't turned on yet, send endpoints answer 403 with code not_enabled, and nothing is sent.

Compliance | Syntropic Developers