Docs menu

Google API endpoint

Google Trends explore rising queries

Returns the Rising related queries widget for one or more Google Trends explore terms. Returns an empty queries array when Google returns no rows for the requested term/filter combination.

POSTapiKey2 credits/requestGoogletrends.ExploreRequesttrends.exploreQueriesResponseDoc/google/trends/explore/rising-queries

Overview

Returns the Rising related queries widget for one or more Google Trends explore terms. Returns an empty queries array when Google returns no rows for the requested term/filter combination.

View Google Search platform page Open in Playground Copy language examples

Request schema

Name	In	Type	Required	Enum	Example	Description
request	body	object	Yes			Explore request
x-api-key	header	string	Yes			API key required

Authentication

Send your scraping API key in the x-api-key header. Use the console API Keys page to rotate or select the active key.

Billing

Endpoint usage is metered in credits. The plan prices, included credits, limits, and overage rates below match the active backend billing configuration.

Credit cost: 2 credits/request
Charged response: Successful 2xx responses

Plan	Price	Included credits	Daily cap	Rate limit	Overage
Free	$0/mo	2,000	500 daily credits	5/min	No overage
Starter	$9/mo	20,000	5,000 daily credits	15/min	$0.75/1,000 overage credits when enabled
Growth	$29/mo	100,000	25,000 daily credits	45/min	$0.45/1,000 overage credits when enabled
Pro	$79/mo	400,000	No daily cap	120/min	$0.30/1,000 overage credits
Business	$199/mo	1,200,000	No daily cap	300/min	$0.20/1,000 overage credits
Enterprise	$499/mo	5,000,000	No daily cap	1,000/min	$0.12/1,000 overage credits

Infrastructure behavior

This endpoint is executed through Crawlora's managed scraping infrastructure.

Proxy strategy: managed automatically where needed
Browser rendering: enabled for supported targets that require rendered HTML or JavaScript execution
Browser cluster: supported dynamic workloads can be routed through distributed browser instances
Retry behavior: automatic retry/fallback may be used depending on endpoint type
Challenge handling: challenged pages or unusable upstream HTML are detected and surfaced clearly when they cannot be used
Billing: credits are charged only for successful 2xx responses
Observability: responses include request context where available

Browser cluster behavior

Some targets require real browser execution because the data is loaded through JavaScript, dynamic rendering, or interaction-like browser behavior.

For supported endpoints, Crawlora can route requests through a managed browser cluster. This allows Crawlora to execute JavaScript, load dynamic content, apply browser-level request behavior, and normalize the rendered result into JSON.

You do not need to operate your own Playwright, Puppeteer, Chrome, proxy, queue, or retry infrastructure.

Error behavior

Crawlora does not silently return bad data when the upstream page cannot be used.

Status	Common failure case
400	Invalid input or missing required parameter
429	Plan or endpoint rate limit exceeded
500	Internal execution error
502	Upstream platform failed, returned unusable HTML, or served a challenge page that could not be resolved

When possible, Crawlora returns structured error context so your integration can retry, back off, or inspect the request.

Failure responses

Status	Description	Schema
400	Invalid input	#/definitions/app.Response
429	Rate limit exceeded	#/definitions/app.Response
500	Internal server error	#/definitions/app.Response
502	Google Trends upstream request failed	#/definitions/app.Response

Request body example

{
  "category": 0,
  "geo": "US",
  "hl": "en-US",
  "keywords": [
    "chatgpt",
    "openai"
  ],
  "property": "",
  "time_range": "today 12-m",
  "type": "web",
  "tz": 0
}

Example response

{
  "code": 200,
  "msg": "OK",
  "data": {
    "keywords": [
      "google"
    ],
    "geo": "HK",
    "time_range": "today 1-y",
    "query_type": "rising",
    "queries": [
      {
        "keyword": "google",
        "items": [
          {
            "query": "google ai studio",
            "formatted_value": "Breakout"
          }
        ]
      }
    ]
  }
}

Request schema

#/definitions/trends.ExploreRequest

Field	Type	Required	Enum	Example
category	integer	No		0
geo	string	No	WORLDWIDE, AF, AX, AL, DZ, AS, AD, AO, AI, AQ, AG, AR, AM, AW, AU, AT, AZ, BS, BH, BD, BB, BY, BE, BZ, BJ, BM, BT, BO, BA, BW, BV, BR, IO, VG, BN, BG, BF, BI, KH, CM, CA, CV, BQ, KY, CF, TD, CL, CN, CX, CC, CO, KM, CG, CD, CK, CR, CI, HR, CU, CW, CY, CZ, DK, DJ, DM, DO, EC, EG, SV, GQ, ER, EE, SZ, ET, FK, FO, FJ, FI, FR, GF, PF, TF, GA, GM, GE, DE, GH, GI, GR, GL, GD, GP, GU, GT, GG, GN, GW, GY, HT, HM, HN, HK, HU, IS, IN, ID, IR, IQ, IE, IM, IL, IT, JM, JP, JE, JO, KZ, KE, KI, XK, KW, KG, LA, LV, LB, LS, LR, LY, LI, LT, LU, MO, MG, MW, MY, MV, ML, MT, MH, MQ, MR, MU, YT, MX, FM, MD, MC, MN, ME, MS, MA, MZ, MM, NA, NR, NP, NL, NC, NZ, NI, NE, NG, NU, NF, KP, MK, MP, NO, OM, PK, PW, PS, PA, PG, PY, PE, PH, PN, PL, PT, PR, QA, RE, RO, RU, RW, WS, SM, ST, SA, SN, RS, SC, SL, SG, SX, SK, SI, SB, SO, ZA, GS, KR, SS, ES, LK, BL, SH, KN, LC, MF, PM, VC, SD, SR, SJ, SE, CH, SY, TW, TJ, TZ, TH, TL, TG, TK, TO, TT, TN, TR, TM, TC, TV, UM, VI, UG, UA, AE, GB, US, UY, UZ, VU, VA, VE, VN, WF, EH, YE, ZM, ZW	US
hl	string	No		en-US
keywords	array	No		chatgpt,openai
property	string	No
time_range	string	No	now 1-H, now 4-H, now 1-d, now 7-d, today 1-m, today 3-m, today 12-m, today 1-y, today 5-y, all	today 12-m
type	string	No	web, image, news, youtube, shopping	web
tz	integer	No		0

Response schema

#/definitions/trends.exploreQueriesResponseDoc

Field	Type	Required	Example
code	integer	No	200
data	trends.ExploreQueriesResponse	No
data.category	integer	No	0
data.geo	string	No	US
data.hl	string	No	en-US
data.keywords	array	No
data.property	string	No
data.queries	array	No
data.queries[].items	array	No
data.queries[].items[].formatted_value	string	No	100
data.queries[].items[].link	string	No	/trends/explore?q=chatgpt
data.queries[].items[].query	string	No	chatgpt login
data.queries[].items[].topic_mid	string	No	/g/11khcfz0y2
data.queries[].items[].topic_title	string	No	ChatGPT
data.queries[].items[].topic_type	string	No	Topic
data.queries[].items[].value	integer	No	100
data.queries[].keyword	string	No	chatgpt
data.query_type	string	No	top
data.time_range	string	No	today 12-m
data.type	string	No	web
data.tz	integer	No	0
msg	string	No	OK

Code examples

Use environment variables for secrets and keep Crawlora API keys server-side.

curl -X POST "https://api.crawlora.net/api/v1/google/trends/explore/rising-queries" \
  -H "x-api-key: $CRAWLORA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"category":0,"geo":"US","hl":"en-US","keywords":["chatgpt","openai"],"property":"","time_range":"today 12-m","type":"web","tz":0}'

Responsible public web data workflows

Crawlora is designed for responsible structured public web data workflows. Customers are responsible for using Crawlora in compliance with applicable laws, third-party rights, target-platform rules, and Crawlora terms.

Read Crawlora terms

More Google endpoints Google Search platform Pricing Playground

Open in Playground Back to group

Google Trends explore rising queries

Overview

Request schema

Authentication

Billing

Infrastructure behavior

Browser cluster behavior

Error behavior

Failure responses

Request body example

Example response

Code examples

Responsible public web data workflows

Related