Search & SEO

Google Trends API

The Google Trends API returns search-interest data as clean JSON.

4 actionsLive JSON1,000 free creditsMCP-ready

🤖 Using an AI assistant? Copy this link into ChatGPT / Claude / Cursor — it reads every endpoint and parameter instantly and tells you if this API fits your use case.

The primary interest_over_time endpoint returns a 0-100 timeline per keyword and geo, and you can pull related_queries, related_topics, interest_by_region, trending_now, suggestions and categories. It is built for trend research, content planning and market intelligence that need Trends data without waiting on the official alpha. One ReefAPI key, one shared credit pool, the standard envelope.

Live example

Real request and response JSON

Captured from the indexed primary action, interest_over_time, on Jul 18, 2026, 5:19 PM UTC.

Captured request

{
  "method": "POST",
  "url": "https://api.reefapi.com/google-trends/v1/interest_over_time",
  "headers": {
    "x-api-key": "$REEF_KEY",
    "content-type": "application/json"
  },
  "body": {
    "keyword": "bitcoin",
    "geo": "US",
    "timeframe": "today 12-m"
  }
}

Captured response

{
  "ok": true,
  "meta": {
    "api": "google-trends",
    "endpoint": "interest_over_time",
    "mode": "live",
    "latency_ms": 2226.8,
    "record_count": 53,
    "bytes": 14239,
    "cache_hit": false,
    "completeness_pct": 100
  },
  "data": {
    "keywords": [
      "bitcoin"
    ],
    "geo": "US",
    "timeframe": "today 12-m",
    "category": 0,
    "property": "",
    "timeline": [
      {
        "date": "[redacted-phone]",
        "timestamp": 1752364800,
        "formatted_time": "Jul 13 – 19, 2025",
        "value": 54,
        "has_data": true
      },
      {
        "date": "[redacted-phone]",
        "timestamp": 1752969600,
        "formatted_time": "Jul 20 – 26, 2025",
        "value": 44,
        "has_data": true
      },
      {
        "date": "[redacted-phone]",
        "timestamp": 1753574400,
        "formatted_time": "Jul 27 – Aug 2, 2025",
        "value": 48,
        "has_data": true
      }
    ]
  }
}

Actions

What the Google Trends API does

Action	Description	Concrete use case	Key params
trending_now	Currently trending searches for a geo (title + approx traffic + news articles)	SEO teams call trending_now to get currently trending searches for a geo (title + approx traffic + news articles).	geo
suggest	Keyword autocomplete — candidate topics/entities (the Google Trends suggestion list) so you can pick the right entity (e.g. the 'Apple Inc. — Technology company' topic mid vs the fruit) before querying interest_over_time/related.	Content strategists call suggest to get keyword autocomplete.	keyword, hl
categories	List the Google Trends category taxonomy (id + name, hierarchical) so you can find the right `category` id to narrow interest_over_time / related_queries / interest_by_region (e.g. 7=Finance, 5=Computers & Electronics). Optionally filter by a name substring.	Rank trackers call categories to list the Google Trends category taxonomy (id + name, hierarchical) so you can find the right….	query
realtime_trending	Realtime trending story-clusters for a country (richer than trending_now): each cluster has a title, approximate search-traffic volume, the FULL related-query set, category ids, and an article count. Best for 'what is breaking right now' research.	AI answer-monitoring tools call realtime_trending to get realtime trending story-clusters for a country (richer than trending_now).	geo, hours, limit

Code samples

Call trending_now from your stack

curl -X POST https://api.reefapi.com/google-trends/v1/trending_now \
  -H "x-api-key: $REEF_KEY" \
  -H "content-type: application/json" \
  -d '{"keyword":"bitcoin","geo":"US","timeframe":"today 12-m"}'

import requests

r = requests.post(
    "https://api.reefapi.com/google-trends/v1/trending_now",
    headers={"x-api-key": REEF_KEY},
    json={
  "keyword": "bitcoin",
  "geo": "US",
  "timeframe": "today 12-m"
},
)
print(r.json()["data"])

const res = await fetch("https://api.reefapi.com/google-trends/v1/trending_now", {
  method: "POST",
  headers: {
    "x-api-key": process.env.REEF_KEY,
    "content-type": "application/json",
  },
  body: JSON.stringify({
  "keyword": "bitcoin",
  "geo": "US",
  "timeframe": "today 12-m"
}),
});
const { ok, data, meta, error } = await res.json();

MCP one-liner

Ask your MCP-connected assistant: call reefapi.google-trends.trending_now with {"keyword":"bitcoin","geo":"US","timeframe":"today 12-m"}.

Use cases

Who uses this API and why

Content teams call interest_over_time and related_queries to plan around demand.
Market intelligence uses interest_by_region to target geographies.
Trend trackers use trending_now to catch rising topics early.

FAQ

Questions developers ask before integrating

What is the Google Trends API?

Google Trends API is a ReefAPI endpoint group for search interest over time, by region, and trending now. It returns live JSON through POST requests under /google-trends/v1.

Is the Google Trends API free to try?

Yes. ReefAPI starts with 1,000 free credits, no card required. Google Trends calls use the same shared credit balance as every other ReefAPI engine.

Do I need a Google Trends login or account?

No login to Google Trends is needed for the API response. You call ReefAPI with your x-api-key header, and the playground can run live examples before you create a production key.

How fresh is the Google Trends data?

The page example is captured from a live trending_now call, and production requests fetch live data through ReefAPI rather than a static sample.

How many credits does the Google Trends API use?

Google Trends actions currently cost 1-2 credits per successful call. Failed or blocked calls are free, and all APIs draw from one credit pool.

Can I call Google Trends from an AI assistant or MCP client?

Yes. Connect ReefAPI once through MCP and your assistant can call google-trends actions with the same key, credit pool and JSON envelope used by normal REST requests.

Is the Google Trends API a Google Trends scraper?

It is the managed alternative to a DIY Google Trends scraper. Instead of building and maintaining your own scraper — proxies, headless browsers, captcha and constant breakage — you call one ReefAPI endpoint and get the same search interest over time, by region, and trending now back as clean JSON.

Why does my Google Trends scraper keep getting blocked?

Most Google Trends scrapers break on anti-bot defenses, rate limits and IP bans that need rotating residential proxies and browser fingerprinting to clear. ReefAPI handles all of that for you — no proxies, no captchas, no maintenance — and returns live JSON. Blocked or failed calls are free.

docs / google-trends

Google Trends

Search interest over time, by region, and trending now.

base /google-trends/v14 endpoints

post/google-trends/v1/trending_now1 credit

Currently trending searches for a geo (title + approx traffic + news articles)

Parameter		Allowed / range	Description
geo = US	optional	—	Country code for the trending feed (e.g. US, GB, JP). Required by the RSS feed; defaults to US.

Try in playground →

post/google-trends/v1/suggest1 credit

Keyword autocomplete — candidate topics/entities (the Google Trends suggestion list) so you can pick the right entity (e.g. the 'Apple Inc. — Technology company' topic mid vs the fruit) before querying interest_over_time/related.

Parameter		Allowed / range	Description
keyword	required	—	The term to autocomplete into Trends topics/entities.
hl = en-US	optional	—	UI language for suggestion titles (e.g. en-US, tr, de).

Try in playground →

post/google-trends/v1/categories1 credit

List the Google Trends category taxonomy (id + name, hierarchical) so you can find the right `category` id to narrow interest_over_time / related_queries / interest_by_region (e.g. 7=Finance, 5=Computers & Electronics). Optionally filter by a name substring.

Parameter		Allowed / range	Description
query	optional	—	Optional case-insensitive substring to filter category names (e.g. 'finance', 'sports'). Omit to list the full taxonomy.

Try in playground →

post/google-trends/v1/realtime_trending2 credits

Realtime trending story-clusters for a country (richer than trending_now): each cluster has a title, approximate search-traffic volume, the FULL related-query set, category ids, and an article count. Best for 'what is breaking right now' research.

Parameter		Allowed / range	Description
geo = US	optional	—	Country code for the realtime feed (e.g. US, GB, JP, TR). Country-level only (sub-region suffixes are dropped). Country/US-state names are auto-mapped. Defaults to US.
hours = 24	optional	4 · 24 · 48 · 168	Trailing time window for the realtime feed. Defaults to 24h.
limit = 50	optional	1–300	Max story-clusters to return (1-300; Google returns the most trending first). Defaults to 50.

Try in playground →

Example request · trending_now

curl -X POST https://api.reefapi.com/google-trends/v1/trending_now \
  -H "x-api-key: $REEF_KEY" \
  -H "content-type: application/json" \
  -d '{"geo":"US"}'

Response shape

{
  "ok": true,
  "data": { /* the result */ },
  "meta": {
    "latency_ms": 240,
    "record_count": 12,
    "completeness_pct": 100
  },
  "error": null
}