Handling Errors

Errors return an HTTP status and a JSON body with an error code, message, and diagnostic code.

{
  "errorCode": "400-218",
  "errorMessage": "At least one company ID, keyword set ID, or keyword is required.",
  "diagnosticCode": "..."
}

Status codes

Status	Meaning
`400 Bad Request`	The request body, filter values, date range, sorting, or pagination token is invalid.
`401 Unauthorized`	The bearer token is missing, invalid, expired, or unsupported.
`403 Forbidden`	The API key set does not include access to the Intent API.
`429 Too Many Requests`	A rate or account quota has been reached. Reduce concurrency and retry after a delay.
`500 Internal Server Error`	An unexpected error occurred.
`503 Service Unavailable`	The service is temporarily unavailable.

Error code	Cause
`400-218`	No company IDs, keyword set IDs, or keywords were provided.
`400-219`	More than 10 company IDs were provided.
`400-220`, `400-221`	A date is missing or is not in `yyyy-MM-dd` format.
`400-222`	`startDate` is later than `endDate`.
`400-223`	The date range exceeds 12 months.
`400-224`	`intentStrength` contains an unsupported value.
`400-225`	The people-researching range is negative or the minimum exceeds the maximum.
`400-226`	`pageSize` is outside the 1–100 range.
`400-227`	A sorting value is unsupported.
`400-228`	The page token is invalid or expired.
`400-229`	More than 10 keyword set IDs were provided.
`400-230`	More than 50 keywords were provided.

Use errorMessage to correct a 400 response before retrying.
Refresh or replace the bearer token for 401 responses.
Ask your Demandbase administrator to verify Intent API access for 403 responses.
Retry 429 and transient 5xx responses with exponential backoff and jitter.
Include the diagnosticCode when contacting Demandbase Support.