comparisons

Official alpha is unscaled Google. This API is 0-100 JSON.

Google's Trends API is an application-gated alpha with consistently scaled values and a rolling 1800-day window. Trends API is a Bearer POST, 0-100, and more than Google.

Google announced a Trends API alpha on 24 July 2025 and still collects testers at developers.google.com/search/apis/trends. The official product is first-party Google search interest, consistently scaled, geo via ISO 3166-2, a rolling five-year window. Trends API is a different contract: a Bearer key, POST https://api.trendsapi.ai/api, scores on 0-100, and sources Google does not operate. body is a JSON string and must be parsed a second time. Docs: the API reference. Caps: pricing. Google notes: the Google Trends guide.

Alpha application, no self-serve key

The official page asks for testers who can start soon and send feedback. Until a project is allow-listed, there is no official client to compare latency against. Trends API keys exist without that form. Do not file an alpha ticket against POST /api.

Consistently scaled values are not 0-100

The website rescales every request. The official API does not. That is why Google says callers can merge the last period onto an older pull and compare dozens of terms (the website still caps a comparison set). Trends API keeps the website-like 0-100 so google search can sit next to tiktok without a private min-max.

1800 days and geo ISO-3166-2

Official history is a rolling 1800 days. Official geo is region and sub-region. Those are the official differentiators versus Explore. Trends API get_growth windows are preset strings (3M, 12M, YTD). Country slices are not an ISO field on this POST.

What the official API does not ship

The public alpha text does not list TikTok, Amazon, Reddit, npm, or a live trending-now board. If the project is approved and the job is unscaled Google only, the official API is the first-party path. If the job is JSON today on more than Google, this POST is the path that exists without a waitlist.

Trends API vs official Google Trends API

What you get

Official alpha application

Consistently scaled official values

Rolling 1800-day official window

Trends API 0-100 plus other sources

Official has no TikTok source

FAQ

Common questions

Is the official Google Trends API generally available?

No. Google's Search Central page still frames it as an alpha with an application form. Access opens on a rolling basis to a limited set of testers. There is no public self-serve key.

Are official values 0-100?

No. The July 2025 announcement and the API page say values are consistently scaled across requests and are not the website's 0-100 rescale. That is the feature that lets callers merge pulls. Trends API scores are 0-100 so sources share one axis.

How much history does the official API keep?

A rolling window of 1800 days, about five years, with daily, weekly, monthly, and yearly aggregation. Data stops about two days ago per the announcement. Other sources on Trends API have their own stored length.

Does the official API include Trending Now?

The public alpha pages describe interest, intervals, and region or sub-region. They do not document a trending-now board. Trends API exposes type Google Trends on get_top_trends.

Keep exploring

An official-grade replacement for Google Trends access Official-grade means a named vendor, a documented JSON contract, and a key. Google's alpha is first-party and gated. Trends API is third-party and multi-source. Unofficial clients scrape. The official API is an allow-list. Libraries, SERP engines, Actors, and proxy URLs all read Explore or Daily Trends HTML. Google's alpha is a different scale, a different auth, and a form. They are not substitutes. One is a frozen scrape. One is a gated Google Cloud product. pytrends 4.9.2 still rescales 0-100 per Explore request. The official alpha is consistently scaled, apply-only, and five years. They do not share an auth model or a value scale.

Start pulling trend data in 60 seconds.

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