New and Lost Backlinks

See which backlinks a domain gained or lost over time. Call the New and Lost Backlinks API via REST or MCP to automate SEO research in your app or AI agent.

CostRecent 37 credits / call

Try online

POST · https://api.nexscope.ai/seo/backlinkNewLostMCP · nexscope_seo_backlink_new_lost

Choose an integration method

Backlinks & Authority

What this API does

See which backlinks a domain gained or lost over time. The request accepts dateFrom, dateTo, groupRange, target. Its documented result includes bucketPolicy, groupRange, inputTarget, bucketEndAt, lostBacklinks, lostReferringDomains, lostReferringMainDomains, newBacklinks.

New and Lost Backlinks API use cases

Review link acquisition evidence

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

Compare competitor link profiles

A search marketer uses New and Lost Backlinks 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 New and Lost Backlinks with dateFrom and dateTo to prioritize links for manual review. The result helps choose suspicious or valuable links for manual assessment.

New and Lost Backlinks API FAQ

What does the New and Lost Backlinks API return?

See which backlinks a domain gained or lost over time. The documented output includes bucketPolicy, groupRange, inputTarget, bucketEndAt, lostBacklinks, lostReferringDomains, lostReferringMainDomains, newBacklinks. 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 New and Lost Backlinks 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 New and Lost Backlinks API from my app or an MCP client?

Send a POST request to https://api.nexscope.ai/seo/backlinkNewLost 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_new_lost. 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/backlinkNewLost

MCP method

nexscope_seo_backlink_new_lost

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/backlinkNewLost

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/backlinkNewLost' \
  -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"
}'

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	HTTP request completed. Check JSON code; only 0 indicates business success or acceptance.
400	Request JSON or required API parameters are invalid.
401	API key is missing, invalid, or cannot be matched to a user.
5xx	API execution or upstream service failed.

View parameters & response Try online

All categories/ Backlinks & Authority

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

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/backlinkNewLost`
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

Code example

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

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": [
        {
          "bucketEndAt": 9007199254740992,
          "lostBacklinks": 9007199254740992,
          "lostReferringDomains": 9007199254740992,
          "lostReferringMainDomains": 9007199254740992,
          "missing": [
            {
              "field": "synthetic",
              "reason": "synthetic"
            }
          ],
          "newBacklinks": 9007199254740992,
          "newReferringDomains": 9007199254740992,
          "newReferringMainDomains": 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[].bucketEndAt`	`integer`	required	Bucket end at value used by this API operation. Minimum: 0
`data.result.items[].lostBacklinks`	`integer \| null`	required	Lost backlinks value used by this API operation. Minimum: 0
`data.result.items[].lostReferringDomains`	`integer \| null`	required	Lost referring domains value used by this API operation. Minimum: 0
`data.result.items[].lostReferringMainDomains`	`integer \| null`	required	Lost referring main domains 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[].newBacklinks`	`integer \| null`	required	New backlinks value used by this API operation. Minimum: 0
`data.result.items[].newReferringDomains`	`integer \| null`	required	New referring domains value used by this API operation. Minimum: 0
`data.result.items[].newReferringMainDomains`	`integer \| null`	required	New referring main domains 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 with PROCESSING and a callId means 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/backlinkNewLost/calls/{callId} \
  -H "Authorization: Bearer nk-xxxxxxxxxxxxxxxxx"

Responses

Code	Description
200	HTTP request completed. Check JSON code; only 0 indicates business success or acceptance.
400	Request JSON or required API parameters are invalid.
401	API key is missing, invalid, or cannot be matched to a user.
5xx	API execution or upstream service failed.

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_new_lost",
    "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

Online test

Execute the current API with your API key and JSON payload. Online tests use this site's configured API environment; the Endpoint and copyable examples use the public integration address.

Uses your signed-in Nexscope session

SEO API Lab

SEO Backlink New Lost

See which backlinks a domain gained or lost over time. Call the New and Lost Backlinks API via REST or MCP to automate SEO research in your app or AI agent.

Live request

Estimated 37 credits / callAPI usage records

Date From

Value sent as the “dateFrom” request parameter.

Date To

Value sent as the “dateTo” request parameter.

Group Range

Choose one of the supported values: DAY, WEEK, MONTH, YEAR.

4 options

Target

Value sent as the “target” request parameter.

Up to 254 characters

Live calls may use Data credits.

Processing result

If a request is still processing, use the returned identifier to retrieve its stored result. The tester recognizes the identifier automatically, and result queries do not spend credits.

Live response

Results

Your live result will appear here.

Complete the request fields above and run the API. No sample response is substituted.

Test with an API key or MCP

Estimated 37 credits / callAPI usage records

Try it

Send a real request with the same contract shown in the reference.

Endpoint

/seo/backlinkNewLost

Processing result endpoint

https://api.nexscope.ai/seo/backlinkNewLost/calls/{resultId}

MCP method

nexscope_seo_backlink_new_lost

API key*

JSON payload*

cURL

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

Response

No response yet. Run the request to see the response here.

Processing result

Use the identifier returned by Run request. The tester selects the correct result query automatically, and result queries do not spend credits.

Result identifier

Result response

No task result yet. Query the task to see the generated output here.

Related APIs

Backlink Overview

Get a backlink summary for a domain or page, incl. backlinks and referring domains.

Backlink Anchors

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

Domain Backlink Pages

List the pages on a domain that attract the most backlinks.

Page Backlink Composition

Break down the backlink profile of a page by link type and source.