Google Trends API
google_trends
87.5% off
Research search interest, resolve Trends topics, and discover current trending searches through one API collection.
Selected API: Google Trends Search API — Analyze Google search interest over time or compare regional interest for up to five terms.
Use this API for demand analysis, seasonality, market comparisons, and regional research. The response keeps the relevant Google Trends dataset under output.data while APINEED provides one key, one balance, and consistent request billing.
APIS3PRICE$0.003125 per requestRESPONSEStructured JSON
{
"request_id": "example_google_trends_search",
"tool": "google_trends_search",
"output": {
"data": {
"interest_over_time": {
"timeline_data": [
{
"date": "May 26, 2026",
"timestamp": "1779753600",
"values": [
{
"extracted_value": "24",
"query": "OpenAI",
"value": 24
},
{
"extracted_value": "94",
"query": "ChatGPT",
"value": 94
}
]
}
],
"timerange_data": []
}
},
"query": "OpenAI,ChatGPT"
},
"usage": {
"price_usd": "0.003125",
"quota": 1563
}
}Google Trends Search API Pricing
Current pricing from the APINEED catalog. Failed requests are refunded; server usage records remain authoritative.
Quick Start
Invoke Google Trends Search with one APINEED key and a JSON request body.
Use your APINEED API key
Reuse the same APINEED API key that your application already uses for LLM, image, and video APIs. Keep it server-side.
Create API keyexport API_NEED_API_KEY=sk-apineed-v1-...Send the request
POST the same input shown in the Playground to /v1/tools/google_trends_search/invoke.
curl 'https://apineed.com/v1/tools/google_trends_search/invoke' \
-H "Authorization: Bearer $API_NEED_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"data_type": "INTEREST_OVER_TIME",
"date": "today 3-m",
"geo": "US",
"language": "en",
"query": "OpenAI,ChatGPT",
"tz": 0
}'Read the response
Use output.data for the result and usage.price_usd for the settled request price.
const trendData = response.output.data;Endpoint
This endpoint uses bearer-token authentication and returns a synchronous normalized JSON response.
POST
/v1/tools/google_trends_search/invoke- Authorization
- Bearer $API_NEED_API_KEY
- Content-Type
- application/json
- Billing
- $0.003125 per request on successful invocation
- Response
- request_id, tool, output, usage
Google Trends Search API Parameters
Only query is required. You may compare up to five comma-separated terms; omitted filters use their default behavior.
| Name | Type | Requirement | Values | Description |
|---|---|---|---|---|
query | string | Required | 1–500 characters | One to five search terms or topic IDs separated by commas. |
cat | string | Optional | 0–12 characters | Optional Google Trends category ID. Defaults upstream to 0. |
data_type | string | Optional | INTEREST_OVER_TIME, REGION_BREAKDOWN | Whether to return a timeline or a regional breakdown. |
date | string | Optional | 1–64 characters | A documented predefined or custom Google Trends date range. |
geo | string | Optional | Pattern: ^[A-Za-z]{2}(?:-[A-Za-z0-9]{1,3})?$ | Optional country or subregion code. Omit for worldwide data. |
gprop | string | Optional | IMAGES, NEWS, SHOPPING, YOUTUBE | Optional Google property filter. |
language | string | Optional | Pattern: ^[A-Za-z]{2}$ | Optional two-letter result language. Defaults upstream to en. |
region | string | Optional | COUNTRY, REGION, DMA, CITY | Geographic aggregation used for region breakdowns. |
tz | integer | Optional | -1439–1439 | Timezone offset in minutes. |
Google Trends API Introduction
One collection page for the related APIs, with a developer guide for the currently selected request contract.
Google Trends API overview
Google Trends API is a JSON interface for researching relative search interest, resolving phrases to Trends topics, and discovering searches that are accelerating in a selected market. APINEED presents it as a tool: an application sends a bounded request, receives a stable envelope, and uses the same key, balance, and usage records as model traffic. It fits server products, agents, pipelines, dashboards, and scheduled jobs that need structured data. It is not the limited-access official Google Trends API alpha; APINEED publishes its own collection, member endpoints, schemas, authentication, pricing, and response envelope. The live catalog publishes the endpoint, price, schemas, example payload, and limits together. Start with the smallest valid request, verify the response, and add optional controls only when the product needs them. This keeps a Google Trends API integration observable and avoids assumptions borrowed from a different service.
Designing a Google Trends API request
Send the Google Trends API request as JSON to the selected Google Trends API member endpoint shown on this page with an APINEED bearer key. The collection contains three focused contracts. Interest Search requires query; Autocomplete requires query; Trending Now requires geo. Language, geography, time range, property, category, pagination-like limits, and other controls belong only to the member schemas that publish them. Unknown top-level fields are rejected so typos fail clearly instead of being ignored. Omitted values keep documented defaults, while explicit zero or false values remain meaningful. Validate types, enums, ranges, and pagination before sending traffic. Store the key on the server; never place it in a browser bundle, URL, analytics event, or log. The signed-in Playground tests through the website session without exposing a key. In production, set a timeout, attach a correlation ID, and retain request_id so a Google Trends API call can be reproduced and investigated.
Reading the Google Trends API response
A successful Google Trends API call returns request_id, tool, output, and usage. request_id identifies the operation, output contains tool data, and usage records the settled dollar price and quota. Every member returns the APINEED envelope, but output differs by operation: Interest Search returns a trend dataset, Autocomplete returns topic suggestions, and Trending Now returns a bounded trend list. Callers must parse the selected member schema rather than assume one universal output. Treat optional output fields as optional: an empty array may be valid, missing text must not break parsing, and numeric units should be preserved. Store request_id with downstream records and read the final charge from usage rather than duplicating billing math. On failure, inspect the HTTP status and public error code instead of parsing the body as success. Retry only transient failures. A typed response boundary lets the application tolerate variation without discarding useful fields.
Interpreting Google Trends API data correctly
Interpretation is often harder than transport. Google Trends API data can be valid yet unsuitable for a conclusion when geography, language, time range, ranking context, sampling, freshness, or missing fields are ignored. Google Trends values are normalized and relative, not absolute search counts. Topic suggestions identify candidates rather than popularity, and Trending Now represents recent acceleration rather than a permanent ranking. Geography, window, category, property, sampling, and term-versus-topic choices all affect meaning. Store the request controls and retrieval time beside the response. Do not turn a preview, rank, score, count, or label into a stronger claim than it supports. For customer-facing answers, verify an underlying source where possible and distinguish observation from inference. Repeated Google Trends API calls may change, so decide whether the workflow needs live data, a cached snapshot, or a dated record. These rules keep convenient JSON from being treated as unquestionable evidence. [1][2][3][4]
Google Trends API workflows and use cases
Use Google Trends API as one explicit step in a larger workflow. Use the collection for seasonality and market research, topic resolution, editorial monitoring, regional analysis, product comparison, anomaly detection, or bounded agent retrieval. Pick only the member operations needed by the product and retain every operation's request context. For an agent, define when it may call the tool, which user input is copied, how many items are allowed, and which fields enter model context. A pipeline should retain the request, execution time, request_id, and normalization version. A dashboard should show relevant market, language, period, or location controls. Monitoring jobs should deduplicate repeated items and alert on meaningful change. Start with one measurable use case and test positive, empty, localized, malformed, and rate-limited requests before expanding access. Retrieval belongs to Google Trends API; ranking, policy, summarization, and user experience remain application responsibilities.
Accuracy, freshness, and limits of Google Trends API
Do not treat Google Trends API as an unlimited or permanent database. The collection does not provide a census, exact query volume, proof of intent, sentiment, public opinion, or a guarantee that every topic and optional metric is present. Results can change and must be interpreted within the selected comparison and retrieval time. Results can change when a page is re-ranked, a place changes, a topic cools, or an optional field disappears. The APINEED schema defines accepted and normalized data; it does not promise a maximum item count or every optional attribute. Handle empty and partial results from the first release. Cache only when staleness is acceptable and store a retrieval time. Google Trends API can assist discovery for sensitive legal, medical, financial, safety, or compliance work, but it should not be the only authority. Document blind spots and let users inspect material conclusions. [1][2][3][4]
Production reliability for Google Trends API
A production Google Trends API client needs bounded concurrency, timeouts, jittered backoff, and a retry budget. Never retry validation or authentication failures. Retry a timeout or temporary dependency failure only when the call is safe and still useful. Record latency, status, public error code, request_id, and settled usage, while redacting credentials and sensitive query text. Test each member independently, including one and five comparison terms, topic IDs, ambiguous phrases, empty suggestions, worldwide and regional requests, every current Trending Now window, explicit bounds, low-volume zeros, missing optional metrics, and partial workflow failure. Contract tests should cover required fields, explicit zero or false values, maximum lengths, pagination boundaries, empty output, and representative optional fields. A low-frequency canary may detect a dependency outage, but it should not create unnecessary billable traffic. These controls prevent one delayed Google Trends API dependency from producing duplicated work.
Billing, rate limits, and caching
The live catalog publishes the current Google Trends API price; do not hardcode it. A successful response includes usage.price_usd and usage.quota, while usage logs provide reconciliation. Let server settlement decide failed-call billing. Rate limits protect users and shared capacity, so pace bursts, honor Retry-After when supplied, and prevent synchronized worker retries. Cache members independently. Historical interest may tolerate a longer expiration than topic suggestions, while Trending Now usually needs a short expiration. Include every result-shaping member parameter in the cache key and preserve the retrieval time. A cache key must include every result-shaping parameter, use an explicit expiration, and keep sensitive input out of shared namespaces. Catalog pricing, bounded retries, and intentional caching make Google Trends API cost predictable without trading correctness for a lower request count.
Choosing an endpoint in Google Trends API
Google Trends API is a collection rather than one oversized request contract. Choose the member API by the decision you need to make: measure interest, resolve an ambiguous phrase to a topic, or discover searches accelerating now. Each member uses its own endpoint, required fields, validation rules, and response shape. The selector on this page changes the Playground, parameter table, cURL example, price, and example response without creating duplicate documentation pages. A client should call only the selected member endpoint; the collection slug is for documentation and is not an invocation URL. Keeping Google Trends API members separate makes failures clearer and prevents unrelated parameters from silently leaking into another operation. Before implementation, record which member answers the product question, then build and test against that member's published schema.
Google Trends Search API in the Google Trends API
Google Trends API includes Google Trends Search API at /v1/tools/google_trends_search/invoke. This member is designed for measuring relative interest over time or comparing geographic interest for one to five terms or topic identifiers. query is required; language, geo, region, data_type, timezone offset, category, Google property, and date range are optional controls published in its schema. output.query preserves the comparison expression and output.data contains either interest-over-time or regional data selected by data_type. Use Google Trends Search API when the product needs a dated comparison, seasonality, relative demand, or a geographic breakdown rather than a list of current headlines. Do not send fields copied from another Google Trends API member merely because the operations share a page: the backend validates each JSON object against the selected contract. In an agent, expose the member with a precise description and a bounded input schema so the model can choose it deliberately. In application code, store the member name with request_id and usage because a later audit needs to distinguish which Google Trends API operation produced the data. The shared Introduction and Q&A explain collection-wide behavior, while the member's parameter table and examples remain the source of truth for that call. [1][2][3][4]
Google Trends Autocomplete API in the Google Trends API
Google Trends API includes Google Trends Autocomplete API at /v1/tools/google_trends_autocomplete/invoke. This member is designed for resolving an ordinary phrase into candidate topic labels, types, URLs, and topic identifiers before deeper analysis. query is required and language is optional; this member does not accept a trend period, geography, or result-count field. output.query records the phrase and output.suggestions returns candidate topics with a required title and optional topic_id, type, and URL. Use Google Trends Autocomplete API when a phrase may refer to several entities or the workflow wants a topic ID that can group related searches across languages. Do not send fields copied from another Google Trends API member merely because the operations share a page: the backend validates each JSON object against the selected contract. In an agent, expose the member with a precise description and a bounded input schema so the model can choose it deliberately. In application code, store the member name with request_id and usage because a later audit needs to distinguish which Google Trends API operation produced the data. The shared Introduction and Q&A explain collection-wide behavior, while the member's parameter table and examples remain the source of truth for that call. [1][2][3][4]
Google Trends Trending Now API in the Google Trends API
Google Trends API includes Google Trends Trending Now API at /v1/tools/google_trends_trending_now/invoke. This member is designed for retrieving a bounded list of currently accelerating search topics for a selected country and recent time window. geo is required; hours, language, max_results, and max_related_queries are optional and bounded by the published schema. output.geo confirms the market and output.trends contains a title and active state plus optional timestamps, volume, increase, categories, and related queries. Use Google Trends Trending Now API when the product needs timely discovery, newsroom monitoring, editorial triage, or alert candidates rather than historical comparison. Do not send fields copied from another Google Trends API member merely because the operations share a page: the backend validates each JSON object against the selected contract. In an agent, expose the member with a precise description and a bounded input schema so the model can choose it deliberately. In application code, store the member name with request_id and usage because a later audit needs to distinguish which Google Trends API operation produced the data. The shared Introduction and Q&A explain collection-wide behavior, while the member's parameter table and examples remain the source of truth for that call. [1][2][3][4]
Google Trends API Q&A
One shared Q&A for the API group, covering selection, interpretation, authentication, billing, rate limits, and production use.
What is the APINEED Google Trends API?
APINEED Google Trends API is a server-side JSON tool for researching relative search interest, resolving phrases to Trends topics, and discovering searches that are accelerating in a selected market. It shares the APINEED key, balance, usage logs, and error envelope. The live Google Trends API schema defines supported requests and responses.
Is Google Trends API an official Google API?
No. APINEED Google Trends API is not an official Google product. It is not the limited-access official Google Trends API alpha; APINEED publishes its own collection, member endpoints, schemas, authentication, pricing, and response envelope. Integrate against the APINEED endpoint and schema; use Google documentation only for claims about Google products or data interpretation. [1][2][3][4]
Which fields are required by Google Trends API?
The collection contains three focused contracts. Interest Search requires query; Autocomplete requires query; Trending Now requires geo. Language, geography, time range, property, category, pagination-like limits, and other controls belong only to the member schemas that publish them. The live parameter table lists required flags, types, enums, patterns, and bounds. Unknown top-level fields are rejected so a Google Trends API client receives a clear validation error.
What does Google Trends API return?
Every member returns the APINEED envelope, but output differs by operation: Interest Search returns a trend dataset, Autocomplete returns topic suggestions, and Trending Now returns a bounded trend list. Callers must parse the selected member schema rather than assume one universal output. A successful Google Trends API call also includes request_id, tool, output, and usage. Keep request_id for support and use usage.price_usd as the settled charge.
How should I interpret Google Trends API results?
Google Trends values are normalized and relative, not absolute search counts. Topic suggestions identify candidates rather than popularity, and Trending Now represents recent acceleration rather than a permanent ranking. Geography, window, category, property, sampling, and term-versus-topic choices all affect meaning. Preserve request controls and retrieval time, tolerate missing optional fields, and do not treat a rank, relative score, preview, or category from Google Trends API as a stronger fact than its source supports. [1][2][3][4]
Can I use Google Trends API with AI agents or RAG?
Yes. Use the collection for seasonality and market research, topic resolution, editorial monitoring, regional analysis, product comparison, anomaly detection, or bounded agent retrieval. Pick only the member operations needed by the product and retain every operation's request context. Keep each Google Trends API call bounded, treat returned text as untrusted, verify important sources, and pass only necessary fields into model context.
How much does a Google Trends API request cost?
Use the live catalog price. A successful Google Trends API response records settlement in usage.price_usd and usage.quota. Do not hardcode the displayed price because pricing can change independently of the schema.
Are failed Google Trends API requests billed?
Use APINEED settlement and usage logs as the billing record. Do not create a client-side charge after a failed Google Trends API call. Retry only transient failures with a bounded budget.
How should I handle Google Trends API rate limits?
Pace bursts, bound concurrency, honor Retry-After when supplied, and use jittered backoff. Do not retry invalid input or authentication failures. Coordinate workers sharing Google Trends API through a queue or limiter.
Can Google Trends API responses be cached?
Yes, when the freshness window is acceptable. Cache members independently. Historical interest may tolerate a longer expiration than topic suggestions, while Trending Now usually needs a short expiration. Include every result-shaping member parameter in the cache key and preserve the retrieval time. Include every result-shaping Google Trends API parameter in the key, store retrieval time, set an expiration, and keep sensitive input out of shared caches.
What limitations should I test before launch?
The collection does not provide a census, exact query volume, proof of intent, sentiment, public opinion, or a guarantee that every topic and optional metric is present. Results can change and must be interpreted within the selected comparison and retrieval time. Test Google Trends API empty results, missing fields, localization, maximum lengths, pagination, timeouts, rate limits, and representative production queries. Do not assume another API’s fields are supported. [1][2][3][4]
What is the safest way to migrate to Google Trends API?
Compare both paths with a fixed evaluation set, log request_id and latency in a small canary, move traffic gradually, keep rollback, and update clients from the published Google Trends API schema.
Why does Google Trends API have multiple endpoints?
Google Trends API separates different operations so every request has a focused schema and predictable response. The current members are Google Trends Search API, Google Trends Autocomplete API, Google Trends Trending Now API. Select a member on the page to see its endpoint, parameters, price, request example, and response example.
Which Google Trends API endpoint should I call first?
Start from the product question. Use topic autocomplete when text is ambiguous, interest search when you need relative interest over time or by region, and Trending Now when you need currently accelerating searches. A Google Trends API workflow does not need to call every member.
Can one Google Trends API request call every member?
No. Each Google Trends API member has a separate invocation endpoint and contract. Orchestrate multiple calls in application code or an agent, preserve each request_id, and apply independent retry and caching policies so a partial failure does not hide which operation failed.
Do all Google Trends API members return the same JSON?
No. They share the APINEED envelope—request_id, tool, output, and usage—but output is specific to the selected Google Trends API member. Generate types from the member schema or branch on the tool name instead of forcing every response into one data model.
Does the shared Google Trends API Introduction replace member documentation?
No. The shared Google Trends API Introduction and Q&A explain selection, interpretation, reliability, billing, and collection-wide workflows. The selected member's endpoint, parameter table, cURL, price, and example response define the concrete request and remain visible on the same page.