> ## Documentation Index
> Fetch the complete documentation index at: https://aisa.one/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# Referring Domains
> Referring Domains
The domains linking to one `target`, one row per domain with `domain`, `rank`, `backlinks`, `first_seen`, `lost_date`, `backlinks_spam_score`, `broken_backlinks` and `broken_pages`. Measured at 1.3 KB. Wrapped in DataForSEO's envelope: data in `tasks[0].result`, outcome in `tasks[0].status_code` - a rejected request still returns HTTP 200. Referring domains matter more than raw backlink count, since a thousand links from one domain is one relationship. For the individual links use `post_dataforseo_backlinks_backlinks_live`; to collapse further, to network operators, use `post_dataforseo_backlinks_referring_networks_live`. Keep `limit` low and do not loop.
## Example
```bash REST theme={null}
curl -X POST "https://api.aisa.one/apis/v1/dataforseo/backlinks/referring_domains/live" \
-H "Content-Type: application/json" \
-H "Authorization: Bearer YOUR_API_KEY" \
-d '[{"target": "...", "limit": "...", "offset": "..."}]'
```
```jsonc MCP theme={null}
// Copy this whole block into Claude Code, Codex, Cursor or any coding agent.
// It carries everything needed to connect, authorize and run this example —
// no key to paste, one click of Allow in the browser.
{
"operation_id": "post_dataforseo_backlinks_referring_domains_live",
"arguments": {},
"max_price_usd": 0.05
}
// ── for the agent ─────────────────────────────────────────────────────────
// Register the AIsa MCP server, then call its `use` tool with the JSON above.
// name aisa
// endpoint https://mcp.aisa.one/mcp
// transport streamable-http
// auth OAuth. The server publishes RFC 9728 metadata, so open a
// browser and the user clicks Allow once — nothing to paste.
// If AISA_API_KEY is set, send it as a bearer header instead.
// Use your own MCP mechanism, not a hand-edited config file:
// Codex codex mcp add aisa --url https://mcp.aisa.one/mcp
// Claude Code claude mcp add --transport http -s user aisa https://mcp.aisa.one/mcp
// Cursor / VS Code a "url" entry for https://mcp.aisa.one/mcp in the MCP config
// The server lists five tools over https://mcp.aisa.one/servers worth of APIs:
// search, get_details, use, batch_use, list_categories. search and
// get_details are free; use is billed per call and max_price_usd refuses
// anything above the cap before spending. This operation's full contract —
// every argument, the response shape, the price and the pitfalls — is at
// https://aisa.one/docs/api-reference/dataforseo/post_dataforseo-backlinks-referring-domains-live.md
// Then run the call and show me the result.
```
**First time?** Point any MCP client at `https://mcp.aisa.one/mcp` — Claude
Code, Codex, Cursor, VS Code and the rest. Authorization is OAuth: the client
opens a browser, you click Allow once, and there is no key to paste. The
commands per client, and what each call costs, are on
[aisa.one/mcp](https://aisa.one/mcp#connect).
[Set this endpoint up in your agent →](https://aisa.one/mcp?from=/api-reference/dataforseo/post_dataforseo-backlinks-referring-domains-live)
## OpenAPI
````yaml openapi/dataforseo.json POST /dataforseo/backlinks/referring_domains/live
openapi: 3.0.3
info:
title: DataForSEO API
version: 1.0.0
description: DataForSEO API endpoints exposed through the AIsa unified gateway.
servers:
- url: https://api.aisa.one/apis/v1
security:
- BearerAuth: []
paths:
/dataforseo/backlinks/referring_domains/live:
post:
summary: Referring Domains
description: >-
This endpoint will provide you with a detailed overview of referring
domains pointing to the target you specify.
operationId: post_dataforseo_backlinks_referring_domains_live
requestBody:
required: true
content:
application/json:
schema:
type: array
items:
type: object
properties:
target:
type: string
description: >-
domain, subdomain or webpage to get referring domains for
required field a domain or a subdomain should be specified
without https:// and www. a page should be specified with
absolute URL (including http:// or https://)
limit:
type: integer
description: >-
the maximum number of returned domains optional field
default value: 100 maximum value: 1000
offset:
type: integer
description: >-
offset in the results array of returned domains optional
field default value: 0 if you specify the 10 value, the
first ten domains in the results array will be omitted and
the data will be provided for the successive pages
internal_list_limit:
type: integer
description: >-
maximum number of elements within internal arrays optional
field you can use this field to limit the number of
elements within the following arrays: referring_links_tld
referring_links_types referring_links_attributes
referring_links_platform_types
referring_links_semantic_locations default value: 10
maximum value: 1000
backlinks_status_type:
type: string
description: >-
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 target;
possible values: all – all backlinks will be returned and
counted; live – backlinks found during the last check will
be returned and counted; lost – lost backlinks will be
returned and counted; default value: live
filters:
type: array
items: {}
description: >-
array of results filtering parameters optional field you
can add several filters at once (8 filters maximum) you
should set a logical operator and, or between the
conditions the following operators are supported: regex,
not_regex, =, , in, not_in, like, not_like, match,
not_match you can use the % operator with like and
not_like to match any string of zero or more characters
example: ["referring_pages",">","1"]
[["referring_pages",">","2"], "and",
["backlinks",">","10"]] [["first_seen",">","2017-10-23
11:31:45 +00:00"], "and",
[["domain","like","%dataforseo.com%"],"or",["referring_domains",">","10"]]]
The full list of possible filters is available here.
order_by:
type: array
items:
type: string
description: >-
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: ["backlinks,desc"] 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: ["backlinks,desc","rank,asc"]
backlinks_filters:
type: array
items: {}
description: >-
filter the backlinks of your target optional field you can
use this field to filter the initial backlinks that will
be included in the dataset for aggregated metrics for your
target you can filter the backlinks by all fields
available in the response of this endpoint using this
parameter, you can include only dofollow backlinks in the
response and create a flexible backlinks dataset to
calculate the metrics for example: "backlinks_filters":
["dofollow", "=", true]
include_subdomains:
type: boolean
description: >-
indicates if the subdomains of the target will be included
in the search optional field if set to false, the
subdomains will be ignored default value: true
include_indirect_links:
type: boolean
description: >-
indicates if indirect links to the target will be included
in the results optional field if set to true, the results
will include data on indirect links pointing to a page
that either redirects to the target, or points to a
canonical page if set to false, indirect links will be
ignored default value: true
exclude_internal_backlinks:
type: boolean
description: >-
indicates whether the backlinks from subdomains of the
target are excluded optional field if set to false, the
backlinks from subdomains of the target will be ommited
and you won’t receive the same domain in the response;
default value: true
rank_scale:
type: string
description: >-
defines the scale used for calculating and displaying the
rank, domain_from_rank, and page_from_rank values optional
field you can use this parameter to choose whether rank
values are presented on a 0–100 or 0–1000 scale possible
values: one_hundred — rank values are displayed on a 0–100
scale one_thousand — rank values are displayed on a 0–1000
scale default value: one_thousand learn more about how
this parameter works and how ranking metrics are
calculated in this Help Center article
tag:
type: string
description: >-
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 tag value in the data object of the response
required:
- target
responses:
'200':
description: Successful operation
content:
application/json:
schema:
type: object
properties:
version:
type: string
description: the current version of the API
status_code:
type: integer
description: >-
general status code you can find the full list of the
response codes here
status_message:
type: string
description: >-
general informational message you can find the full list
of general informational messages here
time:
type: string
description: total execution time, seconds
cost:
type: number
description: total tasks cost, USD
tasks_count:
type: integer
description: the number of tasks in the tasks array
tasks_error:
type: integer
description: >-
the number of tasks in the tasks array returned with an
error
tasks:
type: array
items:
type: string
description: array of tasks
tasks.id:
type: string
description: >-
task identifier unique task identifier in our system in
the UUID format
tasks.status_code:
type: integer
description: >-
status code of the task generated by DataForSEO; can be
within the following range: 10000-60000 you can find the
full list of the response codes here
tasks.status_message:
type: string
description: >-
informational message of the task you can find the full
list of general informational messages here
tasks.time:
type: string
description: execution time, seconds
tasks.cost:
type: number
description: total tasks cost, USD
tasks.result_count:
type: integer
description: number of elements in the result array
tasks.path:
type: array
items:
type: string
description: URL path
tasks.data:
type: object
description: >-
contains the same parameters that you specified in the
POST request
tasks.result:
type: array
items:
type: string
description: array of results
tasks.result.target:
type: string
description: target in a POST array
tasks.result.total_count:
type: integer
description: >-
total number of relevant items in the database total
number of main domains referring to your target;
example.com and blog.example.com are counted as one
referring domain
tasks.result.items_count:
type: integer
description: number of items in the items array
tasks.result.items:
type: array
items:
type: string
description: items array
tasks.result.items.type:
type: string
description: type of element
tasks.result.items.domain:
type: string
description: referring domain
tasks.result.items.rank:
type: integer
description: >-
domain rank rank volume that a referring website passes to
the target rank is calculated based on the method for node
ranking in a linked database – a principle used in the
original Google PageRank algorithm learn more about the
metric and how it is calculated in this help center
article
tasks.result.items.backlinks:
type: integer
description: indicates the number of backlinks pointing to the target
tasks.result.items.first_seen:
type: string
description: >-
date and time when our crawler found the backlink for the
first time in the UTC format: “yyyy-mm-dd hh-mm-ss +00:00”
example: 2019-11-15 12:57:46 +00:00
tasks.result.items.lost_date:
type: string
description: >-
date and time when the last backlink from this domain was
lost indicates the date and time when our crawler visited
the page and it responded with 4xx or 5xx status code or
the last backlink was removed in the UTC format:
“yyyy-mm-dd hh-mm-ss +00:00” example: 2017-01-24 13:20:59
+00:00
tasks.result.items.backlinks_spam_score:
type: integer
description: >-
average spam score of all backlinks pointing to the domain
learn more about how the metric is calculated on this help
center page
tasks.result.items.broken_backlinks:
type: integer
description: >-
number of broken backlinks number of broken backlinks
pointing to the domain
tasks.result.items.broken_pages:
type: integer
description: >-
number of broken pages number of pages that respond with
4xx or 5xx status codes where backlinks are pointing to
tasks.result.items.referring_domains:
type: integer
description: >-
indicates the number of referring domains note that we
calculate main domains (root domains, like example.com)
and their subdomains (e.g. blog.example.com) separately
for this metric
tasks.result.items.referring_domains_nofollow:
type: integer
description: >-
number of domains pointing at least one nofollow link to
the target
tasks.result.items.referring_main_domains:
type: integer
description: >-
indicates the number of referring main domains the number
of primary (root) domains referring to your target
tasks.result.items.referring_main_domains_nofollow:
type: integer
description: >-
number of main domains pointing at least one nofollow link
to the target
tasks.result.items.referring ips:
type: integer
description: >-
number of referring IP addresses number of IP addresses
pointing to this page
tasks.result.items.referring subnets:
type: integer
description: number of referring subnetworks
tasks.result.items.referring_pages:
type: integer
description: >-
indicates the number of pages pointing to the target
specified
tasks.result.items.referring_links_tld:
type: object
description: >-
top-level domains of the referring links contains top
level domains and referring link count per each
tasks.result.items.referring_links_types:
type: object
description: >-
types of referring links indicates the types of the
referring links and link count per each type possible
values: anchor, image, link, meta, canonical, alternate,
redirect
tasks.result.items.referring_links_attributes:
type: object
description: >-
link attributes of the referring links indicates link
attributes of the referring links and link count per each
attribute
tasks.result.items.referring_links_platform_types:
type: object
description: >-
types of referring platforms indicates referring platform
types and link count per each platform possible values:
cms, blogs, ecommerce, message-boards, wikis, news,
organization
tasks.result.items.referring_links_semantic_locations:
type: object
description: >-
semantic locations of the referring links indicates
semantic elements in HTML where the referring links are
located and the link count per each semantic location you
can get the full list of semantic elements here examples:
article, section, summary
tasks.result.items.referring_links_countries:
type: object
description: >-
ISO country codes of the referring links indicates ISO
country codes of the domains where the referring links are
located and the link count per each country
tasks.result.items.referring_pages_nofollow:
type: integer
description: >-
number of referring pages pointing at least one nofollow
link to the target
'400':
description: Bad request
'401':
description: Unauthorized
'429':
description: Rate limit exceeded
'500':
description: Internal server error
components:
securitySchemes:
BearerAuth:
type: http
scheme: bearer
````
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.