Google Research Tools: get Trend By Time API

Use Google Research Tools: get Trend By Time API through Nexscope with documented parameters, structured results and API key authentication.

CostRecent 13 credits / call

Try online

POST · https://api.nexscope.ai/googleTrend/getTrendByTimeMCP · nexscope_data_google_trend_get_trend_by_time

Google Research Tools

What this API does

Use Google Research Tools: get Trend By Time API through Nexscope with documented parameters, structured results and API key authentication. The request accepts days, region. Its documented result includes chartOption, chartOption.fieldX, chartOption.fieldY, chartOption.title, trendValues, query, searchVolume, increasePercentage.

Google Research Tools: get Trend By Time API API use cases

Compare market evidence

To compare market evidence, a marketplace analyst submits days and region to Google Research Tools: get Trend By Time API. The returned chartOption, chartOption.fieldX, chartOption.fieldY help compare the requested market or product research signals.

Review a product demand signal

A marketplace analyst uses Google Research Tools: get Trend By Time API with days and region to review a product demand signal. The returned chartOption, chartOption.fieldX, chartOption.fieldY help identify demand evidence worth checking against other sources.

Prepare a sourcing or inventory review

For this workflow, a marketplace analyst calls Google Research Tools: get Trend By Time API with days and region to prepare a sourcing or inventory review. The result helps inform a sourcing review without assuming future sales.

Google Research Tools: get Trend By Time API API FAQ

What does the Google Research Tools: get Trend By Time API API return?

Use Google Research Tools: get Trend By Time API through Nexscope with documented parameters, structured results and API key authentication. The documented output includes chartOption, chartOption.fieldX, chartOption.fieldY, chartOption.title, trendValues, query, searchVolume, increasePercentage. It corresponds to the supplied days, region. 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 Research Tools: get Trend By Time API API cost?

The current documented cost is Recent 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 Research Tools: get Trend By Time API API from my app or an MCP client?

Send a POST request to https://api.nexscope.ai/googleTrend/getTrendByTime 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_data_google_trend_get_trend_by_time. 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/googleTrend/getTrendByTime

MCP method

nexscope_data_google_trend_get_trend_by_time

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/googleTrend/getTrendByTime

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/googleTrend/getTrendByTime' \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "days": 7,
  "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/ Google Research Tools

POSThttps://api.nexscope.ai/googleTrend/getTrendByTime

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

Request parameters

Name	Type	Required	Description
`days`	`integer`	optional	Time range, query the trend data of the last few days. Common values: 1, 2, 7. Example: 7
`region`	`string`	optional	Country code. Optional values: `US`, `GB`, `JP`, `CA`, `MX`, `DE`, `FR`, `IT`, `ES`. `NL`, `AU`, `SG`, `AE`, `BR`, `IN`, `TR`, `PL`, `SE`. Example: US

Code example

{
  "days": 7,
  "region": "US"
}

Response example

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

{
  "code": 0,
  "cost": "-1",
  "data": {},
  "msg": null,
  "time": "2026-01-01 00:00:00",
  "traceId": null,
  "ts": "0"
}

Response fields

Response field reference (13 fields)

Name	Type	Required	Description
`costToken`	`integer`	optional	Consume token.
`chartOption`	`object`	optional	Chart configuration object, containing visualization data.
`chartOption.data`	`array`	optional	data, array of chart data point objects.
`chartOption.fieldX`	`string`	optional	X-axis field.
`chartOption.fieldY`	`array`	optional	Y-axis field.
`chartOption.type`	`string`	optional	Data type.
`chartOption.title`	`string`	optional	title.
`trendValues`	`array`	optional	Trend value, array of popular query objects.
`query`	`string`	optional	Keywords.
`searchVolume`	`integer`	optional	Search volume value.
`increasePercentage`	`integer`	optional	Increase percentage: integer, value range -100~100, unit is %.
`startTime`	`string`	optional	Start timestamp.
`endTime`	`string`	optional	End timestamp.

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_data_google_trend_get_trend_by_time",
    "arguments": {
      "days": 7,
      "region": "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.

10 credits / callAPI usage records

Try it

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

Endpoint

/googleTrend/getTrendByTime

MCP method

nexscope_data_google_trend_get_trend_by_time

API key*

JSON payload*

cURL

curl -X POST \
  https://api.nexscope.ai/googleTrend/getTrendByTime \
  -H "Authorization: Bearer nk-..." \
  -H "Content-Type: application/json" \
  -d '{ "days": 7, "region": "US" }'

Response

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

Use Google Research Tools: google Search API through Nexscope with documented parameters, structured results and API key authentication.

Google Research Tools: get Trend By Keys API

Use Google Research Tools: get Trend By Keys API through Nexscope with documented parameters, structured results and API key authentication.

Google Research Tools: search API

Use Google Research Tools: search API through Nexscope with documented parameters, structured results and API key authentication.

What this API does

Google Research Tools: get Trend By Time API API use cases

Compare market evidence

Review a product demand signal

Prepare a sourcing or inventory review

Google Research Tools: get Trend By Time API API FAQ

What does the Google Research Tools: get Trend By Time API API return?

How many credits does the Google Research Tools: get Trend By Time API API cost?

How do I call the Google Research Tools: get Trend By Time API API from my app or an MCP client?

Authentication

Run an API

Example request

Check the response

HTTP status codes

Run this API

Endpoint

Request parameters

Code example

Response example

Response fields

Responses

Data source, freshness, and limitations

MCP

Call a tool

Legacy MCP v1

Online test

Try it

Related APIs