Errors

Single-message errors

Most failures return an object with one error string:

{ "error": "workspace not found" }

Status	Meaning
400	The request couldn’t be interpreted, for example malformed JSON.
401	Missing, malformed, or expired bearer token. See Authentication.
402	The workspace’s subscription is inactive or a payment failed. The body also carries a `code` of `subscription_inactive` or `payment_failed`.
403	The user isn’t allowed to act on this workspace or resource.
404	The workspace or a referenced record doesn’t exist.
409	The record already exists or can’t be changed.
500	Something went wrong on our side. Retry with backoff, and email support if it persists.

Validation errors

When a request body fails validation the API returns 422 with a list of field errors:

[
  { "field": "From", "message": "must be a valid phone number" },
  { "field": "Text", "message": "must be at most 1200 characters" }
]

field is the field’s internal name, not the JSON key. From refers to the from property, MediaURL to mediaUrl, and so on. Fix every entry and resend. Validation stops the request before anything happens, so a 422 never has side effects.

An empty or unreadable JSON body returns 422 with a single object instead:

{ "message": "invalid JSON (EOF)" }

Getting started

API reference

Context lookups

Actions

Triggers

Errors

Single-message errors

Validation errors

​Errors

​Single-message errors

​Validation errors

Errors

Single-message errors

Validation errors