Name: Google Trends API — Realtime Search Trends Data | REST JSON
Brand: greza
SKU: api-greza-google-trends-api
Availability: InStock
Author: API Market

Sergei Peleskov

# Google Trends Realtime API

Access **live Google Trends data** through a clean JSON REST API. No scraping infrastructure, no proxy management, no reverse-engineering fragile internal endpoints — just reliable, structured trends data on demand.

Google Trends is one of the most valuable free signals on the internet: what people are searching for, right now, in every country and region. But Google offers no official API. This product closes that gap with a production-grade gateway backed by a managed residential proxy pool, smart caching, and continuous monitoring against upstream changes.

## What you can do with it

- **Track search interest over time** for any keyword, in any country, over flexible timeframes — from the last hour to the last five years.
- **Compare up to 5 keywords head-to-head** on a normalized 0–100 scale, exactly like the Google Trends UI, but machine-readable.
- **Break interest down by geography** — countries worldwide, or regions, cities and DMAs within a country.
- **Discover related queries and rising searches** around any topic to find breakout keywords before they peak.
- **Pull the current trending searches feed** for any country in realtime.

## Endpoints

| Endpoint | What it returns |
|---|---|
| `/v1/interest-over-time` | Time series of search interest (0–100) for a keyword, filterable by geo and timeframe |
| `/v1/compare` | Normalized comparison of up to 5 keywords on a single 0–100 scale |
| `/v1/interest-by-region` | Geographic breakdown of interest: COUNTRY (worldwide), REGION, CITY, DMA |
| `/v1/related` | Top and rising queries associated with a keyword |
| `/v1/trending-now` | Live trending searches feed by country |

Full request/response schemas, parameters and examples are available in the interactive API documentation on this page.

## Why this API

**Built for reliability, not demos.**

- **Residential proxy pool under the hood.** Requests to Google go through a managed pool of residential IPs with sticky sessions and automatic slot rotation. You never see a `429` cascade because one datacenter IP got burned.
- **Smart caching.** Identical queries within a short TTL are served from cache — faster responses for you, and resilience against upstream hiccups.
- **Strict input validation.** Invalid parameter combinations (for example, a country-level `resolution` combined with a specific `geo`) are rejected with a clear `400 INVALID_INPUT` before ever reaching Google, so you never burn quota on requests that cannot succeed.
- **Clean error vocabulary.** Every error response carries a stable machine-readable code (`INVALID_INPUT`, `UPSTREAM_BAD_REQUEST`, `UPSTREAM_UNAVAILABLE`, ...) so your integration can branch on codes, not on prose.
- **Actively maintained.** Google changes its internal endpoints without notice; this gateway is monitored and patched continuously. When Google retired its daily trends endpoint, this API migrated transparently — consumers noticed nothing.

## Common use cases

**SEO & content teams.** Find rising queries in your niche before competitors do. Validate content ideas against real search demand instead of gut feeling. Time publication to interest peaks.

**Market research & analytics.** Track brand interest across countries and regions. Benchmark your brand against competitors on a normalized scale. Feed trends series into BI dashboards and forecasting models.

**E-commerce & dropshipping.** Spot product trends early. Compare demand across markets before expanding to a new country. Monitor seasonal patterns to plan inventory.

**Finance & trading signals.** Search interest is a documented leading indicator for retail attention. Pipe keyword series into quantitative models.

**AI agents & LLM pipelines.** Structured JSON output makes this API a natural tool for autonomous agents that need realtime "what is the world searching for" context. Deterministic error codes make retries safe.

**Media & newsrooms.** Detect breaking topics from the trending feed. Quantify how big a story really is by region.

## Quick start

1. Subscribe to a plan (free tier available — no credit card needed to test).
2. Grab your API key from the console.
3. Make your first call:

```bash
curl "https://prod.api.market/v1/greza/google-trends-api/v1/interest-over-time?kw=bitcoin&geo=US&timeframe=now%207-d" \
  -H "x-magicapi-key: YOUR_KEY"
```

You get back a JSON time series ready to plot or feed into your pipeline.

## Response format

All endpoints return structured JSON with a consistent envelope. Successful responses contain the data payload; errors contain a machine-readable `code` and a human-readable `message`. HTTP status codes follow REST conventions: `200` success, `400` invalid input, `401` bad key, `429` rate limited, `5xx` upstream issues.

## Data freshness

- `trending-now` reflects Google's live trending feed.
- Interest and comparison data mirrors what the Google Trends UI shows, including its normalization model (values are relative, 0–100, per query context).
- Short-TTL caching means repeated identical queries are fast without serving stale data.

## Fair usage & limits

Each plan includes a monthly request quota with clearly priced overage. Rate limits protect the shared infrastructure; if you need sustained high throughput or a custom SLA, contact us through the platform for an enterprise arrangement.

## FAQ

**Is this an official Google API?**
No. Google does not offer a public Trends API. This is an independent service that provides programmatic access to publicly available Google Trends data through managed infrastructure.

**How is this different from scraping it myself?**
You skip: residential proxy costs and management, session/cookie handling, normalization quirks, silent upstream format changes, and 429 storms. One subscription replaces an entire scraping stack.

**What happens when Google changes something?**
We monitor upstream continuously and patch the gateway. Breaking changes on Google's side are absorbed by the gateway — the API contract you integrate against stays stable.

**Can I use the data commercially?**
You are responsible for complying with applicable laws and Google's terms regarding the use of publicly available data. The API delivers the data; usage decisions are yours.

**What uptime can I expect?**
The gateway runs on monitored production infrastructure with caching layers that absorb short upstream outages. Status is reflected in response codes — `UPSTREAM_UNAVAILABLE` errors are not billed against retries in your client logic.

---

Start with the free tier, run your keywords, and see the data quality for yourself. Integration takes minutes: one HTTP call, one JSON response.

Realtime Google Trends API: interest over time, keyword comparison, regional breakdowns, related queries, trending searches. JSON REST. Free tier available.

Google Trends API — Realtime Search Trends Data | REST JSON

Free