Keyword & Search Demand

Google Trends By Keywords

Google Trends keyword search popularity comparison and trend analysis, supporting global regions and custom time ranges. Triggered by: Google Trends, keyword popularity over time, search interest comparison, keyword trend analysis, seasonal trend detection, regional search popularity, keyword heatmap, multi-keyword comparison on Google, keyword research, market trend analysis, search trends, seasonal analysis, regional popularity.

post/api/skill-api/v1/skills/google-trends-by-keywords/run

Request

  • Base URL: https://api.nexscope.ai
  • URL: https://api.nexscope.ai/api/skill-api/v1/skills/google-trends-by-keywords/run
  • Auth: HTTP bearer

Headers

X-Nexscope-Http-Status'legacy' | 'semantic'

Use semantic for HTTP error statuses on run and task-result requests. Without this header v1 retains legacy status behavior. The JSON envelope is unchanged; code 0 means success or acceptance, not asynchronous completion.

Request body

keywordstring required

Keyword (the keyword must be in the language of the target country! For example, use English keywords for the US, German keywords for Germany. If not in the corresponding country's language, please translate first.) Max length 100 characters

regionstring

Country/region, default US. Options: US, GB, JP, CA, MX, DE, FR, IT, ES, NL, AU, SG, AE, BR, IN, TR, PL, SE

dayRangeStartstring

Time range start (use when you want to freely specify the time range; custom time range takes priority), format YYYY-MM-DD, starting from 2004

dayRangeEndstring

Time range end (use when you want to freely specify the time range; custom time range takes priority), format YYYY-MM-DD, starting from 2004

Example request

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

Response

Successful response.

codeinteger required

0 means accepted or successful; nonzero is a platform error.

msgstring nullable required
tsstring required

Epoch milliseconds.

timestring required

Server local time: yyyy-MM-dd HH:mm:ss.

coststring required

Elapsed milliseconds, never credits; -1 outside web requests.

traceIdstring nullable required

Example response

{
  "data": {
    "trendInfoForKeys": [],
    "chartOption": {},
    "costToken": 1
  }
}

Changes

No recorded changes to this operation across all 1 revision of this API.