Keyword Interest by Region

Compare relative search interest in a keyword across US regions. Call the Keyword Interest by Region API via REST or MCP to automate SEO research.

CostRecent 10 credits / call

Try online

POST · https://api.nexscope.ai/seo/keywordInterestRegionsMCP · nexscope_seo_keyword_interest_regions

Choose an integration method

Keyword Research

What this API does

Compare relative search interest in a keyword across US regions. The request accepts dateFrom, dateTo, keywords, market. Its documented result includes dateFrom, dateTo, inputKeywords, keyword, regions.geoId, regions.geoName, regions.interest, languageFilter.

Keyword Interest by Region API use cases

Build a keyword shortlist

To build a keyword shortlist, a search marketer submits dateFrom and dateTo to Keyword Interest by Region. The returned dateFrom, dateTo, inputKeywords help choose candidate search terms for further investigation.

Compare search demand signals

A search marketer uses Keyword Interest by Region with dateFrom and dateTo to compare search demand signals. The returned dateFrom, dateTo, inputKeywords help compare keyword demand within the requested market scope.

Plan a content or advertising test

For this workflow, a search marketer calls Keyword Interest by Region with dateFrom and dateTo to plan a content or advertising test. The result helps select terms for a content or advertising experiment.

Keyword Interest by Region API FAQ

What does the Keyword Interest by Region API return?

Compare relative search interest in a keyword across US regions. The documented output includes dateFrom, dateTo, inputKeywords, keyword, regions.geoId, regions.geoName, regions.interest, languageFilter. It corresponds to the supplied dateFrom, dateTo, keywords, market. 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 Keyword Interest by Region API cost?

The current documented cost is Recent 10 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 Keyword Interest by Region API from my app or an MCP client?

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

MCP method

nexscope_seo_keyword_interest_regions

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

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/keywordInterestRegions' \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "dateFrom": "2026-01-01",
  "dateTo": "2026-01-31",
  "keywords": [
    "nexscope"
  ],
  "market": "US"
}'

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/ Keyword Research

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

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/keywordInterestRegions`
Auth	`Bearer API key`
Content-Type	`application/json`

Request parameters

Name	Type	Required	Description
`dateFrom`	`string`	required	2004-01-01 or later; inclusive interval at most 366 days. Format: date
`dateTo`	`string`	required	No later than first acceptance UTC day; replay retains the frozen dates. Format: date
`keywords`	`array`	required	Keywords value used by this API operation. Minimum items: 1 Maximum items: 5
`keywords[]`	`string`	required	After Unicode trim, NFC and lowercase, 1 to 80 code points and at most ten whitespace-separated words; no control characters. Minimum length: 1
`market`	`string`	optional	Market value used by this API operation. Constant: US Default: US

Code example

{
  "dateFrom": "2026-01-01",
  "dateTo": "2026-01-31",
  "keywords": [
    "nexscope"
  ],
  "market": "US"
}

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": {
      "dateFrom": "synthetic",
      "dateTo": "synthetic",
      "inputKeywords": [
        "synthetic"
      ],
      "items": [
        {
          "keyword": "synthetic",
          "missing": [
            {
              "field": "synthetic",
              "reason": "synthetic"
            }
          ],
          "regions": [
            {
              "geoId": "synthetic",
              "geoName": "synthetic",
              "interest": 9007199254740992,
              "missing": [
                {
                  "field": "synthetic",
                  "reason": "synthetic"
                }
              ]
            }
          ]
        }
      ],
      "languageFilter": "synthetic",
      "marketScope": "synthetic",
      "missing": [
        {
          "field": "synthetic",
          "reason": "synthetic"
        }
      ],
      "normalizedKeywords": [
        "synthetic"
      ],
      "returnedCount": 1,
      "sourceKind": "synthetic",
      "sourceProduct": "synthetic",
      "truncated": false
    },
    "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.dateFrom`	`string`	required	Date from value used by this API operation. Format: date
`data.result.dateTo`	`string`	required	Date to value used by this API operation. Format: date
`data.result.inputKeywords`	`array`	required	Input keywords value used by this API operation. Minimum items: 1 Maximum items: 5
`data.result.inputKeywords[]`	`string`	required	Item in data result inputKeywords.
`data.result.items`	`array`	required	Items value used by this API operation. Minimum items: 0 Maximum items: 5
`data.result.items[]`	`object`	required	Item in data result items.
`data.result.items[].keyword`	`string`	required	Keyword value used by this API operation.
`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[].regions`	`array`	required	Regions value used by this API operation. Minimum items: 0 Maximum items: 300
`data.result.items[].regions[]`	`object`	required	Item in data result items[] regions.
`data.result.items[].regions[].geoId`	`string \| null`	required	Geo id value used by this API operation.
`data.result.items[].regions[].geoName`	`string \| null`	required	Geo name value used by this API operation.
`data.result.items[].regions[].interest`	`integer \| null`	required	Interest value used by this API operation. Minimum: 0 Maximum: 100
`data.result.items[].regions[].missing`	`array`	required	Missing value used by this API operation. Minimum items: 0
`data.result.items[].regions[].missing[]`	`object`	required	Item in data result items[] regions[] missing.
`data.result.items[].regions[].missing[].field`	`string`	required	Field value used by this API operation.
`data.result.items[].regions[].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.languageFilter`	`null`	required	Language filter value used by this API operation.
`data.result.marketScope`	`string`	required	Market scope value used by this API operation. Constant: US
`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.normalizedKeywords`	`array`	required	Normalized keywords value used by this API operation. Minimum items: 1 Maximum items: 5
`data.result.normalizedKeywords[]`	`string`	required	Item in data result normalizedKeywords.
`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_trends_region_relative
`data.result.sourceProduct`	`string`	required	Source product value used by this API operation. Constant: keywords_data
`data.result.truncated`	`boolean`	required	Truncated value used by this API operation.
`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/keywordInterestRegions/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_keyword_interest_regions",
    "arguments": {
      "dateFrom": "2026-01-01",
      "dateTo": "2026-01-31",
      "keywords": [
        "nexscope"
      ],
      "market": "US"
    }
  }
}

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

Keyword Interest by Region

Compare relative search interest in a keyword across US regions. Call the Keyword Interest by Region API via REST or MCP to automate SEO research.

Live request

Estimated 10 credits / callAPI usage records

Date From

2004-01-01 or later; inclusive interval at most 366 days.

Date To

No later than first acceptance UTC day; replay retains the frozen dates.

Keywords

After Unicode trim, NFC and lowercase, 1 to 80 code points and at most ten whitespace-separated words; no control characters.

1–5 values

Market

Value sent as the “market” request parameter.

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 10 credits / callAPI usage records

Try it

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

Endpoint

/seo/keywordInterestRegions

Processing result endpoint

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

MCP method

nexscope_seo_keyword_interest_regions

API key*

JSON payload*

cURL

curl -X POST \
  https://api.nexscope.ai/seo/keywordInterestRegions \
  -H "Authorization: Bearer nk-..." \
  -H "Content-Type: application/json" \
  -d '{ "dateFrom": "2026-01-01", "dateTo": "2026-01-31", "keywords": [ "nexscope" ], "market": "US" }'

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

Keyword Metrics

Get search volume, CPC, competition and difficulty for a list of keywords.

Keyword History

See how search volume and other metrics for a keyword changed over time.

Keyword Intent

Detect whether keywords are informational, navigational, commercial or transactional.

Keyword Categories

Classify keywords into product and service categories.