Google Trends Autocomplete API
google_trends_autocomplete
Discover Google Trends topics and topic IDs from a search phrase.
Autocomplete helps applications turn an ambiguous phrase into Google Trends topic identifiers and localized topic labels before running deeper trend analysis.
TYPETopic suggestionsPRICE$0.00625 per requestRESPONSEStructured JSON
{}Google Trends Autocomplete API Pricing
Current pricing from the APINEED catalog. Failed requests are refunded; server usage records remain authoritative.
Discount information
The catalog price is the amount advertised by APINEED. No separate comparison price or savings percentage is published for this tool.
| Price | Billing unit | Amount | Discount |
|---|---|---|---|
| Comparison price | Request | Not published | Not available |
| APINEED | Successful request | $0.00625 per request | Catalog price |
Final charges are recorded in the response usage. No unverified competitor prices are used.
Quick Start
Invoke Google Trends Autocomplete 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_autocomplete/invoke.
curl 'https://apineed.com/v1/tools/google_trends_autocomplete/invoke' \
-H "Authorization: Bearer $API_NEED_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"language": "en",
"query": "artificial intelligence"
}'Read the response
Use output.suggestions for the result and usage.price_usd for the settled request price.
const suggestions = response.output.suggestions;Endpoint
This endpoint uses bearer-token authentication and returns a synchronous normalized JSON response.
POST
/v1/tools/google_trends_autocomplete/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 Autocomplete API Parameters
Only query is required. Omit language to use the default language.
| Name | Type | Requirement | Values | Description |
|---|---|---|---|---|
query | string | Required | 1–500 characters | The phrase to expand into Google Trends topics. |
language | string | Optional | Pattern: ^[A-Za-z]{2}$ | Optional two-letter result language. Defaults upstream to en. |
Google Trends Autocomplete API Introduction
A practical guide to the request, response, billing, and application use cases.
Google Trends Autocomplete API
Autocomplete helps applications turn an ambiguous phrase into Google Trends topic identifiers and localized topic labels before running deeper trend analysis.
Topic discovery
Resolve ordinary phrases into stable Google Trends topic IDs.
Localized labels
Request suggestions in a two-letter result language.
Trend workflow setup
Let a user choose the intended topic before running a trend comparison.
Request contract
Send a JSON object to /v1/tools/google_trends_autocomplete/invoke. Use the required fields, supported optional parameters, and bounds listed above. Undocumented parameters are not guaranteed to be supported.
Response and usage
Read the tool result from output.suggestions 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 Autocomplete API do?
Autocomplete helps applications turn an ambiguous phrase into Google Trends topic identifiers and localized topic labels before running deeper trend analysis.
How do I authenticate?
Send a POST request to /v1/tools/google_trends_autocomplete/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: language. 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.