Errors

Evade returns errors in a consistent envelope:

{
  "success": false,
  "error": {
    "code": "solve_failed",
    "message": "terminal semantic report: semantic attribution incomplete",
    "challenge_variant_id": "4c9510e5f1f417514a5255fedc48b891d66eecf1f8ea483c30d25be846f8c1d8"
  }
}

challenge_variant_id is included for solve failures when the challenge is known. It is diagnostic metadata, not an input to a later solve.

Status	Code	Meaning
`400`	`invalid_request`	JSON or a field is invalid, or a session is no longer active.
`401`	`missing_api_key`	The authorization header is missing.
`401`	`invalid_api_key`	The key is malformed, invalid, expired, or revoked.
`403`	`insufficient_scope`	The key lacks `solve`, or lacks `debug` for a debug solve.
`408`	`solve_canceled`	The caller canceled the request.
`429`	`quota_exceeded`	The key exhausted its current solve quota window.
`502`	`solve_failed`	Upstream acquisition or challenge generation failed.
`503`	`quota_unavailable`	Quota enforcement is temporarily unavailable.
`503`	`usage_unavailable`	Required usage recording is temporarily unavailable.
`504`	`solve_timeout`	The solve exceeded the server deadline.

Retry guidance

Correct 400, 401, and 403 requests before retrying.
For 429, wait until X-RateLimit-Reset.
Start a fresh solve when a session ID is no longer active.
Retry transient 502, 503, or 504 responses with bounded backoff and a healthy proxy.
Branch on error.code; message text is diagnostic and may evolve.

Overview

Shape

DataDome

Retry guidance

​Retry guidance

Retry guidance