Skip to main content
Every error returns JSON in this shape: 
{
  "error": {
    "code":       "...",
    "message":    "...",
    "field":      "...",
    "request_id": "req_..."
  }
}
The field is set when an input is at fault and points at the bad path (e.g. filters.homeowner.gt). The request_id is always set — include it when contacting support.

​
Codes

HTTPCodeWhat happenedHow to fix
400BAD_REQUESTYour JSON is malformed or a required field is missing.Validate your JSON. Check the endpoint’s request body fields.
401UNAUTHENTICATEDMissing or invalid Authorization header.Confirm your key, the Bearer prefix, and that the key isn’t revoked.
403FORBIDDEN_SCOPEYour key is valid but doesn’t have permission for this endpoint.Ask the Data Driver team to add the missing scope.
403FORBIDDEN_TABLEYour key isn’t allowed to read this table.Request access for the table.
403FORBIDDEN_FIELDYour select includes a column you can’t see (e.g. PII you’re not cleared for).Remove the field from select, or request access.
404NOT_FOUNDUnknown table name or export id.Check the URL spelling. Tables come from GET /v1/datasets.
410EXPORT_EXPIREDThe export’s signed URL has aged out (>7 days).Re-create the export.
422INVALID_FILTERYou used an unknown column or unsupported operator.Check the response’s field. Verify against /schema.
422QUERY_TOO_BROADExport would exceed our row limit (10M default).Add narrower filters.
429RATE_LIMITEDYou’ve sent more requests than your limit allows.Wait. Check the Retry-After header for seconds to wait.
500INTERNAL_ERRORServer-side problem.Note the request_id in the response and contact us.