Skip to content
looot docs
Esc
↑↓navigate↵open⌘Jpreview
On this page

Batch web scrape

Run job:web.scrape.batch through the looot API: 1 provider, from $0.0018 per result. Inputs, prices, output shape and code for curl, JavaScript and Python.

Batch web scrape.

Job id web.scrape.batch, in Enrichment (Web data). As of 2026-10-07, 1 provider serve it through 1 tool. Run job:web.scrape.batch and looot picks one of them; with fallback on, a miss moves on to the next. See Jobs.

Inputs

This job has one tool, so it takes that tool’s fields. Any key you send passes through unchanged.

Name Type Required Description
country string no Country for the batch execution. Provide in ISO 3166-1 alpha-2 codes like US(USA), IN(India), etc
items array yes Array of items to be processed in the batch.
links_on_page object no Get all the links present on each page in the batch. Links are always returned as absolute URLs.
metadata object no Set of key-value pairs for storing additional information about an object. Follows Stripe’s approach with validation rules: max 50 keys, key max 40 characters (no square brackets), value max 500 characters, all values stored as strings.
parser object no You can use this parameter to specify the parser to use. Parsers are useful to extract structured content from web pages. Olostep has a few parsers built in for most common web pages, and you can also create your own parsers.
webhook string no HTTPS URL to receive a POST request when the batch completes. Must be a publicly accessible URL using http:// or https:// protocol. Cannot point to localhost or private IP addresses. See Webhooks for payload format and retry behavior.

Providers and prices

Provider Tool Price
Olostep olostep-batch-start $0.0018 per result

A call that fails at the provider costs $0. See What’s free.

Output

The run’s result holds the provider’s answer. Signed in, looot inspect olostep-batch-start prints its fields.

Run it

Every call needs your API token in LOOOT_TOKEN; Sign in shows how to get one. Each run also needs a new idempotency key, so a retry never pays twice. With wait: 30 the answer comes back inline when the run ends within 30 seconds. Otherwise you get the running run back: poll GET /v1/runs/<runId>.

Example input with placeholder values:

curl -X POST "https://api.looot.ai/v1/runs" \
  -H "Authorization: Bearer $LOOOT_TOKEN" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{"endpointId":"job:web.scrape.batch","input":{"items":[]},"wait":30}'
const response = await fetch("https://api.looot.ai/v1/runs", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.LOOOT_TOKEN}`,
    "Content-Type": "application/json",
    "Idempotency-Key": crypto.randomUUID(),
  },
  body: JSON.stringify({
    endpointId: "job:web.scrape.batch",
    input: {
      items: [],
    },
    wait: 30,
  }),
});
const run = await response.json();
console.log(run.status, run.result);
import os
import uuid

import requests

response = requests.post(
    "https://api.looot.ai/v1/runs",
    headers={
        "Authorization": f"Bearer {os.environ['LOOOT_TOKEN']}",
        "Idempotency-Key": str(uuid.uuid4()),
    },
    json={
        "endpointId": "job:web.scrape.batch",
        "input": {
            "items": [],
        },
        "wait": 30,
    },
    timeout=90,
)
run = response.json()
print(run["status"], run.get("result"))

To pin one provider, send its tool id as endpointId instead of job:web.scrape.batch. The shared input names above are for the job: run only; a tool id takes that tool’s own field names, listed on its page, and refuses the shared ones when they differ. For olostep-batch-start that is items.

Was this page helpful?