Errors

Error format

The API returns errors as JSON. The format depends on the endpoint type:

{
  "error": "Rate limit exceeded. Please try again later."
}

{
  "error": "rate limit exceeded"
}

Code	Name	When
`200`	OK	Request succeeded
`201`	Created	Resource created (monitors, lists, webhooks, API keys)
`202`	Accepted	Async operation queued (bulk jobs, monitor runs)
`204`	No Content	Delete succeeded
`400`	Bad Request	Invalid or missing request body/parameters
`401`	Unauthorized	Missing or invalid API key
`402`	Payment Required	Insufficient credits for the operation
`403`	Forbidden	Permission denied (wrong workspace role)
`404`	Not Found	Resource doesn’t exist
`405`	Method Not Allowed	Wrong HTTP method
`409`	Conflict	Resource already exists (duplicate)
`413`	Payload Too Large	Request body exceeds size limit (bulk operations)
`429`	Too Many Requests	Rate limit exceeded
`500`	Internal Server Error	Unexpected server failure
`502`	Bad Gateway	Upstream data provider failed
`503`	Service Unavailable	Required service not configured

Your API key is missing, invalid, or revoked.

{"error": "unauthorized"}

Fix: Check that your Authorization: Bearer <key> header is correct and the key hasn’t been revoked.

Your workspace has insufficient credits for the requested operation.

{"error": "Insufficient credits"}

Fix: Add credits in the dashboard billing page, or use free endpoints (validate, breaches) that don’t consume credits.

You’ve exceeded the request limit for this endpoint.

{"error": "Rate limit exceeded. Please try again later."}

The response includes headers to help you retry:

Header	Description
`X-RateLimit-Limit`	Maximum requests allowed in the window
`X-RateLimit-Remaining`	Requests remaining in current window
`X-RateLimit-Reset`	Unix timestamp when the window resets
`Retry-After`	Seconds until you can retry

See Rate Limits for full details.

An upstream data provider (search engine or breach database) failed to respond.

{"error": "upstream provider failed"}

Fix: Retry after a short delay. These are transient and typically resolve within seconds.