Scraper as API
Instead of a file, we expose the scraper behind an HTTP endpoint you call with parameters. Useful when your application needs fresh data on request.
Some use cases cannot wait for a scheduled run: a user types a product URL and expects the current price, or your system needs a company profile the moment a record is created. For those we deploy the scraper behind an authenticated endpoint. You send a request with the parameters, we fetch the live page through the anti-bot layer and return structured JSON. The scraper is the same one we would use for a dataset; only the way you call it changes.
In detail
One HTTPS endpoint per source, protected with an API key, taking the inputs the site needs: a URL, a search term, a location. Responses are JSON with the same field names as our file deliveries plus a fetch timestamp. Rate limits are agreed in the quote.
Endpoints run on our infrastructure or, if you prefer, as an Apify Actor you call through the Apify API with pay-per-result billing. Either way you get logs, retries and fingerprint rotation without running browsers or proxies yourself.
If you need thousands of records at once, a scheduled dataset is cheaper and gentler on the source than thousands of live calls. We tell you which fits and often combine both: bulk history by file, fresh lookups by API.
Schema
Starting point only. You name the columns; we keep the names stable across every run.
request_idinput_urlstatusfetched_atdatasource_latency_msQuestions
Setup is quoted like a project, from $500 per source, and running costs depend on call volume and the proxies the site needs. We give a per-thousand-calls estimate before you commit.
Most sources return in a few seconds, since each call fetches a live page through the protection in front of it. Cached responses for repeated inputs can be enabled if staleness of a few minutes is acceptable.
Yes. Many of our scrapers are published as Actors on the Apify platform; you call them through Apify's API and pay per result with no setup fee.
The endpoint returns an explicit error instead of bad data, and our checks page an engineer. The fix is covered under the maintenance part of the plan.
Related
Tell us the site and the fields. We build the scraper, run it, hand you the output and fix anything that breaks for 30 days. From $500 per site.
Scraped data is only useful once it is in your systems. Every job ends with delivery to a destination you already use, in a layout you can load without cleanup.
Send a URL and the fields you need. An engineer looks at it the same day and replies with a plan and a price.
Hi! Send me the site you need data from and I'll get an engineer to look at it.
Chat on WhatsApp Or get a quote