---
title: "DataForSEO Dataforseo Labs API / /v3/dataforseo_labs/google/domain_intersection/live.ai"
description: "DataForSEO tool dataforseo-dataforseo-labs-google-domain-intersection-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. */}

This endpoint will provide you with the keywords for which both specified domains rank within the same SERP. You will get search volume, competition, cost-per-click and impressions data on each intersecting keyword. Along with that, you will get data on the first and second domain's SERP element di

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

## Inputs

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `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, &lt;, &lt;=, &gt;, &gt;=, =, &lt;&gt;, 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", "in", [100, 1000]] Combined: [["first_domain_serp_element.etv", "&gt;", 0]... |
| `ignore_synonyms` | boolean | no | ignore highly similar keywords, if set to true, results will be more accurate |
| `include_clickstream_data` | boolean | no | Include or exclude data from clickstream-based metrics in the result |
| `intersections` | boolean | no | domain intersections in SERP optional field if you set intersections to true, you will get the keywords for which both target domains specified as target1 and target2 have results within the same SERP; the corresponding SERP elements for both domains will be provided in the results array Note: this endpoint will not provide results if the number of intersecting keywords exceeds 10 million if you specify intersections: false, you will get the keywords for which the domain specified as target1... |
| `item_types` | array | no | display results by item type indicates the type of search results included in the response |
| `language_code` | string | no | language code required field example: en |
| `limit` | number | no | Maximum number of keywords to return |
| `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 parameter 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... |
| `target1` | string | yes | target domain 1 |
| `target2` | string | yes | target domain 2 |

## Output

The run's `result` holds the provider's answer. Signed in, `looot inspect dataforseo-dataforseo-labs-google-domain-intersection-live-ai` prints its fields.

## 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-domain-intersection-live-ai","input":{"target1":"<target1>","target2":"<target2>"},"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-domain-intersection-live-ai",
    input: {
      target1: "<target1>",
      target2: "<target2>",
    },
    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-domain-intersection-live-ai",
        "input": {
            "target1": "<target1>",
            "target2": "<target2>",
        },
        "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.domain-intersection.live-ai` as `endpointId`; see [the job page](/reference/jobs/dataforseolabs-google-domain-intersection-live-ai).
