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

Live ai dataforseolabs bulk traffic estimation

Run job:dataforseolabs.bulk-traffic-estimation.live-ai through the looot API: 1 provider, from $0.012 per call. Inputs, prices, output shape and code for curl, JavaScript and Python.

Live ai dataforseolabs bulk traffic estimation.

Job id dataforseolabs.bulk-traffic-estimation.live-ai, in Search & SERP (SEO keyword & domain research). As of 2026-10-01, 1 provider serve it through 1 tool. Run job:dataforseolabs.bulk-traffic-estimation.live-ai 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
ignore_synonyms boolean no ignore highly similar keywords, if set to true, results will be more accurate
item_types array no display results by item type indicates the type of search results included in the response
language_code string no language code required field example: en
location_name string no full name of the location required field only in format “Country” (not “City” or “Region”) example: ‘United Kingdom’, ‘United States’, ‘Canada’
targets array yes target domains, subdomains, and webpages. you can specify domains, subdomains, and webpages in this field; domains and subdomains should be specified without https:// and www.; pages should be specified with absolute URL, including https:// and www.; you can set up to 1000 domains, subdomains or webpages

Providers and prices

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 dataforseo-dataforseo-labs-bulk-traffic-estimation-live-ai 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:dataforseolabs.bulk-traffic-estimation.live-ai","input":{"targets":[]},"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:dataforseolabs.bulk-traffic-estimation.live-ai",
    input: {
      targets: [],
    },
    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:dataforseolabs.bulk-traffic-estimation.live-ai",
        "input": {
            "targets": [],
        },
        "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:dataforseolabs.bulk-traffic-estimation.live-ai.

Was this page helpful?