ScavioScavio
ToolsPricing
Sign InsGet Startedg
2 live endpoints

Google Trends API

Historical interest over time for any term and region, plus what is spiking right now with real search volume and growth — each one a single POST returning structured JSON. Google has never shipped an official Trends API.

Get your API keyRead the docs

50 free credits on signup. No card required.

POST /api/v2/google/trends
sample
query:
try
{  "search_parameters": {    "query": "ai agents",    "geo": "US",    "hl": "en",    "date": "today 12-m",    "tz": "420"  },  "interest_over_time": {    "timeline_data": [      {        "date": "Jun 29 – Jul 5, 2025",        "timestamp": "1751155200",        "values": [          {            "query": "ai agents",            "value": "19",            "extracted_value": 19          }        ]      }    ]  },  "credits_used": 1,  "credits_remaining": 49}
captured example · 1 credits3 / 3 free

Live call against the real endpoint — 3 free runs, then it's your own key.

What is the Scavio Google Trends API?

The Scavio Google Trends API is a REST API that returns Google Trends data as structured JSON. You send a term with a region and date window to get a normalised interest series with related queries, or a region and hours window to get the searches trending there right now with absolute volume and growth.

2
endpoints, all live in production
1
credit per call, both endpoints
0
official Google Trends APIs

Two endpoints, two different questions

One answers is this rising. The other answers what is rising.

Interest over time

POST /api/v2/google/trends

The classic Trends series for a term and geography — normalised values by week, with related queries, ready to chart or regress against your own numbers.

Trending now

POST /api/v2/google/trending

What is spiking in a region right now, with actual search volume and growth percentage rather than a rank — so you can filter by size, not vibes.

Both Google Trends endpoints

Every route is a POST, returns JSON, and takes the same API key. 1 credit per successful call.

EndpointReturnsCredits
Interest over time/api/v2/google/trendsA term's normalised interest series by date, plus related queries1
Trending now/api/v2/google/trendingTerms trending in a region now — search volume, growth, start time1

50 free credits on signup covers 50 calls of any kind. See plans

A twelve-month series in one call

Chart interest for a term, then ask what is spiking now. The response on the right is a real capture — note the flat shape, with no data wrapper.

from scavio import ScavioClient

client = ScavioClient(api_key="sk_live_your_key")

res = client.google.trends(query="ai agents", geo="US", date="today 12-m")
for row in res["interest_over_time"]["timeline_data"]:
    print(row["date"], row["values"][0]["extracted_value"])

# What is spiking right now - 1 credit
now = client.google.trending(geo="US", hours=24)
200 response.jsoncaptured
{
  "search_parameters": {
    "query": "ai agents",
    "geo": "US",
    "hl": "en",
    "date": "today 12-m",
    "tz": "420"
  },
  "interest_over_time": {
    "timeline_data": [
      {
        "date": "Jun 29 – Jul 5, 2025",
        "timestamp": "1751155200",
        "values": [
          {
            "query": "ai agents",
            "value": "19",
            "extracted_value": 19
          }
        ]
      }
    ]
  },
  "credits_used": 1,
  "credits_remaining": 49
}

Why not the official Google Trends API?

There isn't one. That is the whole reason this endpoint exists.

Google Trends

  • No public, documented API has ever shipped
  • The site is a web UI backed by internal endpoints that change without notice
  • Community libraries break whenever those internals move
  • Rate limiting and CAPTCHAs make self-scraping unreliable at any scale

Scavio Google Trends API

  • A documented, versioned REST endpoint with a stable response shape
  • Interest over time and real-time trending, both at 1 credit
  • Trending returns absolute search volume and growth, not just a rank
  • Same key and JSON envelope as 30 other Scavio platforms

Scavio returns publicly available aggregate interest data, which contains no personal information.

What developers build with it

Demand forecasting and seasonality

Pull twelve months of interest for your category and regress it against your own sales. Seasonality that is obvious in Trends is often invisible in a single account's history.

trends

Newsjacking and content timing

Trending now returns real search volume and growth percentage, so an editor can pick the spike worth writing about within the hour rather than the day after.

trending

Keyword and market validation

Before committing to a term, check whether interest is rising, flat or a dead cat. Related queries surface the phrasing people actually use around it.

trends

Competitor and brand interest tracking

Track your brand term against rivals on the same normalised scale, by region, to see who is gaining share of attention rather than share of spend.

trends

Agent tools for research

Point an agent at the MCP server and Trends becomes a callable tool — is this rising, what is spiking in this market — with the same key as every other Scavio platform.

MCP + REST

How to get Google Trends data as JSON

  1. 1

    Get an API key

    Sign up for a Scavio account and copy your key from the dashboard. You get 50 credits free on signup, with no card required and nothing to scrape or reverse engineer.

  2. 2

    POST a term or a region

    Send {"query": "ai agents", "geo": "US", "date": "today 12-m"} to https://api.scavio.dev/api/v2/google/trends, or POST a geo to /api/v2/google/trending for what is spiking now.

  3. 3

    Read the JSON

    Google v2 responses are flat — interest_over_time and trends sit at the top level, not under data, alongside credits_used and credits_remaining. Each timeline point has a date and an extracted_value ready to chart.

One key, 31 platformsMCP server for agentsPython & JS SDKsn8n community node

Google Trends API FAQ

What is the Scavio Google Trends API?

+

It is a REST API that returns Google Trends data as structured JSON. Two POST endpoints cover interest over time for a term and geography with related queries, and real-time trending searches for a region with search volume and growth. You authenticate with a Scavio API key.

Who are these endpoints for?

+

Developers embedding demand signals in a product; AI agent builders wiring Trends in as an MCP or SDK tool; automation engineers running it inside n8n, Zapier or Make; growth and SEO teams validating keywords; brand managers tracking share of attention; and editorial teams timing coverage. Same API for all of them.

Does Google have an official Trends API?

+

No. Google Trends has never shipped a public, documented API — the site is a web UI backed by internal endpoints that change without notice. Every Trends integration is built on an unofficial layer; this one is maintained, versioned and documented.

What is the difference between trends and trending?

+

The trends endpoint returns a historical interest series for a term you choose. The trending endpoint returns what is spiking in a region right now, which you did not choose — with real search volume, growth percentage and when it started.

Are the interest values real search volumes?

+

For the trends endpoint, no. Google normalises interest to a 0-100 scale relative to the peak of the series, which is why the same term can look different over different date ranges. The trending endpoint does return an absolute search_volume figure.

How much does a Google Trends request cost?

+

Both endpoints cost 1 credit. New accounts get 50 free credits on signup, one time, with no card required. Paid plans start at $30 per month for 7,000 credits.

What date ranges and regions are supported?

+

Pass a date window such as today 12-m and a geo such as US on the trends endpoint, and a geo plus an hours window on trending. The values you sent come back in search_parameters, so a stored response is self-describing.

What does the response look like?

+

Google v2 responses are flat rather than wrapped: search_parameters and interest_over_time sit at the top level, alongside credits_used and credits_remaining. Each timeline point carries date, timestamp and values with both a string value and a numeric extracted_value.

Which languages and tools are supported?

+

Official Python (pip install scavio) and JavaScript/TypeScript (npm i scavio) SDKs, a remote MCP server at mcp.scavio.dev for AI agents, and an n8n community node. Any language can call the REST endpoints directly with an HTTP client.

Is using Google Trends data legal?

+

Scavio returns publicly available aggregate interest data, which contains no personal information. You remain responsible for how you use it, including compliance with Google's terms. Talk to your own counsel for your specific use case.

Explore more of Scavio

Google Search API

The full SERP — organic, ads, AI Overview.

Google News API

Headlines, sources and dates as JSON.

Google Shopping API

Products, prices and every seller.

Reddit API

Search Reddit and pull full comment threads.

MCP server

Every platform as a callable tool for agents.

Pricing

Credit packs and plans, no per-platform surcharge.

Start pulling Google Trends data today

50 free credits on signup, no card. Your first request is a POST with a term in it.

Get your API keySee pricing
ScavioScavio

One scraper API for every social, search and ecommerce platform. Built for AI agents.

Product

  • Features
  • Pricing
  • Dashboard
  • Affiliates

Developers

  • Documentation
  • API Reference
  • Quickstart
  • MCP Integration
  • Python SDK

Alternatives

  • Tavily Alternative
  • SerpAPI Alternative
  • Firecrawl Alternative
  • Exa Alternative
  • Serper Alternative
  • Tavily vs Scavio
  • SerpAPI vs Scavio
  • All alternatives
  • Compare Scavio vs alternatives

Search APIs

  • Google Search API
  • Amazon Product API
  • YouTube API
  • Reddit API
  • Walmart Product API
  • TikTok API
  • Instagram API

Tools

  • All Tools

© 2026 Scavio. All rights reserved.

Featured on TAAFT
Terms of ServicePrivacy Policy