Skip to main content
Every error comes back in the response envelope with status set to false and a message in error. Messages are written for people, so you can show them as they are.

Status codes

Errors the API handles itself come back with HTTP 200. Read status on every response, not only the HTTP code.

Common messages

Campaigns

Starting a campaign

Start campaign checks these in order and stops at the first one that fails:

Editing a campaign

What you can change depends on the campaign’s status: A change that doesn’t fit the status is refused with a message that names the status, such as A running campaign keeps the audience it started with — its people are already queued or A completed campaign can only be renamed.

Retrying

  • Retry 500 errors and network failures after a short wait, and wait longer each time.
  • Don’t retry a 200 with status: false, a 401 or a 402 until you fix the cause.
  • For a 429, wait until the account’s limit resets. Get account limits shows what is left.
  • Before you retry a message that timed out, list the conversation’s messages. The first attempt may have been sent.