Get a domain's search traffic overview

Run job:keywords.domain.overview through the looot API: 2 providers, from $0.00642 per call. Inputs, prices, output shape and code for curl, JavaScript and Python.

Get a domain’s search traffic overview.

Job id keywords.domain.overview, in Search & SERP (Keyword & trend data). As of 2026-10-01, 2 providers serve it through 2 tools. Run job:keywords.domain.overview and looot picks one of them; with fallback on, a miss moves on to the next. See Jobs.

Inputs

Fields the job’s tools take, most shared first. Any key you send passes through unchanged.

Name	Type	Taken by	Required by	Description
`company_domain`	string	1 of 2	1	Company website (without www or http)
`ignore_synonyms`	boolean	1 of 2	0	ignore highly similar keywords, if set to true, results will be more accurate
`language`	string	1 of 2	0	Language for keyword results
`language_code`	string	1 of 2	0	language code required field example: en
`limit`	integer	1 of 2	0	Number of results to return
`location_name`	string	1 of 2	0	full name of the location required field only in format “Country” (not “City” or “Region”) example: ‘United Kingdom’, ‘United States’, ‘Canada’
`target`	string	1 of 2	1	target domain. Example: “example.com”

Providers and prices

Provider	Tool	Price
Adyntel	`adyntel-domain-keywords`	$0.00642 per call
DataForSEO	`dataforseo-dataforseo-labs-google-domain-rank-overview-live-ai`	$0.012 per call

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

Output

Each provider answers in its own shape. Shape of the run’s result from adyntel-domain-keywords, checked against 2 real answers:

{ paid: { count, is_up, pos_1, is_new, is_down, is_lost, pos_2_3, pos_4_10, pos_11_20, pos_21_30, pos_31_40, pos_41_50, pos_51_60, pos_61_70, pos_71_80, pos_81_90, pos_91_100, estimated_traffic, estimated_ad_budget }, organic: { count, is_up, pos_1, is_new, is_down, is_lost, pos_2_3, pos_4_10, pos_11_20, pos_21_30, pos_31_40, pos_41_50, pos_51_60, pos_61_70, pos_71_80, pos_81_90, pos_91_100, estimated_traffic }, paid_percentages: {}, organic_percentages: { is_up, pos_1, is_new, is_down, is_lost, pos_2_3, pos_4_10, pos_11_20, pos_21_30, pos_31_40, pos_41_50, pos_51_60, pos_61_70, pos_71_80, pos... ...

The shape is cut here. Signed in, looot inspect adyntel-domain-keywords prints all of it.

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:keywords.domain.overview","input":{"company_domain":"example.com"},"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:keywords.domain.overview",
    input: {
      company_domain: "example.com",
    },
    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:keywords.domain.overview",
        "input": {
            "company_domain": "example.com",
        },
        "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:keywords.domain.overview.