keyword source · google search

Google Trends API

Google Trends data as clean JSON. Normalized 0-100 search interest time series, growth over 3M/6M/12M/5Y windows, and the live trending searches feed from one REST endpoint.

GitHub repo

POST get_growth · google search

# one POST, every source
POST https://api.trendsapi.ai/api
Authorization: Bearer YOUR_API_KEY

{ "mode": "get_growth",
  "source": "google search",
  "keyword": "ai agents",
  "window": ["3M", "12M"] }

200 OKnormalized 0-100

response

  {
    "search_term": "ai agents",
    "data_source": "google search",
    "results": [
      {
        "period": "3M",
        "growth": 38.2,
        "direction": "increase"
      },
      {
        "period": "12M",
        "growth": 340.7,
        "direction": "increase"
      }
    ]
  }

application/jsontimestamped

Why it exists

Google Trends trend data, without the plumbing

Anyone who has pulled Google Trends data programmatically knows the failure modes: 429 rate-limit errors, requests that only work through residential proxies, and pipelines that break when Google changes an endpoint. Trends API runs that infrastructure for you. You send one POST with a keyword, you get back a normalized time series with a timestamp.

Because every source on the platform is rescaled to the same 0-100 range, a Google search interest score is directly comparable to a TikTok hashtag score or an Amazon product search score. That makes cross-platform questions ('did TikTok buzz turn into search demand?') a two-call job instead of two integrations.

Use cases

What people build with it

SEO research

Check whether a keyword's search interest is rising or fading before you invest in content for it.

Market research

Measure consumer demand for a category over 5 years before entering it.

Journalism

Verify whether a story is still climbing or already past peak interest.

Investing

Track brand and product search interest as an alternative-data signal.

Comparison

How it compares

	pytrends / scrapers	Trends API
429 rate-limit errors	constant	never
Proxies required	often	never
Breaks on Google changes	regularly	no, managed infrastructure
Sources covered	Google only	16 keyword sources + 24 live feeds
Growth windows	compute yourself	3M/6M/12M/5Y built in
Maintenance	pytrends is archived	actively maintained
Free tier	n/a	100 requests/month

Three modes, one endpoint

get_time_series

Historical trend series for a keyword on this source, normalized 0-100.

get_growth

Growth percentages over 3M / 6M / 12M / 5Y windows.

get_top_trends

24 live trending feeds across platforms, no keyword needed.

FAQ

Common questions

Is this an official Google API?

No. Trends API is an independent managed service that normalizes Google Trends interest into a stable JSON schema. You do not need a Google account, and you never deal with rate-limit blocks or scraping breakage.

Why not just use pytrends?

pytrends is archived and relies on endpoints Google actively blocks. Users hit 429 errors, broken pipelines and proxy costs. Trends API runs the data infrastructure; you call one POST endpoint and get JSON back.

What does the 0-100 score mean?

Each keyword series is rescaled against its own history, where 100 is the peak interest in the requested window. Because every source is normalized the same way, a Google score and a TikTok score are directly comparable.

How far back does history go?

Up to 5 years of weekly data on paid plans. The free tier includes 12 months of history with 24-hour delayed data.

Can I get what is trending right now?

Yes. Call get_top_trends with type "Google Trends" for the live trending searches feed, no keyword needed.

Keep exploring

Related trend sources

pytrends alternativeThe managed pytrends alternative YouTubeYouTube trend data as JSON NewsNews trend data as JSON

Start pulling Google Trends trends in 60 seconds.

100 requests a month free. No credit card, no sales call. One key works for every source.