Errors

When a request returns an error we always try to provide a clear explanation of what went wrong.

Errors are returned as json files and follow the same structure:

{
  status: "error",
  message: "Error explanation" // Eg: "Missing API token"
  code: "error_code" // Eg: no_token
}

Status
Our API raises errors for many reasons and when this happens the "status" attribute will always be "error".
We recommend writing code that gracefully handles all possible API exceptions.

Message
A human-readable message providing more details about the error. 

Code
The type of error returned. Can be:  no_token,  no_list_uuid,  api_connection_error,  invalid_list_or_token,   no_email_address,  invalid_email_address,  no_hosting_url,  subscriber_already_exist,  too_many_calls,   subscriber_not_found,  no_code,  no_position,  no_points,  subscriber_already_promoted

Still need help? Contact Us Contact Us