API Reference
Errors
402 is expected. Pay and retry. It is not a tool failure.
| What happened | HTTP from us | Where it appears |
|---|---|---|
| No / invalid payment | 402 | Response; pay and retry |
| Batch larger than the tool allows | 400 | {"error":{"code":"batch_too_large","n","max_n","tool_id"}} before pay |
Bad JSON, or both url and items[] | 400 | error.code is invalid_body |
| Target 401/403 — Check URL Status | 200 | data.status_code, ok: false |
| Target 401/403 — Web Content/Index Cleaner | 200 | Item error: fetch_failed |
| Target 401/403 — Metadata / Link Extractor | 200 | Item error: fetch_failed. The page is not parsed. |
| Fetched HTML over 32,000,000 bytes (clean / extract) | 200 | Item error: too_large |
| Request timed out | 504 | Retry with a smaller batch |
Email role_based, dns_timeout, dns_error | 200 | valid: true and detail |
| Email format / disposable / no MX | 200 | valid: false and detail |
Retry 402 after paying. Retry 504 with a smaller batch. Change the request for 400 / too_large. A target-site 403 is that page blocking the fetch, not our API being down.
Also true: no JS render (server HTML only). Empty Link Extractor page is item error no_links. Clean with no extractable body is item no_main_content, still HTTP 200.