---
title: "DataForSEO API documentation / /v3/dataforseo_labs/google/related_keywords/live"
description: "DataForSEO tool dataforseo-dataforseo-labs-google-related-keywords-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 Related Keywords endpoint provides keywords appearing in the “Searches Related to” SERP element. View the element. You can get up to 4680 keyword ideas by specifying the search depth. Each related keyword comes with the list of relevant product categories, search volume rate for the last month, search volume trend for the previous 12 months, as well as current cost-per-click and competition values.

- **Tool id:** `dataforseo-dataforseo-labs-google-related-keywords-live`
- **Provider:** [DataForSEO](/providers/dataforseo)
- **Job:** [Live dataforseolabs google related keywords](/reference/jobs/dataforseolabs-google-related-keywords-live) (`dataforseolabs.google.related-keywords.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; send one of language_name / language_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, depth, limit, keyword, se_type, function, language_code, location_code }, path: string[], time, result: { items: { ... }[], se_type, items_count, total_count, seed_keyword, language_code, location_code, seed_keyword_data }[], 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-related-keywords-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-related-keywords-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-related-keywords-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.related-keywords.live` as `endpointId`; see [the job page](/reference/jobs/dataforseolabs-google-related-keywords-live).