Errors

New Venue Data uses conventional HTTP status codes to indicate the success or failure of a request. Every error response includes a machine-readable code, a human-readable message, and the X-Request-ID header so you can reference the request when contacting support.

json

{
  "error": {
    "code": "validation_error",
    "message": "filed_after must be an ISO 8601 date",
    "param": "filed_after"
  },
  "requestId": "req_01HZ8XQ9P2WKRN4M5YJVD3B"
}

Error Codes

Status	Code	When it happens	How to fix
400	invalid_request	The request was malformed — unparseable JSON body, an unknown query parameter, or a wrong data type.	Check the request shape against the endpoint reference and resend.
401	unauthorized	The API key is missing, malformed, or no longer valid.	Send a valid key in the Authorization: Bearer header. Rotate a revoked key from the dashboard.
403	forbidden	The key is valid but your plan does not include the requested resource or field (e.g. enrichment fields on Starter).	Upgrade your plan or remove the out-of-scope parameter from the request.
404	not_found	The requested record or route does not exist — e.g. an unknown license ID or a stale pagination cursor.	Verify the ID or path. Re-fetch a fresh cursor if the old one has expired.
422	validation_error	The request is well-formed but a parameter value failed validation, such as a bad date or an out-of-range limit.	Inspect the param field in the response and correct the offending value.
429	rate_limited	You exceeded the rate limit for your plan within the rolling 60-second window.	Back off and retry after the number of seconds in the Retry-After header.
500	internal_error	An unexpected error occurred on our side while processing the request.	Retry with backoff. If it persists, contact support with the X-Request-ID.
503	service_unavailable	The API is temporarily down for maintenance or overloaded.	Retry after a short delay using exponential backoff. Check the status page for incidents.

Was this page helpful?