---
title: "DataForSEO Dataforseo Labs API / /v3/dataforseo_labs/google/related_keywords/live.ai"
description: "DataForSEO tool dataforseo-dataforseo-labs-google-related-keywords-live-ai 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 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 tre

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

## Inputs

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `depth` | number | no | keyword search depth |
| `filters` | array | no | Array-based filter expression. A single condition is a 3-element array: [field, operator, value]. Combine conditions with ["and"\|"or"] between them: [condition, "and", condition]. Max 8 filters. Operators: regex, not_regex, <, <=, >, >=, =, <>, in, not_in, match, not_match, ilike, not_ilike, like, not_like Use % with like/not_like/ilike/not_ilike as a wildcard. Examples: Single: ["keyword_data.keyword_info.search_volume", ">", 0] Combined: [["keyword_info.search_volume", "in", [0, 1000]], "an... |
| `include_clickstream_data` | boolean | no | Include or exclude data from clickstream-based metrics in the result |
| `keyword` | string | yes | target keyword |
| `language_code` | string | no | language code required field example: en |
| `language_name` | string | no | language name, e.g. 'English' |
| `limit` | number | no | Maximum number of keywords to return |
| `location_code` | integer | no | DataForSEO location code, e.g. 2840 for the United States |
| `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' |
| `offset` | number | no | offset in the results array of returned keywords optional field default value: 0 if you specify the 10 value, the first ten keywords in the results array will be omitted and the data will be provided for the successive keywords |
| `order_by` | array | no | results sorting rules optional field you can use the same values as in the filters array to sort the results possible sorting types: asc, results will be sorted in the ascending order desc, results will be sorted in the descending order you should use a comma to set up a sorting type example: ["keyword_data.keyword_info.competition,desc"] default rule: ["keyword_data.keyword_info.search_volume,desc"] note that you can set no more than three sorting rules in a single request you should use a... |

## Output

Shape of the run's `result`, checked against 1 real answer:

```txt
{ id, items: { depth, keyword_data: { keyword, serp_info: { ... }, keyword_info:... ...
```

The shape is cut here. Signed in, `looot inspect dataforseo-dataforseo-labs-google-related-keywords-live-ai` 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":"dataforseo-dataforseo-labs-google-related-keywords-live-ai","input":{"keyword":"<keyword>"},"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-ai",
    input: {
      keyword: "<keyword>",
    },
    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-ai",
        "input": {
            "keyword": "<keyword>",
        },
        "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-ai` as `endpointId`; see [the job page](/reference/jobs/dataforseolabs-google-related-keywords-live-ai).