Docs · Getting started
Errors and retry strategy
Predictable error codes, a recommended retry pattern, and the request ID to quote in support tickets.
GET
/v1/* Every error response is JSON with a status of error or a clear detail message. Errors are stable: 401 means re-auth, 429 means wait, 5xx means retry with backoff.
Request ID. Every response, success or failure, carries an X-Request-ID header. When you file a support ticket, quoting this ID is the fastest way to get a useful answer. If you send an X-Request-ID header on the request, we echo it back so you can correlate your logs with ours. Otherwise we mint a fresh UUID and return that.
Request
# Failed scrape — note the X-Request-ID in headers:
# x-request-id: 4f2a7c8e1b9d4a3c8f5e6d2b1a3c4d5e
# Quote that ID when contacting [email protected].Response
{
"status": "error",
"url": "https://example.com",
"error": "Timeout after 30s",
"time_ms": 30042
}Errors
| Code | Meaning |
|---|---|
| 400 | Malformed request body or missing required field. |
| 401 | Auth failed — check your API key. |
| 404 | Resource (such as a job_id) not found. |
| 429 | Rate limit or monthly quota exceeded. |
| 500 | Upstream fetch failed. Retry with backoff. |
| 503 | Endpoint temporarily disabled. Check the status page. |