Skip to main content
POST /v1/web/batch reads a list of URLs you give it, as one background job. There is no discovery: you choose exactly which pages. You get a batchId straight away, then poll it or let a webhook tell you as pages finish. 1 credit per page read.

Batch or crawl?

Batch

You give the URLs. Best when you already know which pages you want.

Crawl

We find the URLs from a starting page. Best for a whole site or section.

When to use it

  • You have a set of URLs, from your own data, a sitemap or a Map call, and want them all read in one job.
  • You want the same options applied to every URL.

Example

The batch starts at once:

Options

string[]
required
The URLs to read, from 1 to 25,000. Each must be http or https.
object
How to read each page. The same options as a Scrape, with formats limited to markdown, html, rawHtml, links and structured.
object
Have us call your URL as pages finish and when the job ends, instead of polling. See Jobs & webhooks.

Getting the results

Poll GET /v1/web/batch/{id}. It answers in the same shape as a crawl’s status, with kind set to batch and every page’s discoveredVia set to requested. Results stay available for 90 days after the batch last changes. After that the call answers 404.

Cost

1 credit per page read. Pages that fail are free. The job’s creditsUsed shows the total so far.

Next steps

Map a site

Get the URLs to send to a batch.

Crawl a whole site

When you want us to find the pages.

Jobs & webhooks

Polling, webhooks and checking deliveries.

API reference

The full schema, with a live playground.