Skip to content

Error codes

Deploy API v1 endpoints return error responses as RFC 9457 Problem Details. Each error response includes an error code described on this page.

code HTTP status Meaning
invalid_request_error 400 The request was malformed or failed validation.
authentication_error 401 The API credentials are missing or invalid.
permission_error 403 The credentials are valid but not allowed for this action.
not_found_error 404 The requested resource does not exist.
conflict_error 409 The request conflicts with the current state.
contact_exists 409 A contact with that email already exists.
operation_in_progress 409 A previous operation is still running; retry later.
api_error 500 An unexpected error occurred.

400 Bad Request. The request body or a query parameter failed validation: an unknown contact attribute, an invalid value, or a missing required field. The errors array identifies each offending field.

401 Unauthorized. The request did not include a valid API key. Include your API key as a bearer token in the authorization header.

403 Forbidden. The credentials are valid but lack access to the requested resource or action.

404 Not Found. The resource does not exist.

409 Conflict. The request cannot be applied because it conflicts with the current state of the resource.

409 Conflict. A contact with the given email already exists. Update the existing contact instead of creating a new one.

409 Conflict. A previous bulk operation for the account is still running. The response includes a Retry-After header indicating how many seconds to wait before retrying.

500 Internal Server Error. An unexpected error occurred. The request can be retried.