Google logo

Google Trends Search API

google_trends_search

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.

TYPETimeline or region dataPRICE$0.00625 per requestRESPONSEStructured JSON

Google Trends Search API Playground

Edit the JSON request and inspect the API response. Requests use your signed-in APINEED account and balance; no API key is needed here.

Request JSON
$0.00625 per requestSign in required. Failed requests are refunded.
Response JSON
{}
ReadySend a request to see the response.

Google Trends Search API Pricing

Current pricing from the APINEED catalog. Failed requests are refunded; server usage records remain authoritative.

APINEED price$0.00625 per requestBilled from recorded usage
Billing policySuccessful requests onlyFailed requests are refunded
Account balanceOne shared balanceUse the same balance and API keys as your models

Discount information

The catalog price is the amount advertised by APINEED. No separate comparison price or savings percentage is published for this tool.

PriceBilling unitAmountDiscount
Comparison priceRequestNot publishedNot available
APINEEDSuccessful request$0.00625 per requestCatalog price

Final charges are recorded in the response usage. No unverified competitor prices are used.

Quick Start

Invoke Google Trends Search with one APINEED key and a JSON request body.

1

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 key
export API_NEED_API_KEY=sk-apineed-v1-...
2

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
}'
3

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.00625 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.

NameTypeRequirementValuesDescription
querystringRequired1–500 charactersOne to five search terms or topic IDs separated by commas.
catstringOptional0–12 charactersOptional Google Trends category ID. Defaults upstream to 0.
data_typestringOptionalINTEREST_OVER_TIME, REGION_BREAKDOWNWhether to return a timeline or a regional breakdown.
datestringOptional1–64 charactersA documented predefined or custom Google Trends date range.
geostringOptionalPattern: ^[A-Za-z]{2}(?:-[A-Za-z0-9]{1,3})?$Optional country or subregion code. Omit for worldwide data.
gpropstringOptionalIMAGES, NEWS, SHOPPING, YOUTUBEOptional Google property filter.
languagestringOptionalPattern: ^[A-Za-z]{2}$Optional two-letter result language. Defaults upstream to en.
regionstringOptionalCOUNTRY, REGION, DMA, CITYGeographic aggregation used for region breakdowns.
tzintegerOptional-1439–1439Timezone offset in minutes.

Google Trends Search API Introduction

A practical guide to the request, response, billing, and application use cases.

Integration guide·Based on the live API catalog
01

Google Trends Search API

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.

02

Demand over time

Measure how interest changes across hours, days, months, or multi-year ranges.

03

Term comparison

Compare as many as five products, topics, or Google topic IDs in one request.

04

Regional analysis

Switch to region breakdowns to discover where each topic is strongest.

05

Request contract

Send a JSON object to /v1/tools/google_trends_search/invoke. Use the required fields, supported optional parameters, and bounds listed above. Undocumented parameters are not guaranteed to be supported.

06

Response and usage

Read the tool result from output.data and the settled charge from usage.price_usd. Keep request_id for troubleshooting. Preserve optional response fields rather than assuming they are always present.

Common Questions

Practical answers about authentication, parameters, pricing, and integration.

What does Google Trends Search API do?

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.

How do I authenticate?

Send a POST request to /v1/tools/google_trends_search/invoke with your APINEED API key in the Authorization: Bearer header. The same key can be used for model APIs. Keep the key on your server, not in browser code.

Can I try this API without entering an API key?

Yes. The Playground uses your signed-in APINEED account and shared balance. Sign in to send a request, or add funds if your balance is insufficient.

Which input fields are required?

Required fields: query. Check the parameter table for types, allowed values, and limits.

Can I omit optional parameters?

Yes. Optional fields: cat, data_type, date, geo, gprop, language, region, tz. Omitted fields are not sent. Explicit false and 0 values are preserved; use the defaults and limits documented in the parameter table.

How much does a request cost?

The current catalog price is $0.00625 per request. The final charge is recorded in usage.price_usd and your account usage logs. Failed requests are refunded.

How should I read the response?

A successful invocation returns request_id, tool, output, and usage. Read the result from output, preserve request_id for troubleshooting, and inspect usage for the settled charge. The Playground shows the returned JSON without changing it.