Error handling

Available error codes

Status	Description
400	Bad request. The request or the request body is invalid. Examples: missing required fields, invalid field format.
401	Unauthorized. The request requires authentication. This usually means the API key is missing or invalid.
402	Insufficient credits. You do not have enough credits to perform this request. See Credit usage for more information.
403	Forbidden. The request is not allowed. This may be due to insufficient privileges or attempting to access resources belonging to another user.
404	Not found. The requested resource does not exist. This could be due to an incorrect ID or an invalid endpoint.
429	Too many requests. You have exceeded the rate limit. See Rate limiting for more information.
500	Internal server error. Something went wrong on our side. If this persists, please contact support with the request details so we can investigate.

Error format

v2 errors always include a message field, but the response envelope otherwise mirrors the shape of a successful response for that endpoint — fields such as the entity identifier (e.g. companyIdentifier, legalEntityIdentifier) and data (and, where applicable, endpoint-specific fields like pagination or range) are present but set to null.

Companies

{
  "companyIdentifier": null,
  "data": null,
  "message": "Company not found"
}

Legal Entities

{
  "legalEntityIdentifier": null,
  "data": null,
  "message": "Legal entity not found"
}

Lists Exports / Agents

{
  "data": null,
  "message": "List not found"
}

Getting Started

V2 API

V1 API

Available error codes

Error format

​Available error codes

​Error format

Available error codes

Error format