Backlink Time Series

Compare a website’s backlink counts, linking websites, and authority scores across returned periods to understand longer-term changes.

CostRecent 37 credits / call

Try online

POST · https://api.nexscope.ai/seo/backlinkTimeseriesMCP · nexscope_seo_backlink_timeseries

What this API does

Compare a website’s backlink counts, linking websites, and authority scores across returned periods to understand longer-term changes. The request accepts dateFrom, dateTo, groupRange, target. Its documented result includes bucketPolicy, groupRange, inputTarget, backlinks, backlinksNofollow, bucketEndAt, rank, referringDomains.

Backlink Time Series API use cases

Review link acquisition evidence

To review link acquisition evidence, a search marketer submits dateFrom and dateTo to Backlink Time Series. The returned bucketPolicy, groupRange, inputTarget help identify referring sources that merit closer inspection.

Compare competitor link profiles

A search marketer uses Backlink Time Series with dateFrom and dateTo to compare competitor link profiles. The returned bucketPolicy, groupRange, inputTarget help compare link evidence for competing websites.

Prioritize links for manual review

For this workflow, a search marketer calls Backlink Time Series with dateFrom and dateTo to prioritize links for manual review. The result helps choose suspicious or valuable links for manual assessment.

Backlink Time Series API FAQ

What does the Backlink Time Series API return?

Compare a website’s backlink counts, linking websites, and authority scores across returned periods to understand longer-term changes. The documented output includes bucketPolicy, groupRange, inputTarget, backlinks, backlinksNofollow, bucketEndAt, rank, referringDomains. It corresponds to the supplied dateFrom, dateTo, groupRange, target. Optional fields can be absent; a missing value should not be interpreted as a measured zero. Example values illustrate the response shape, rather than live account results.

How many credits does the Backlink Time Series API cost?

The current documented cost is Recent 37 credits / call. This is the same cost shown at the top of this page. If a range or estimate is displayed, the final charge depends on the request. Review your available credits and the pricing page before calling the API, and check API usage records for the actual charge.

How do I call the Backlink Time Series API from my app or an MCP client?

Send a POST request to https://api.nexscope.ai/seo/backlinkTimeseries with your API key as a Bearer token and the JSON inputs shown in API integration. In a compatible MCP client such as Claude or Cursor, connect Nexscope and call nexscope_seo_backlink_timeseries. Use the MCP arguments shown in the MCP guide, or switch Online test to MCP to review its request before adding it to your app.

View plans and credits Connect this API with MCP

Try this API

Endpoint

https://api.nexscope.ai/seo/backlinkTimeseries

MCP method

nexscope_seo_backlink_timeseries

Step 1 of 3 · Authenticate

Authentication

All run endpoints require a user API key. Send it as a bearer token in the Authorization header.

Authorization: Bearer nk-xxxxxxxxxxxxxxxxx

Missing or invalid API keys return an authentication error. Manage keys from .

Step 2 of 3 · Send a request

POSThttps://api.nexscope.ai/seo/backlinkTimeseries

Run an API

Send a JSON request body using the parameters described below.

Example request

Replace YOUR_API_KEY, then run this command in your terminal.

curl -X POST 'https://api.nexscope.ai/seo/backlinkTimeseries' \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "dateFrom": "2026-01-01",
  "dateTo": "2026-01-31",
  "groupRange": "MONTH",
  "target": "nexscope.ai"
}'

Code example

{
  "dateFrom": "2026-01-01",
  "dateTo": "2026-01-31",
  "groupRange": "MONTH",
  "target": "nexscope.ai"
}

Step 3 of 3 · Inspect the result

Check the response

Read code for the request status and data for the result. Open the parameter and response reference for the full field definitions.

HTTP status codes

Code	Description
200	Default HTTP response for both success and many business errors. Only outer JSON code 0 indicates success or asynchronous acceptance; inspect data for the result.
429	Execution admission rate limit; honor Retry-After when present.
503	Execution admission is temporarily unavailable; honor Retry-After when present.
Opt-in	X-Nexscope-Http-Status: semantic maps controller-handled business errors to HTTP status on run and task routes. Pre-authentication failures, such as a missing or invalid API key (code 11209, including an incomplete or corrupted copy) or an expired website login session (code 12001), may still return HTTP 200 before this mapping. Always check the outer JSON code; malformed requests and infrastructure failures may also return non-200 HTTP responses.

View parameters & response Try online

All categories/ Backlinks & Authority

POSThttps://api.nexscope.ai/seo/backlinkTimeseries

Run this API

Send a JSON request to execute this API and receive the documented response payload.

Open tester

Endpoint

Method	`POST`
Path	`https://api.nexscope.ai/seo/backlinkTimeseries`
Auth	`Bearer API key`
Content-Type	`application/json`

Request parameters

Name	Type	Required	Description
`dateFrom`	`string`	required	Date from value used by this API operation. Format: date
`dateTo`	`string`	required	Date to value used by this API operation. Format: date
`groupRange`	`string`	optional	Group range value used by this API operation. Allowed: DAY, WEEK, MONTH, YEAR Default: MONTH
`target`	`string`	required	Target value used by this API operation. Minimum length: 1 Maximum length: 254

Response example

Example response envelope from the documented SEO API contract.

{
  "code": 0,
  "cost": "-1",
  "data": {
    "callId": "synthetic-call",
    "completedAt": null,
    "coverage": {
      "missing": [
        {
          "field": "synthetic",
          "reason": "UPSTREAM_FIELD_MISSING"
        }
      ],
      "status": "PARTIAL"
    },
    "requestedAt": "123",
    "result": {
      "bucketPolicy": "synthetic",
      "groupRange": "synthetic",
      "inputTarget": "synthetic",
      "items": [
        {
          "backlinks": 9007199254740992,
          "backlinksNofollow": 9007199254740992,
          "bucketEndAt": 9007199254740992,
          "missing": [
            {
              "field": "synthetic",
              "reason": "synthetic"
            }
          ],
          "rank": 9007199254740992,
          "referringDomains": 9007199254740992,
          "referringMainDomains": 9007199254740992,
          "referringPages": 9007199254740992
        }
      ],
      "missing": [
        {
          "field": "synthetic",
          "reason": "synthetic"
        }
      ],
      "normalizedTarget": "synthetic",
      "requestedDateFrom": "synthetic",
      "requestedDateTo": "synthetic",
      "returnedCount": 1,
      "sourceKind": "synthetic",
      "sourceProduct": "synthetic",
      "truncated": false,
      "zeroMeaning": "synthetic"
    },
    "schemaVersion": "synthetic",
    "source": "synthetic",
    "status": "PARTIAL",
    "usage": {
      "billingStatus": "UNAPPROVED",
      "chargedCredits": "0"
    }
  },
  "msg": null,
  "time": "2026-01-01 00:00:00",
  "traceId": "synthetic-trace",
  "ts": "9007199254740993"
}

Response fields

Name	Type	Required	Description
`code`	`integer`	required	0 is a successful envelope; inspect data.status separately. Allowed: 0, 42008, 42009
`cost`	`string`	required	Elapsed processing milliseconds; not price. -1 for non-web context.
`data`	`object`	required	Data value used by this API operation.
`data.callId`	`string \| null`	optional	Call id value used by this API operation.
`data.completedAt`	`string \| integer \| null`	optional	Completed at value used by this API operation.
`data.coverage`	`object`	optional	Coverage value used by this API operation.
`data.coverage.missing`	`array`	optional	Missing value used by this API operation.
`data.coverage.missing[]`	`object`	required	Item in data coverage missing.
`data.coverage.missing[].field`	`string`	optional	Field value used by this API operation.
`data.coverage.missing[].reason`	`string`	optional	Reason value used by this API operation.
`data.coverage.status`	`string`	optional	Status value used by this API operation.
`data.requestedAt`	`string \| integer \| null`	optional	Requested at value used by this API operation.
`data.result`	`object \| null`	required	Result value used by this API operation.
`data.result.bucketPolicy`	`string`	required	Bucket policy value used by this API operation. Constant: provider_full_period
`data.result.groupRange`	`string`	required	Group range value used by this API operation. Allowed: DAY, WEEK, MONTH, YEAR
`data.result.inputTarget`	`string`	required	Input target value used by this API operation.
`data.result.items`	`array`	required	Items value used by this API operation. Minimum items: 0 Maximum items: 366
`data.result.items[]`	`object`	required	Item in data result items.
`data.result.items[].backlinks`	`integer \| null`	required	Backlinks value used by this API operation. Minimum: 0
`data.result.items[].backlinksNofollow`	`integer \| null`	required	Backlinks nofollow value used by this API operation. Minimum: 0
`data.result.items[].bucketEndAt`	`integer`	required	Bucket end at value used by this API operation. Minimum: 0
`data.result.items[].missing`	`array`	required	Missing value used by this API operation. Minimum items: 0
`data.result.items[].missing[]`	`object`	required	Item in data result items[] missing.
`data.result.items[].missing[].field`	`string`	required	Field value used by this API operation.
`data.result.items[].missing[].reason`	`string`	required	Reason value used by this API operation. Allowed: UPSTREAM_FIELD_MISSING, UPSTREAM_FIELD_INVALID, DUPLICATE_UPSTREAM_ITEM, UPSTREAM_ITEM_MISSING
`data.result.items[].rank`	`integer \| null`	required	Rank value used by this API operation. Minimum: 0 Maximum: 1000
`data.result.items[].referringDomains`	`integer \| null`	required	Referring domains value used by this API operation. Minimum: 0
`data.result.items[].referringMainDomains`	`integer \| null`	required	Referring main domains value used by this API operation. Minimum: 0
`data.result.items[].referringPages`	`integer \| null`	required	Referring pages value used by this API operation. Minimum: 0
`data.result.missing`	`array`	required	Missing value used by this API operation. Minimum items: 0
`data.result.missing[]`	`object`	required	Item in data result missing.
`data.result.missing[].field`	`string`	required	Field value used by this API operation.
`data.result.missing[].reason`	`string`	required	Reason value used by this API operation. Allowed: UPSTREAM_FIELD_MISSING, UPSTREAM_FIELD_INVALID, DUPLICATE_UPSTREAM_ITEM, UPSTREAM_ITEM_MISSING
`data.result.normalizedTarget`	`string`	required	Normalized target value used by this API operation.
`data.result.requestedDateFrom`	`string`	required	Requested date from value used by this API operation. Format: date
`data.result.requestedDateTo`	`string`	required	Requested date to value used by this API operation. Format: date
`data.result.returnedCount`	`integer`	required	Returned count value used by this API operation. Minimum: 0
`data.result.sourceKind`	`string`	required	Source kind value used by this API operation. Constant: dataforseo_backlink_index
`data.result.sourceProduct`	`string`	required	Source product value used by this API operation. Constant: backlinks
`data.result.truncated`	`boolean`	required	Truncated value used by this API operation.
`data.result.zeroMeaning`	`string`	required	Zero meaning value used by this API operation. Constant: provider_zero_or_no_data
`data.schemaVersion`	`string \| null`	optional	Schema version value used by this API operation.
`data.source`	`string \| null`	optional	Source value used by this API operation.
`data.status`	`string`	optional	Status value used by this API operation. Allowed: SUCCESS, PARTIAL, EMPTY, PROCESSING, UNKNOWN, FAILED
`data.usage`	`object \| null`	optional	Usage value used by this API operation.
`data.usage.billingStatus`	`string \| null`	optional	Billing status value used by this API operation.
`data.usage.chargedCredits`	`string \| integer \| null`	optional	Charged credits value used by this API operation.
`msg`	`string \| null`	required	Available upstream msg/errmsg/message is preferred for success and failure; Chinese is translated to English. Missing successful message is null. Platform-only errors and task states use platform English. Message text never determines success or retry.
`time`	`string`	required	yyyy-MM-dd HH:mm:ss
`traceId`	`string \| null`	required	Trace id value used by this API operation.
`ts`	`string`	required	Epoch milliseconds; global long serializer.

Accepted processing response

code 0 confirms acceptance. Use data.callId to query the same request; processing is not completion.

Name	Type	Required	Description
`code`	`integer`	required	0 is a successful envelope; inspect data.status separately. Constant: 0
`cost`	`string`	required	Elapsed processing milliseconds; not price. -1 for non-web context.
`data`	`object`	required	Data value used by this API operation.
`data.callId`	`string \| null`	required	Call id value used by this API operation.
`data.reason`	`string`	required	Reason value used by this API operation. Constant: IN_PROGRESS
`data.retryable`	`boolean`	optional	Retryable value used by this API operation.
`data.status`	`string`	required	Status value used by this API operation. Constant: PROCESSING
`data.taskId`	`string \| null`	optional	Task id value used by this API operation.
`msg`	`string \| null`	required	Available upstream msg/errmsg/message is preferred for success and failure; Chinese is translated to English. Missing successful message is null. Platform-only errors and task states use platform English. Message text never determines success or retry.
`time`	`string`	required	yyyy-MM-dd HH:mm:ss
`traceId`	`string \| null`	required	Trace id value used by this API operation.
`ts`	`string`	required	Epoch milliseconds; global long serializer.

Error response

Name	Type	Required	Description
`code`	`integer`	required	0 is a successful envelope; inspect data.status separately.
`cost`	`string`	required	Elapsed processing milliseconds; not price. -1 for non-web context.
`data`	`object`	required	Data value used by this API operation.
`data.callId`	`string \| null`	required	Call id value used by this API operation.
`data.reason`	`string \| null`	required	Reason value used by this API operation.
`data.retryable`	`boolean`	optional	Retryable value used by this API operation.
`data.status`	`string \| null`	required	Status value used by this API operation.
`data.taskId`	`string \| null`	optional	Task id value used by this API operation.
`msg`	`string \| null`	required	Available upstream msg/errmsg/message is preferred for success and failure; Chinese is translated to English. Missing successful message is null. Platform-only errors and task states use platform English. Message text never determines success or retry.
`time`	`string`	required	yyyy-MM-dd HH:mm:ss
`traceId`	`string \| null`	required	Trace id value used by this API operation.
`ts`	`string`	required	Epoch milliseconds; global long serializer.

Retrieve a processing result

A response withPROCESSING and a callIdmeans the result is still being prepared. Use the result query below with the returned identifier. This lookup reads the stored result and does not spend credits.

curl -X GET https://api.nexscope.ai/seo/backlinkTimeseries/calls/{callId} \
  -H "Authorization: Bearer nk-xxxxxxxxxxxxxxxxx"

Responses

Code	Description
200	Default HTTP response for both success and many business errors. Only outer JSON code 0 indicates success or asynchronous acceptance; inspect data for the result.
429	Execution admission rate limit; honor Retry-After when present.
503	Execution admission is temporarily unavailable; honor Retry-After when present.
Opt-in	X-Nexscope-Http-Status: semantic maps controller-handled business errors to HTTP status on run and task routes. Pre-authentication failures, such as a missing or invalid API key (code 11209, including an incomplete or corrupted copy) or an expired website login session (code 12001), may still return HTTP 200 before this mapping. Always check the outer JSON code; malformed requests and infrastructure failures may also return non-200 HTTP responses.

Data source, freshness, and limitations

Source, freshness, coverage, rate limits, and estimation notes are not specified in this API definition unless they appear in the request or response field documentation above. Do not assume official marketplace data or real-time freshness when it is not explicitly documented.

Step 1 of 2 · Connect your MCP client

MCP

V2 recommended

Connect remote agents through the standard MCP 2025-11-25 Streamable HTTP endpoint. Use OAuth 2.1 Authorization Code with PKCE, or an API key for compatibility.

POST https://api.nexscope.ai/mcp
MCP-Protocol-Version: 2025-11-25
Content-Type: application/json

Authentication

OAuth clients request the mcp:tools scope. The endpoint's 401 response advertises protected-resource metadata for authorization discovery.

Step 2 of 2 · Call the tool

Call a tool

{
  "jsonrpc": "2.0",
  "id": "tool-call-1",
  "method": "tools/call",
  "params": {
    "name": "nexscope_seo_backlink_timeseries",
    "arguments": {
      "dateFrom": "2026-01-01",
      "dateTo": "2026-01-31",
      "groupRange": "MONTH",
      "target": "nexscope.ai"
    }
  }
}

Legacy MCP v1

Existing API-key clients can continue using the compatibility endpoint. New integrations should use MCP v2.

GET / POST /mcp/legacy

What can you do with this API?

Data explained and practical use cases

AI Guide

Question

What data can Backlink Time Series provide, and how might I use it?

AI answer

This API provides historical backlink-index measurements for a domain across a requested date range, grouped by day, week, month, or year.

Data category	Documented fields	What the values mean
Time buckets	`data.result.groupRange`, `items[].bucketEndAt`, `bucketPolicy`	The requested grouping, each bucket's end time, and the provider's full-period bucket policy.
Backlink counts	`data.result.items[].backlinks`, `backlinksNofollow`	Provider-reported total and nofollow backlink counts for a bucket, when available.
Referring sources	`data.result.items[].referringDomains`, `referringMainDomains`, `referringPages`	Counts of distinct referring domains, main domains, and pages for a bucket.
Rank signal	`data.result.items[].rank`	The provider-reported rank value for that bucket, when available.
Data interpretation	`data.result.zeroMeaning`, `items[].missing[].field`, `items[].missing[].reason`	A zero may mean a provider zero or no data; missing entries identify unavailable or invalid fields.
Series scope	`data.result.returnedCount`, `truncated`	Number of returned buckets and whether the series was cut short.

Chart whether the domain's indexed backlink count rose or fell over the requested months.
- Prompt example: “I plan search marketing for an online store. Could you chart whether the domain's indexed backlink count rose or fell over the requested months? Show the relevant returned evidence and tell me what input you need from me.”
Compare referring-domain growth with backlink growth to see whether gains came from more sources or more links per source.
- Prompt example: “I plan search marketing for an online store. Could you compare referring-domain growth with backlink growth to see whether gains came from more sources or more links per source? Show the returned values behind the comparison, and mark missing data.”
Examine changes in nofollow counts alongside total backlinks.
- Prompt example: “I plan search marketing for an online store. Could you examine changes in nofollow counts alongside total backlinks? Show the relevant returned evidence and tell me what input you need from me.”
Flag unusual bucket-to-bucket changes for closer investigation using backlink records.
- Prompt example: “I plan search marketing for an online store. Could you flag unusual bucket-to-bucket changes for closer investigation using backlink records? Show the relevant returned evidence and tell me what input you need from me.”

These are provider-index measurements, not a complete history of links on the web. Treat zero values carefully because the documented zeroMeaning explicitly allows no data. The supplied example is still PROCESSING.

Data Example

Sample request and response

Request parameters

{
  "dateTo": "2025-06-30",
  "dateFrom": "2025-01-01",
  "groupRange": "MONTH",
  "inputTarget": "amazon.com",
  "normalizedTarget": "amazon.com"
}

Response

{
  "code": 0,
  "msg": null,
  "data": {
    "usage": {
      "billingStatus": "CHARGED",
      "chargedCredits": 37
    },
    "callId": "1f7f2552-ad6c-4db1-b1d3-b02d57085289",
    "result": {
      "items": [
        {
          "rank": 881,
          "missing": [],
          "backlinks": 2632507255,
          "bucketEndAt": 1738281600000,
          "referringPages": 1846504236,
          "referringDomains": 4111725,
          "backlinksNofollow": 2603041040,
          "referringMainDomains": 3339133
        },
        {
          "rank": 881,
          "missing": [],
          "backlinks": 2589664082,
          "bucketEndAt": 1740700800000,
          "referringPages": 1823113677,
          "referringDomains": 4058184,
          "backlinksNofollow": 2780256731,
          "referringMainDomains": 3313665
        },
        {
          "rank": 827,
          "missing": [],
          "backlinks": 2519836165,
          "bucketEndAt": 1743379200000,
          "referringPages": 1774258741,
          "referringDomains": 3948275,
          "backlinksNofollow": 2992331917,
          "referringMainDomains": 3293939
        },
        {
          "rank": 851,
          "missing": [],
          "backlinks": 2499375699,
          "bucketEndAt": 1745971200000,
          "referringPages": 1754789683,
          "referringDomains": 3800388,
          "backlinksNofollow": 3223691411,
          "referringMainDomains": 3268164
        },
        {
          "rank": 851,
          "missing": [],
          "backlinks": 2487965682,
          "bucketEndAt": 1748649600000,
          "referringPages": 1740803161,
          "referringDomains": 3773780,
          "backlinksNofollow": 3479102862,
          "referringMainDomains": 3257260
        },
        {
          "rank": 850,
          "missing": [],
          "backlinks": 2460909881,
          "bucketEndAt": 1751241600000,
          "referringPages": 1725942629,
          "referringDomains": 3740945,
          "backlinksNofollow": 3751251543,
          "referringMainDomains": 3233668
        }
      ],
      "missing": [],
      "truncated": false,
      "groupRange": "MONTH",
      "sourceKind": "dataforseo_backlink_index",
      "inputTarget": "amazon.com",
      "zeroMeaning": "provider_zero_or_no_data",
      "bucketPolicy": "provider_full_period",
      "returnedCount": 6,
      "sourceProduct": "backlinks",
      "requestedDateTo": "2025-06-30",
      "normalizedTarget": "amazon.com",
      "requestedDateFrom": "2025-01-01"
    },
    "source": "dataforseo",
    "status": "SUCCESS",
    "coverage": {
      "status": "COMPLETE",
      "missing": []
    },
    "completedAt": 1789953358676,
    "requestedAt": 1789953358128,
    "schemaVersion": "MDX-F1-BA12-1.0"
  }
}

Related APIs

Backlink Anchors

List the anchor texts other websites use when linking to a domain or page.

Backlink Authority Ranks

Compare backlink authority scores for up to 20 websites or pages, keeping the returned scores together for SEO and competitor research.

Backlink Competitors

Find domains with backlink profiles similar to a target domain.

Backlink Domain Intersection

Find websites that link to both of two selected websites or pages. Review the shared link sources to support your competitor research.