---
title: "Adyntel / Paid and organic keywords of a domain"
description: "Adyntel tool adyntel-domain-keywords on looot: input fields, $0.00642 per call, output shape, and code to run it with curl, JavaScript or Python."
sidebar:
  hidden: true
---

{/* Generated by scripts/generate-api-reference.mjs from data/api-reference.json. Do not edit. */}

Lists the keywords a domain ranks for organically and the ones it pays for on Google. Send company_domain; limit and language refine it.

- **Tool id:** `adyntel-domain-keywords`
- **Provider:** [Adyntel](/providers/adyntel)
- **Job:** [Get a domain's search traffic overview](/reference/jobs/keywords-domain-overview) (`keywords.domain.overview`)
- **Price:** $0.00642 per call. A call that fails at the provider costs $0.

## Inputs

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `company_domain` | string | yes | Company website (without www or http) |
| `language` | string | no | Language for keyword results |
| `limit` | integer | no | Number of results to return |

## Output

Shape of the run's `result`, checked against 2 real answers:

```txt
{ 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](/get-started/sign-in#use-the-token-in-scripts-and-agents) 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:

<CodeGroup>

```bash curl
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":"adyntel-domain-keywords","input":{"company_domain":"example.com"},"wait":30}'
```

```js JavaScript
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: "adyntel-domain-keywords",
    input: {
      company_domain: "example.com",
    },
    wait: 30,
  }),
});
const run = await response.json();
console.log(run.status, run.result);
```

```python Python
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": "adyntel-domain-keywords",
        "input": {
            "company_domain": "example.com",
        },
        "wait": 30,
    },
    timeout=90,
)
run = response.json()
print(run["status"], run.get("result"))
```

</CodeGroup>

To let looot pick among every provider of this job instead, send `job:keywords.domain.overview` as `endpointId`; see [the job page](/reference/jobs/keywords-domain-overview).