Skip to Content
EIS
Getting started with the API

API Errors

Manage errors declared by each operation

When a body is present, the APIs normally return this format:

{
  "status": "BAD_REQUEST",
  "message": "Descrizione dell'errore",
  "errors": "Dettagli dell'errore"
}
  • status is the name of the HTTP status, for example BAD_REQUEST o NOT_FOUND.
  • message contains a readable description of the error.
  • errors contains details and can be a string, a list of validation errors or a structured object.

See the single reference operation for specific statuses and examples. Some content-free answers do not include a body.

Status of error

StatusGeneral meaningIndication
400Request or invalid parametersCorrect the sent data before retrying.
401API credentials not validVerification clientId and clientSecret.
403Non-allowed operationCheck user permissions.
404Resource not foundCheck identifiers and parameters.
409Conflict with current stateUpgrade your data or resource status before retrying.
500Internal errorKeep the technical context and contact assistance if it persists.
502Error of an external serviceTry again later or contact assistance.
503Temporarily unavailable serviceWait and try again.

Example: already active number

POST /v1/numbers/activate Returns 400 Bad Request when the number is already active or has been deleted:

{
  "status": "BAD_REQUEST",
  "message": "Number already active or deleted",
  "errors": "Number already active or deleted"
}

Diagnostics

When signaling a problem, include timestamps, environment, HTTP method, path and status received. Anonymizes the payload and not share API key, access tokens or personal data.

Perform automatic retry only when you know the imperceptibility of the operation and you can exclude that a writing has already been applied.