POST /v3/backlinks/domain_intersection/live – DataForSEO API documentation

Backlinks

Changed on Dec 14, 2025

‌ This endpoint will provide you with the list of domains pointing to the specified websites. This endpoint is especially useful for creating a Link Gap feature that shows what domains link to your competitors but do not link out to your website.

post/v3/backlinks/domain_intersection/live

Request

Base URL: https://api.dataforseo.com
URL: https://api.dataforseo.com/v3/backlinks/domain_intersection/live
Auth: HTTP basic

Request body

targetsobject nullable

domains, subdomains or webpages to get links for required field you can set up to 20 domains, subdomains or webpages a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code> a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>) example: "targets": { "1": "http://planet.postgresql.org/", "2": "http://gborg.postgresql.org/" }

exclude_targetsstring[] nullable

domains, subdomains or webpages you want to exclude optional field you can specify up to 10 domains, subdomains or webpages if you use this array, results will contain the referring domains that link to <code>targets</code> but don't link to <code>exclude_targets</code> example: "exclude_targets": [ "bbc.com", "https://www.apple.com/iphone/*", "https://dataforseo.com/apis/*"]

filtersobject[] nullable

array of results filtering parameters optional field you can add several filters at once (8 filters maximum) you should set a logical operator <code>and</code>, <code>or</code> between the conditions the following operators are supported: <code>regex</code>, <code>not_regex</code>, <code>=</code>, <code><></code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code>, <code>ilike</code>, <code>not_ilike</code>, <code>match</code>, <code>not_match</code> you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters example: <code>["1.internal_links_count",">","1"]</code><code>[["2.referring_pages",">","2"], "and", ["1.backlinks",">","10"]]</code><code>[["1.first_seen",">","2017-10-23 11:31:45 +00:00"], "and", [["2.target","like","%dataforseo.com%"],"or",["1.referring_domains",">","10"]]]</code>The full list of possible filters is available <a href="/v3/backlinks/filters/?bash" rel="noopener noreferrer" target="_blank">here.</a>

order_bystring[] nullable

results sorting rules optional field you can use the same values as in the <code>filters</code> array to sort the results possible sorting types: <code>asc</code> - results will be sorted in the ascending order <code>desc</code> - results will be sorted in the descending order you should use a comma to set up a sorting type example: <code>["backlinks,desc"]</code> note that you can set no more than three sorting rules in a single request you should use a comma to separate several sorting rules example: <code>["backlinks,desc","rank,asc"]</code>

offsetinteger nullable

offset in the array of returned results optional field default value: <code>0</code> if you specify the <code>10</code> value, the first ten backlinks in the results array will be omitted and the data will be provided for the successive backlinks

limitinteger nullable

the maximum number of returned results optional field default value: <code>100</code> maximum value: <code>1000</code>

internal_list_limitinteger nullable

maximum number of elements within internal arrays optional field you can use this field to limit the number of elements within the following arrays: <code>referring_links_tld</code> <code>referring_links_types</code> <code>referring_links_attributes</code> <code>referring_links_platform_types</code> <code>referring_links_semantic_locations</code>default value: <code>10</code> maximum value: <code>1000</code>

backlinks_status_typestring nullable

set what backlinks to return and count optional field you can use this field to choose what backlinks will be returned and used for aggregated metrics for your <code>targets</code>; possible values: <code>all</code> - all backlinks will be returned and counted; <code>live</code> - backlinks found during the last check will be returned and counted; <code>lost</code> - lost backlinks will be returned and counted;default value: <code>live</code>

backlinks_filtersobject[] nullable

filter the backlinks of your <code>target</code> optional field you can use this field to filter the initial backlinks that will be included in the dataset for aggregated metrics for your <code>target</code> you can filter the backlinks by all fields available in the response of <a href="/v3/backlinks/backlinks/live">this endpoint</a> using this parameter, you can include only dofollow backlinks in the response and create a flexible backlinks dataset to calculate the metrics for example: <code>"backlinks_filters": [["dofollow", "=", true]]</code>

include_subdomainsboolean nullable

indicates if the subdomains of the <code>target</code> will be included in the search optional field if set to <code>false</code>, the subdomains will be ignored default value: <code>true</code>

include_indirect_linksboolean nullable

indicates if indirect links to the <code>targets</code> will be included in the results optional field if set to <code>true</code>, the results will include data on indirect links pointing to a page that either redirects to a target, or points to a canonical page if set to <code>false</code>, indirect links will be ignored default value: <code>true</code>

exclude_internal_backlinksboolean nullable

indicates whether the backlinks from subdomains of the <code>target</code> are excluded optional field if set to <code>false</code>, the backlinks from subdomains of the <code>target</code> will be omitted and you won't receive the same domain in the response; default value: <code>true</code>

intersection_modestring nullable

indicates whether to intersect backlinks optional field use this field to intersect or merge results for the specified domains possible values: <code>all</code>, <code>partial</code> <code>all</code> - results are based on all backlinks; <code>partial</code> - results are based on the intersecting backlinks only; default value: <code>all</code>

rank_scalestring nullable

defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values optional fieldyou can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scalepossible values: <code>one_hundred</code> — rank values are displayed on a 0–100 scale <code>one_thousand</code> — rank values are displayed on a 0–1000 scaledefault value: <code>one_thousand</code>learn more about how this parameter works and how ranking metrics are calculated in <a href="https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale">this Help Center article</a>

tagstring nullable

user-defined task identifier optional field the character limit is 255 you can use this parameter to identify the task and match it with the result you will find the specified <code>tag</code> value in the <code>data</code> object of the response

Example request

[
  {
    "targets": {
      "1": "moz.com",
      "2": "ahrefs.com"
    },
    "include_subdomains": false,
    "exclude_targets": [
      "semrush.com"
    ],
    "limit": 5,
    "order_by": [
      "1.backlinks,desc"
    ],
    "exclude_internal_backlinks": true
  }
]

Response

Successful operation

versionstring nullable

the current version of the API

status_codeinteger nullable

general status code you can find the full list of the response codes here

status_messagestring nullable

general informational message you can find the full list of general informational messages here

timestring nullable

total execution time, seconds

costnumber double nullable

total tasks cost, USD

tasks_countinteger nullable

the number of tasks in the tasks array

tasks_errorinteger nullable

the number of tasks in the tasks array returned with an error

Changes

Dec 14, 2025be20fca9d9cc Revision changes
- info
  api operation id BacklinksDomainIntersectionLive removed and replaced with DomainIntersectionLive
Nov 28, 2025e73495840d61 Revision changes
- info
  api operation id DomainIntersectionLive removed and replaced with BacklinksDomainIntersectionLive

Operation history