Google Trends By Keywords
Compare Google Trends search interest for multiple keywords across regions and custom time ranges for seasonal and market analysis.
Cost10 credits / call
POST ·
https://api.nexscope.ai/api/skill-api/v1/skills/google-trends-by-keywords/runMCP · nexscope_google_trends_by_keywordsChoose an integration method
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.
Endpoint
https://api.nexscope.ai/api/skill-api/v1/skills/google-trends-by-keywords/runMCP method
nexscope_google_trends_by_keywordsStep 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-xxxxxxxxxxxxxxxxxMissing or invalid API keys return an authentication error. Manage keys from .
Step 2 of 3 · Send a request
POST
https://api.nexscope.ai/api/skill-api/v1/skills/google-trends-by-keywords/runRun 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 '{
"region": "US",
"keyword": "phone case"
}'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. |
All categories/ Keyword & Search Demand
POST
https://api.nexscope.ai/api/skill-api/v1/skills/google-trends-by-keywords/runRun this API
Send a JSON request to execute this API and receive the documented response payload.
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
{
"region": "US",
"keyword": "phone case"
}Response example
Platform response envelope. code 0 indicates success or acceptance; data contains the business result.
{
"data": {
"trendInfoForKeys": [
{
"keyword": "phone case",
"trendValues": []
}
],
"chartOption": {
"fieldY": [],
"data": []
},
"costToken": 1
},
"code": 0,
"msg": null,
"ts": "0",
"time": "2026-01-01 00:00:00",
"cost": "-1",
"traceId": null
}Response fields
| Name | Type | Required | Description |
|---|---|---|---|
data | any | required | Data value used by this API operation. |
code | integer | required | 0 means accepted or successful; nonzero is a platform error. |
msg | string | null | required | Msg value used by this API operation. |
ts | string | required | Epoch milliseconds. |
time | string | required | Server local time: yyyy-MM-dd HH:mm:ss. |
cost | string | required | Elapsed milliseconds, never credits; -1 outside web requests. |
traceId | string | null | required | Trace id value used by this API operation. |
Any of option 1
| Name | Type | Required | Description |
|---|---|---|---|
data | object | required | Data value used by this API operation. |
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 |
data.chartOption | object | optional | Chart rendering metadata Example: {} |
data.chartOption.type | string | optional | Data type Example: null |
data.chartOption.fieldX | string | optional | X-axis field Example: null |
data.chartOption.fieldY | array | optional | Y-axis fields Example: [] |
data.chartOption.data | array | optional | Data Example: [] |
data.costToken | integer | optional | Token consumption Example: 1 |
data.type | string | optional | Provider-specific render or payload type. Example: null |
data.title | string | optional | Provider-specific response title. Example: null |
data.sourceType | string | optional | Provider-specific source platform type. Example: null |
data.sourceTool | string | optional | Provider-specific source tool name. Example: null |
data.costTime | integer | optional | Execution time reported by the upstream provider. Example: null |
data.page | integer | optional | Current page returned by the upstream provider. Example: null |
data.pageSize | integer | optional | Page size returned by the upstream provider. Example: null |
data.pageItemCount | integer | optional | Item count on the current page returned by the upstream provider. Example: null |
data.totalPage | integer | optional | Total page count returned by the upstream provider. Example: null |
data.dataSnapshotMonth | string | optional | Data snapshot month returned by the upstream provider. Example: null |
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 recommendedConnect 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/jsonAuthentication
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": {
"region": "US",
"keyword": "phone case"
}
}
}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/mcpOnline test
Execute the current API with your API key and JSON payload.
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/runMCP method
nexscope_google_trends_by_keywordscURL
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 '{ "region": "US", "keyword": "phone case" }'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.