Catalog / Search, maps & leads
SEARCH, MAPS & LEADS
Google Trends
Get Google Trends data for up to five compared search terms: interest over time, interest by country, region, city or metro, and top and rising related queries and topics.
About this data
Get Google Trends data for up to five compared search terms: interest over time, interest by country, region, city or metro, and top and rising related queries and topics. Any region, time range, category or search type, plus each country's trending searches.
From the actor’s Apify Store listing. The per-call endpoint may return a bounded subset; its own description is below.
Buy per call over x402
One endpoint at api.ssh.autos. Each call is one JSON POST, paid in USDC with no account or API key, and answered in the same HTTP response.
POST /v1/google/trends/interest
One term and one region: normalized interest over time, source timestamps, formatted intervals, hasData/partial flags, resolved time range and Google Trends explore URL.
Timeline only: no related queries/topics, geography expansion, trending news, alerts or stored state.
A successfully parsed timeline with insufficient search volume returns no record.
Input
Send a JSON body to POST https://api.ssh.autos/v1/google/trends/interest.
| Field | Type | Required | Notes |
|---|---|---|---|
term | string | required | 1–100 characters |
geo | string | optional | pattern ^(?:[A-Z]{2}(?:-[A-Z0-9]{1,3}(?:-[0-9]{3})?)?)?$ |
timeRange | string | optional | one of past-7-days, past-30-days, past-90-days, past-12-months; default "past-12-months" |
searchProperty | string | optional | one of web, images, news, youtube, shopping; default "web" |
Returned fields
The answer is JSON: records, a list, and summary, the run status and counts. Each record has these 30 fields; a field the source does not publish comes back null.
30 fields per record
| Field | Type | Notes |
|---|---|---|
kind | string | searchTerm: one looked-up term with its interest and related searches. trendingSearch: one entry of a country's trending list. one of searchTerm, trendingSearch |
searchTerm | string | — |
comparedWith | array of strings | Other terms sharing the interest-over-time scale. Regional maps and related-query rankings are normalized separately per term. |
geo | string | Region code searched; null is worldwide. |
timeRange | string | The time range input (a preset name or custom). |
timeRangeResolved | string | The exact period Google Trends reported, e.g. 2025-10-23 2026-10-23. |
category | integer | — |
searchProperty | string | one of web, images, news, youtube, shopping |
averageInterest | integer | Average interest over the period when terms are compared. |
interestOverTime | array of objects | — |
regionResolution | string | one of COUNTRY, REGION, CITY, DMA |
interestByRegion | array of objects | — |
relatedQueries | object | — |
relatedTopics | object | — |
missingSections | array of objects | Requested sections not retrieved. Includes optional trending news failures; available data remains in the row. |
rank | integer | Position in the trending list in the chosen order. |
timeWindow | string | — |
searchVolume | integer | Approximate searches during the trend (Google's lower bound). |
searchVolumeFormatted | string | — |
increasePercentage | integer | — |
startedAt | string | — |
endedAt | string | — |
isActive | boolean | — |
categories | array of strings | — |
relatedSearches | array of strings | Other searches Google groups into this trend. |
picture | string | — |
newsArticles | array of objects | — |
exploreUrl | string | — |
scrapedAt | string | — |
normalization | object | Timeline comparison uses one shared scale. Each term's regional map and related-query ranking use their own scale. Interest scores are relative indices, not counts. |
Example call
npx agentcash@latest fetch https://api.ssh.autos/v1/google/trends/interest -m POST -b '{"term": "coffee"}'The example values come from the API spec or the actor’s own sample input. Running it is a paid call.
What is and isn’t charged
You pay the call price for
- An answer, including a definitive “not found” or an empty result.
- Confirmed no matches returns records: [] (charged: it is an answer).
Free
- Invalid input (422), busy (503), source failure (502), timeout (504) and calls whose client hung up are never charged.
- Invalid input and source failures are not charged.
Prefer a subscription? Run it on Apify
This data source is a public actor on the Apify Store: Google Trends Scraper. Run it with your Apify account and plan for larger, scheduled or exported runs; it may offer more input options than the per-call endpoint.
How x402 payment works
- Your client sends the request. The API answers
402 Payment Requiredwith the price and where to pay. - The client pays from its own wallet: USDC on Base or Solana over x402, or over MPP on Tempo. No account, sign-up or API key.
- The client retries with the payment attached and gets the JSON answer in the same call. You are only charged for answers.
The AgentCash CLI in the example does all three steps for you and pays from your AgentCash wallet. Any x402 or MPP client works the same way.
Machine-readable: openapi.json · llms.txt