Reference

Errors

Errors are deliberately generic. You see a short, stable code you can act on and a request_id to quote to support — never our internal reason.

Which connector, which defense, and which stage failed stays in your dashboard, keyed by the same request_id. Your integration never has to parse infra detail.

Error

{
  "error": {
    "code": "extraction_failed",
    "message": "We couldn't complete this extraction. If it persists, contact support with this request id.",
    "request_id": "req_a1b2c3",
    "retryable": true
  }
}

Error codes

Code	HTTP	Meaning
`invalid_request`	400	A field is missing or malformed.
`unauthorized`	401	Missing or invalid API key.
`quota_exceeded`	402	Out of credits for the period.
`unsupported`	422	Connector or operation not available.
`session_invalid`	422	The session is no longer valid — refresh it.
`rate_limited`	429	Too many requests. Back off and retry.
`extraction_failed`	502	We couldn't complete it. Usually retryable.
`temporarily_unavailable`	503	A target is degraded right now. Retry later.