Nexscope

SEO Backlink Records

SEO API documentation for REST and MCP, generated from the implemented API contract.

API selector
Backlinks & Authority

API overview

Bounded backlinks projection from the DataForSEO backlink index. Preserve target kind and provider scope. Proprietary rankings are not Google ratings or measured traffic. No pagination or additional provider calls. Unapproved costs prevent execution.

Try this API
Endpoint
/api/skill-api/v1/skills/seo-backlink-records/run
MCP method
nexscope_seo_backlink_records

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 .
POST/api/skill-api/v1/skills/seo-backlink-records/run

Run an API

Send a JSON request body using the parameters described below.

Slugseo-backlink-records
HeadersAuthorization: Bearer nk-...
Content-Type: application/json
Request bodyAPI-specific JSON object.
Response bodyComplete HTTP envelope, including code and data.

Status codes

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

Example request

curl -X POST https://api.nexscope.ai/api/skill-api/v1/skills/seo-backlink-records/run \
  -H "Authorization: Bearer nk-xxxxxxxxxxxxxxxxx" \
  -H "Content-Type: application/json" \
  -d '{   "limit": 10,   "target": {     "kind": "DOMAIN",     "target": "nexscope.ai"   } }'
All categories/ Backlinks & Authority

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/api/skill-api/v2/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.

Call a tool

{
  "jsonrpc": "2.0",
  "id": "tool-call-1",
  "method": "tools/call",
  "params": {
    "name": "nexscope_seo_backlink_records",
    "arguments": {
      "limit": 10,
      "target": {
        "kind": "DOMAIN",
        "target": "nexscope.ai"
      }
    }
  }
}
Legacy MCP v1

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

GET / POST /api/skill-api/v1/mcp

Online test

Execute the current API with your API key and JSON payload.

Try it

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

Endpoint
/api/skill-api/v1/skills/seo-backlink-records/run
Processing result endpoint
https://api.nexscope.ai/api/skill-api/v1/skills/seo-backlink-records/calls/{resultId}
MCP method
nexscope_seo_backlink_records
cURL
curl -X POST \
  https://api.nexscope.ai/api/skill-api/v1/skills/seo-backlink-records/run \
  -H "Authorization: Bearer nk-..." \
  -H "Content-Type: application/json" \
  -d '{ "limit": 10, "target": { "kind": "DOMAIN", "target": "nexscope.ai" } }'
Response
No response yet. Run the request to see the response here.
Processing result

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

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