Skip to main content
Save the HTTP status, error_code, request_id, and a redacted copy of the input. Compare the request with the endpoint reference before retrying.

​
Start with the response

​
Authentication and access

Send Authorization: Bearer <API_KEY> to https://api.context.dev/v1. A missing or unknown key can currently return 401 NOT_FOUND with an endpoint-not-found message; check the key before changing a valid route. For DISABLED, inspect the key in the dashboard. Free organizations can have all keys disabled after repeated failed requests; stop the retry loop and follow the account email or contact support. For USAGE_EXCEEDED, check the organization’s balance and billing settings. For INSUFFICIENT_PERMISSIONS, grant the required scope; repeated unchanged requests will still fail.

​
Empty and partial outputs

Scrape can return HTTP 200 with failed outputs. Empty successful text may mean selectors matched nothing. Inspect Scrape errors and verify page readiness. A Brand profile can have empty collections. People can return not_found or a weak candidate. Answers can have null facts. Handle these as product states rather than assuming every successful request contains complete data.

​
Target access and documents

WEBSITE_BLOCKED can mean an anti-bot page, CAPTCHA, or login shell. Confirm the URL and access requirements, then use a bounded recovery strategy. Avoid an unchanged retry loop. A scanned upload with OCR off returns PDF_IMAGES_ONLY from Parse. Scrape reports failed text outputs instead. See PDFs and OCR.

​
Async work

Batch results expire after seven days; expired signed links can be refreshed only while the files remain. After an idempotent submit returns a failed batch, inspect its failure code before submitting a new key. See batch errors. For missing monitor alerts, inspect runs, event subscriptions, delivery history, and retry configuration. Omitting webhook.retry requests best-effort delivery. See Webhooks.

​
Retry or report

Honor Retry-After, use bounded backoff for transient failures, and keep client timeouts longer than API deadlines. Report reproducible API or documentation issues through Agent feedback, or email [email protected] with the request ID.