Skip to main content
POST
Reference example
New and lost backlinks and referring domains for one target per period, grouped by group_range. Measured at 1.4 KB for three monthly points. Wrapped in DataForSEO’s envelope: data in tasks[0].result, outcome in tasks[0].status_code - a rejected request still returns HTTP 200. This is the derivative of post_dataforseo_backlinks_timeseries_summary_live: that one gives the level, this one the change. A flat total hiding heavy churn only shows up here. For the same figures across many targets at once use post_dataforseo_backlinks_bulk_new_lost_backlinks_live. This one takes no limit parameter, so the only lever is calling it less often.

Example

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.
Set this endpoint up in your agent →

Cost and request rules

Published reference values are not an account-specific quote or a settled charge. For endpoints supporting X-AISA-Cost-Mode: quote, obtain a free quote for your exact request before execution; reconcile the settled cost with response metadata and Usage Logs. USD amounts use 1,000,000 integer micro-USD per dollar.
  • Default request reference estimate (USD): 0.0372
  • Cost contract: response_usd
  • Published reference multiplier: 1.0
  • Settlement evidence source: response_body

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json
target
string

domain to get data for
required field
a domain should be specified without https:// and www.
example:
"forbes.com"

date_from
string | null

starting date of the time range
optional field
this field indicates the date which will be used as a threshold for new and lost backlinks and referring domains;
the backlinks and referring domains that appeared in our index after the specified date will be considered as new;
the backlinks and referring domains that weren't found after the specified date, but were present before, will be considered as lost;

minimum value: 2019-01-30
maximum value shouldn't exceed the date specified in the date_to
date format: "yyyy-mm-dd"
example:
"2021-01-01"

date_to
string | null

ending date of the time range
optional field
if you don't specify this field, the today's date will be used by default
minimum value shouldn't preceed the date specified in the date_from
maximum value: today's date
date format: "yyyy-mm-dd"
example:
"2021-01-15"

group_range
string | null

time range which will be used to group the results
optional field
default value: month
possible values: day, week, month, year

note: for day, we will return items corresponding to all dates between and including date_from and date_to;
for week/month/year, we will return items corresponding to full weeks/months/years, where each item will indicate the last day of the week/month/year

for example, if you specify:
"group_range": "month","date_from": "2022-03-23","date_to": "2022-05-13"
we will return items falling between 2022-03-01 and 2022-05-31, namely, three items corresponding to the following dates: 2022-03-31, 2022-04-30, 2022-05-31

if there is no data for a certain day/week/month/year, we will return 0

include_subdomains
boolean | null

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

tag
string | null

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

Example:

Response

object | null

Successful operation

version
string | null

the current version of the API

status_code
integer | null

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

status_message
string | null

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

time
string | null

total execution time, seconds

cost
number<double> | null

total tasks cost, USD

tasks_count
integer<int64> | null

the number of tasks in the tasks array

tasks_error
integer<int64> | null

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

tasks
(object | null)[] | null

array of tasks