Troubleshooting
Find the cause before you retry.
A practical checklist for authentication failures, queued requests, unsupported options, and validation errors.
5 min read
401 or 403: check your identity
Sign in again if your session expired. For API calls, check X-API-Key and make sure the key is active. A 403 can mean your email needs verification or the route requires an administrator. Never share a token with support.
402 or 429: check your limits
402 indicates insufficient credits. 429 can mean rate, active-job, or key allowance limits. Wait for active work to finish before retrying and reduce concurrent submissions. Do not create multiple accounts or keys to bypass a limit.
202: keep the job ID
Continue polling the existing job instead of submitting duplicate work. For asynchronous submissions, reuse an Idempotency-Key when retrying the same body. A changed body under the same key can return 409.
501 or 502: inspect the requested result
501 means a requested capability is not enabled; remove that option or inspect GET /v1/capabilities. 502 means scraping or validation failed and the failed result is not charged. Check your URL, selectors, and required fields. The current MVP uses simulated target responses.
503: check service availability
Open the system status page, allow a short recovery period, and try again with bounded backoff. For a persistent issue, send the request ID, approximate UTC time, HTTP status, and a redacted description to support.
KEEP BUILDING