Async Job API for Web Scraping

Submit a job, get a job_id back in milliseconds, then poll the job (custom deployments can also push results to a webhook) - most jobs resolve in seconds. Batch endpoints take a list per call - up to 20 hotels on Google Hotels, up to 1,000 cells in one Rate Shop request - so a large sweep is a few requests, not one per item.

No. We absorb redesigns on our side and keep your field names and types stable - that contract is the whole point of a managed API. When a target adds data worth having, new fields are added alongside the old ones, never in place of them.

The job reports a clean, categorized failure instead of a mystery timeout - and it is not billed. Retries on fresh infrastructure happen automatically before a failure is ever reported to you.

A scoped deployment typically goes live as a production API in 48-72 hours. That includes the scraper itself, a wrapper API shaped to your workflow, custom fields added to the response, monitoring and alerting on our side, and a staging key so your team can validate the schema before production traffic starts.

That is our problem, not yours. Every source is monitored around the clock - layout changes, anti-bot updates and success-rate drops page our engineers before they page you, and your field names stay stable through redesigns because we absorb the change behind the schema. Failed requests are retried automatically, and anything that still fails is not billed: pricing is success-based.