---
title: "DataForSEO API documentation / /v3/dataforseo_labs/google/keywords_for_site/live"
description: "DataForSEO tool dataforseo-dataforseo-labs-google-keywords-for-site-live on looot: input fields, $0.012 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. */}

‌ The Keywords For Site endpoint will provide you with a list of keywords relevant to the target domain. Each keyword is supplied with relevant categories, search volume data for the last month, cost-per-click, competition, and search volume trend values for the past 12 months.

- **Tool id:** `dataforseo-dataforseo-labs-google-keywords-for-site-live`
- **Provider:** [DataForSEO](/providers/dataforseo)
- **Job:** [Live dataforseolabs google keywords for site](/reference/jobs/dataforseolabs-google-keywords-for-site-live) (`dataforseolabs.google.keywords-for-site.live`)
- **Price:** $0.012 per call. A call that fails at the provider costs $0.

## Inputs

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `tasks` | array | yes | one task object per request; DataForSEO takes an array at the body root Required by DataForSEO: send one of location_name / location_code. |

## Output

Shape of the run's `result`, the expected shape, not yet checked against real answers:

```txt
{ cost, time, tasks: { id, cost, data: { api, limit, target, filters: string[], se_type, function, language_code, location_code, include_serp_info, include_subdomains }, path: string[], time, result: { items: unknown[], offset, target, se_type, items_count, total_count, language_code, location_code }[], status_code, result_count, status_message }[], version, status_code, tasks_count, tasks_error, status_message }
```

## 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":"dataforseo-dataforseo-labs-google-keywords-for-site-live","input":{"tasks":[]},"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: "dataforseo-dataforseo-labs-google-keywords-for-site-live",
    input: {
      tasks: [],
    },
    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": "dataforseo-dataforseo-labs-google-keywords-for-site-live",
        "input": {
            "tasks": [],
        },
        "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:dataforseolabs.google.keywords-for-site.live` as `endpointId`; see [the job page](/reference/jobs/dataforseolabs-google-keywords-for-site-live).