Collectors · SEO & keywords
Google Trends API in Python
Today's trending searches for a country, with traffic band and attached news stories. One POST from Python with the input, rows back as JSON with 10 fields, $0.0005 per delivered trend. No proxies or parsers to maintain.

First call
Install, call, read the rows.
pip install requestsimport os, requests
r = requests.post(
"https://api.quanticdata.io/v1/scraper/collectors/google_trends/run",
headers={"Authorization": f"Bearer {os.environ['QD_API_KEY']}"},
json={
"country": "us",
"max_results": 10,
},
timeout=120,
)
r.raise_for_status()
run = r.json()["payload"]
print(run["count"], "rows,", run["cost"]["usd"], "USD")
for row in run["results"]:
print(row.get("query"), row.get("approx_traffic"), row.get("published"), row.get("image"))The key comes from an environment variable, never from the code. The run answers in the same request when it finishes in time; payload.results holds the rows and payload.cost what they cost.
Request parameters
What the collector takes.
| Parameter | Type | Required | Meaning |
|---|---|---|---|
country | string | no | ISO 3166-1 alpha-2 code — which country's trending feed to read (default us). |
max_results | integer | no (default 10) | How many trends to deliver at most (1–20). You pay only for delivered trends. |
Response fields
10 fields per trend.
| Field | Type | What it holds |
|---|---|---|
rank | integer | Position in today's feed. |
query | string | The trending search query. |
approx_traffic | string, nullable | Google's traffic band, e.g. "1000+". |
published | string, nullable | When Google surfaced the trend. |
image | string, nullable | Representative image URL. |
articles | object[] | News stories attached to the trend ({ title, url, source }). |
country | string | Country the feed was read for. |
traffic_min | integer, nullable | approx_traffic as a number ("2000+" → 2000). |
published_at | string, nullable | published as an ISO 8601 timestamp. |
article_count | integer | How many stories are attached. |
Add ?format=csv to the runs endpoint to get the same rows as CSV.
Long runs
Run in the background, then poll.
A run that needs more time can go to the background: send "async": true, get 202 with the run id, and poll the runs endpoint until the status is done. Reading a run is free.
import os, time, requests
H = {"Authorization": f"Bearer {os.environ['QD_API_KEY']}"}
r = requests.post("https://api.quanticdata.io/v1/scraper/collectors/google_trends/run", headers=H,
json={**{"country":"us","max_results":10}, "async": True}, timeout=30)
run_id = r.json()["payload"]["run_id"]
while True:
run = requests.get(f"https://api.quanticdata.io/v1/scraper/collectors/runs/{run_id}", headers=H, timeout=30).json()["payload"]
if run["status"] in ("done", "failed"):
break
time.sleep(5)
print(run["status"], run["count"])Errors
What can come back, and what is billed.
| Status | Meaning | Billed |
|---|---|---|
400 | The input does not match the collector (payload.errors) | No |
401 | Missing or wrong API key | No |
402 | Balance and free credit do not cover the run: top up | No |
422 | The input can never resolve; retrying the same input cannot help | No |
424 | The run failed at the source (blocked, timed out, layout changed); safe to retry | No |
429 | Rate limit or a per-account brake; wait for Retry-After | No |
Only delivered rows are billed: a run that delivers nothing costs nothing.
Price
$0.0005 per delivered trend.
| Rows | Cost |
|---|---|
| 1 | $0.0005 |
| 1,000 | $0.50 |
| 10,000 | $5.00 |
Up to 20 trends per run; split larger jobs into several runs. The $2 free credit every month covers about 4,000 trends. No subscription; paid tiers lower the unit price. All collector prices: collector pricing.
Before you run it
Questions developers ask
Is there a free Google Trends — trending now API?
Every account gets $2 of free usage each month, about 4,000 trends of this collector at $0.0005 each, with no card.
Do I have to handle proxies, retries or blocks?
No. The collector runs on our network and handles them; a run blocked at the source returns 424 and is not billed.
How many rows can one run return?
Up to 20 trends per run (the max_results input, where the collector has one).
Can an AI agent run it?
Yes: the MCP server exposes it as the run_collector tool, with the same input and price. See the MCP server.
Run it on the free credit.
Create an API key, export it as QD_API_KEY and run the example. $0.0005 per delivered trend, no subscription.