Google Trends By Keywords

Compare Google Trends search interest for multiple keywords across regions and custom time ranges for seasonal and market analysis. Call it via REST API or MCP.

CostRecent Avg. 13 · Range 10–13 credits / call

Try online

POST · https://api.nexscope.ai/api/skill-api/v1/skills/google-trends-by-keywords/runMCP · nexscope_google_trends_by_keywords

Keyword & Search Demand

What this API does

Compare Google Trends search interest for multiple keywords across regions and custom time ranges for seasonal and market analysis. The request accepts keyword, region, dayRangeStart, dayRangeEnd. Its documented result includes chartOption, chartOption.fieldX, chartOption.fieldY, dataSnapshotMonth, page, pageItemCount, pageSize, sourceTool.

Google Trends By Keywords API use cases

Build a keyword shortlist

To build a keyword shortlist, a marketplace analyst submits keyword and region to Google Trends By Keywords. The returned chartOption, chartOption.fieldX, chartOption.fieldY help choose candidate search terms for further investigation.

Compare search demand signals

A marketplace analyst uses Google Trends By Keywords with keyword and region to compare search demand signals. The returned chartOption, chartOption.fieldX, chartOption.fieldY help compare keyword demand within the requested market scope.

Plan a content or advertising test

For this workflow, a marketplace analyst calls Google Trends By Keywords with keyword and region to plan a content or advertising test. The result helps select terms for a content or advertising experiment.

Google Trends By Keywords API FAQ

What does the Google Trends By Keywords API return?

Compare Google Trends search interest for multiple keywords across regions and custom time ranges for seasonal and market analysis. The documented output includes chartOption, chartOption.fieldX, chartOption.fieldY, dataSnapshotMonth, page, pageItemCount, pageSize, sourceTool. It corresponds to the supplied keyword, region, dayRangeStart, dayRangeEnd. 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 Google Trends By Keywords API cost?

The current documented cost is Recent Avg. 13 · Range 10–13 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 Google Trends By Keywords API from my app or an MCP client?

Send a POST request to https://api.nexscope.ai/api/skill-api/v1/skills/google-trends-by-keywords/run 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_google_trends_by_keywords. The same documented request parameters apply; use Online test to review a request before adding it to your app.

View plans and credits Connect this API with MCP

Try this API

Endpoint

https://api.nexscope.ai/api/skill-api/v1/skills/google-trends-by-keywords/run

MCP method

nexscope_google_trends_by_keywords

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/api/skill-api/v1/skills/google-trends-by-keywords/run

Run an API

Request parameters documented by ecommerce.google-trends-by-keywords.

Example request

Replace YOUR_API_KEY, then run this command in your terminal.

curl -X POST 'https://api.nexscope.ai/api/skill-api/v1/skills/google-trends-by-keywords/run' \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "keyword": "phone case",
  "region": "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 & Search Demand

POSThttps://api.nexscope.ai/api/skill-api/v1/skills/google-trends-by-keywords/run

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/api/skill-api/v1/skills/google-trends-by-keywords/run`
Auth	`Bearer API key`
Content-Type	`application/json`

Request parameters

Name	Type	Required	Description
`keyword`	`string`	required	Keyword in the target country's language, at most 100 characters. Example: phone case
`region`	`string`	optional	Country/region, default US. Options: US, GB, JP, CA, MX, DE, FR, IT, ES, NL, AU, SG, AE, BR, IN, TR, PL, SE Example: US
`dayRangeStart`	`string`	optional	Time range start (
`dayRangeEnd`	`string`	optional	Time range end (

Code example

{
  "keyword": "phone case",
  "region": "US"
}

Response example

Platform response envelope. code 0 indicates success or acceptance; data contains the business result.

{
  "code": 0,
  "cost": "-1",
  "data": {
    "chartOption": {
      "data": [],
      "fieldY": []
    },
    "costToken": 1,
    "trendInfoForKeys": [
      {
        "keyword": "phone case",
        "trendValues": []
      }
    ]
  },
  "msg": null,
  "time": "2026-01-01 00:00:00",
  "traceId": null,
  "ts": "0"
}

Response fields

Name	Type	Required	Description
`code`	`integer`	required	0 means accepted or successful; nonzero is a platform error.
`cost`	`string`	required	Elapsed milliseconds, never credits; -1 outside web requests.
`data`	`any`	required	Data value used by this API operation.
`msg`	`string \| null`	required	Msg value used by this API operation.
`time`	`string`	required	Server local time: yyyy-MM-dd HH:mm:ss.
`traceId`	`string \| null`	required	Trace id value used by this API operation.
`ts`	`string`	required	Epoch milliseconds.

Any of option 1

Name	Type	Required	Description
`data`	`object`	required	Data value used by this API operation.
`data.chartOption`	`any`	optional	Chart option value used by this API operation.
`data.costTime`	`any`	optional	Cost time value used by this API operation.
`data.costToken`	`any`	optional	Cost token value used by this API operation.
`data.dataSnapshotMonth`	`any`	optional	Data snapshot month value used by this API operation.
`data.page`	`any`	optional	Page value used by this API operation.
`data.pageItemCount`	`any`	optional	Page item count value used by this API operation.
`data.pageSize`	`any`	optional	Page size value used by this API operation.
`data.sourceTool`	`any`	optional	Source tool value used by this API operation.
`data.sourceType`	`any`	optional	Source type value used by this API operation.
`data.title`	`any`	optional	Title value used by this API operation.
`data.totalPage`	`any`	optional	Total page value used by this API operation.
`data.trendInfoForKeys`	`any`	optional	Trend info for keys value used by this API operation.
`data.type`	`any`	optional	Type value used by this API operation.

Any of option 1

Name	Type	Required	Description
`data.chartOption`	`object`	optional	Chart rendering metadata Example: {}
`data.chartOption.data`	`any`	optional	Data value used by this API operation.
`data.chartOption.fieldX`	`any`	optional	Field x value used by this API operation.
`data.chartOption.fieldY`	`any`	optional	Field y value used by this API operation.
`data.chartOption.type`	`any`	optional	Type value used by this API operation.

Any of option 1

Name	Type	Required	Description
`data.chartOption.data`	`array`	optional	Data Example: []

Any of option 2

Name	Type	Required	Description
`data.chartOption.data`	`null`	optional	Data value used by this API operation.

Any of option 1

Name	Type	Required	Description
`data.chartOption.fieldX`	`string`	optional	X-axis field Example: null

Any of option 2

Name	Type	Required	Description
`data.chartOption.fieldX`	`null`	optional	Field x value used by this API operation.

Any of option 1

Name	Type	Required	Description
`data.chartOption.fieldY`	`array`	optional	Y-axis fields Example: []

Any of option 2

Name	Type	Required	Description
`data.chartOption.fieldY`	`null`	optional	Field y value used by this API operation.

Any of option 1

Name	Type	Required	Description
`data.chartOption.type`	`string`	optional	Data type Example: null

Any of option 2

Name	Type	Required	Description
`data.chartOption.type`	`null`	optional	Type value used by this API operation.

Any of option 2

Name	Type	Required	Description
`data.chartOption`	`null`	optional	Chart option value used by this API operation.

Any of option 1

Name	Type	Required	Description
`data.costTime`	`integer`	optional	Execution time reported by the upstream provider. Example: null

Any of option 2

Name	Type	Required	Description
`data.costTime`	`null`	optional	Cost time value used by this API operation.

Any of option 1

Name	Type	Required	Description
`data.costToken`	`integer`	optional	Token consumption Example: 1

Any of option 2

Name	Type	Required	Description
`data.costToken`	`null`	optional	Cost token value used by this API operation.

Any of option 1

Name	Type	Required	Description
`data.dataSnapshotMonth`	`string`	optional	Data snapshot month returned by the upstream provider. Example: null

Any of option 2

Name	Type	Required	Description
`data.dataSnapshotMonth`	`null`	optional	Data snapshot month value used by this API operation.

Any of option 1

Name	Type	Required	Description
`data.page`	`integer`	optional	Current page returned by the upstream provider. Example: null

Any of option 2

Name	Type	Required	Description
`data.page`	`null`	optional	Page value used by this API operation.

Any of option 1

Name	Type	Required	Description
`data.pageItemCount`	`integer`	optional	Item count on the current page returned by the upstream provider. Example: null

Any of option 2

Name	Type	Required	Description
`data.pageItemCount`	`null`	optional	Page item count value used by this API operation.

Any of option 1

Name	Type	Required	Description
`data.pageSize`	`integer`	optional	Page size returned by the upstream provider. Example: null

Any of option 2

Name	Type	Required	Description
`data.pageSize`	`null`	optional	Page size value used by this API operation.

Any of option 1

Name	Type	Required	Description
`data.sourceTool`	`string`	optional	Provider-specific source tool name. Example: null

Any of option 2

Name	Type	Required	Description
`data.sourceTool`	`null`	optional	Source tool value used by this API operation.

Any of option 1

Name	Type	Required	Description
`data.sourceType`	`string`	optional	Provider-specific source platform type. Example: null

Any of option 2

Name	Type	Required	Description
`data.sourceType`	`null`	optional	Source type value used by this API operation.

Any of option 1

Name	Type	Required	Description
`data.title`	`string`	optional	Provider-specific response title. Example: null

Any of option 2

Name	Type	Required	Description
`data.title`	`null`	optional	Title value used by this API operation.

Any of option 1

Name	Type	Required	Description
`data.totalPage`	`integer`	optional	Total page count returned by the upstream provider. Example: null

Any of option 2

Name	Type	Required	Description
`data.totalPage`	`null`	optional	Total page value used by this API operation.

Any of option 1

Name	Type	Required	Description
`data.trendInfoForKeys`	`array`	optional	Keyword trend info array Example: []
`data.trendInfoForKeys[]`	`object`	required	Item in data trendInfoForKeys.
`data.trendInfoForKeys[].keyword`	`string`	optional	Keyword Example: phone case
`data.trendInfoForKeys[].trendValues`	`array`	optional	Trend value array Example: []
`data.trendInfoForKeys[].trendValues[]`	`object`	required	Item in data trendInfoForKeys[] trendValues.
`data.trendInfoForKeys[].trendValues[].timeRange`	`string`	optional	Time, format yyyy-MM-dd Example: null
`data.trendInfoForKeys[].trendValues[].value`	`string`	optional	Value (normalized search interest, 0-100) Example: null

Any of option 2

Name	Type	Required	Description
`data.trendInfoForKeys`	`null`	optional	Trend info for keys value used by this API operation.

Any of option 1

Name	Type	Required	Description
`data.type`	`string`	optional	Provider-specific render or payload type. Example: null

Any of option 2

Name	Type	Required	Description
`data.type`	`null`	optional	Type value used by this API operation.

Any of option 2

Name	Type	Required	Description
`data`	`null`	required	Data value used by this API operation.

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

Step 2 of 2 · Call the tool

Call a tool

{
  "jsonrpc": "2.0",
  "id": "tool-call-1",
  "method": "tools/call",
  "params": {
    "name": "nexscope_google_trends_by_keywords",
    "arguments": {
      "keyword": "phone case",
      "region": "US"
    }
  }
}

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. Online tests use this site's configured API environment; the Endpoint and copyable examples use the public integration address.

10 credits / callAPI usage records

Try it

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

Endpoint

https://api.nexscope.ai/api/skill-api/v1/skills/google-trends-by-keywords/run

MCP method

nexscope_google_trends_by_keywords

API key*

JSON payload*

cURL

curl -X POST \
  https://api.nexscope.ai/api/skill-api/v1/skills/google-trends-by-keywords/run \
  -H "Authorization: Bearer nk-..." \
  -H "Content-Type: application/json" \
  -d '{ "keyword": "phone case", "region": "US" }'

Response

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

Related APIs

Amazon ASIN Keywords

Find keywords driving traffic to an Amazon ASIN.

Amazon Keyword Expansion

Find related Amazon keywords and compare search demand.

Amazon Keyword Intelligence

Explore weekly Amazon Brand Analytics search-term data.

Amazon Keyword Overview

Evaluate search demand and competition for an Amazon keyword.