> ## 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.
# New & Lost Backlinks Timeseries Summary
> New and lost backlinks and referring domains for one target per period, grouped by group_range.
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
```bash REST theme={null}
curl -X POST "https://api.aisa.one/apis/v1/dataforseo/backlinks/timeseries_new_lost_summary/live" \
-H "Content-Type: application/json" \
-H "Authorization: Bearer YOUR_API_KEY" \
-d '[{"target": "...", "date_from": "...", "date_to": "..."}]'
```
```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_timeseries_new_lost_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-timeseries-new-lost-summary-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-timeseries-new-lost-summary-live)
## OpenAPI
````yaml openapi/dataforseo.json POST /dataforseo/backlinks/timeseries_new_lost_summary/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/timeseries_new_lost_summary/live:
post:
summary: New & Lost Backlinks Timeseries Summary
description: >-
This endpoint will provide you with the number of new and lost backlinks
and referring domains for the domain specified in the target field.
operationId: post_dataforseo_backlinks_timeseries_new_lost_live
requestBody:
required: true
content:
application/json:
schema:
type: array
items:
type: object
properties:
target:
type: string
description: >-
domain to get data for required field a domain should be
specified without https:// and www. example: "forbes.com"
date_from:
type: string
description: >-
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:
type: string
description: >-
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:
type: string
description: >-
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:
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
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 from a POST array
tasks.result.date_from:
type: string
description: >-
starting date of the time range in the UTC format:
“yyyy-mm-dd” example: 2019-01-01
tasks.result.date_to:
type: string
description: >-
ending date of the time range in the UTC format:
"yyyy-mm-dd" example: "2019-01-15"
tasks.result.group_range:
type: string
description: group_range from the POST array
tasks.result.total_count:
type: integer
description: total amount of results relevant the request
tasks.result.items_count:
type: integer
description: the number of results returned in the items array
tasks.result.items:
type: array
items:
type: string
description: contains relevant backlinks and referring domains data
tasks.result.items.type:
type: string
description: type of element
tasks.result.items.date:
type: string
description: >-
date and time when the data for the target was stored in
the UTC format: “yyyy-mm-dd hh-mm-ss +00:00” example:
2019-11-15 12:57:46 +00:00
tasks.result.items.new_backlinks:
type: integer
description: >-
number of new backlinks number of new backlinks pointing
to the target
tasks.result.items.lost_backlinks:
type: integer
description: >-
number of lost backlinks number of lost backlinks of the
target
tasks.result.items.new_referring_domains:
type: integer
description: >-
number of new referring domains number of new referring
domains pointing to the target
tasks.result.items.lost_referring_domains:
type: integer
description: >-
number of lost referring domains number of lost referring
domains of the target
tasks.result.items.new_referring_main_domains:
type: integer
description: >-
number of new referring main domains number of new
referring main domains pointing to the target
tasks.result.items.lost_referring_main_domains:
type: integer
description: >-
number of lost referring main domains number of lost
referring main domains of 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.