qstringrequired
Parameter defines the query you want to search. You can use anything that you would use in a regular Google Trends search. The query is used to retrieve suggested searches.
https://api.sandbase.ai/v1/api/google/trends-autocompleteGet Google Trends topic and query suggestions for a keyword, with the topic ID to use in Google Trends lookups.
Your output will appear here
Complete the inputs, then click Run.
Get Google Trends topic and query suggestions for a keyword, with the topic ID to use in Google Trends lookups.
curl -X POST "https://api.sandbase.ai/v1/api/google/trends-autocomplete" \
-H "Authorization: Bearer $SANDBASE_API_KEY" \
-H "Content-Type: application/json" \
-d '{"q": "coffee"}'
The result is returned in outputs[0].data as structured JSON.
| Name | Type | Required | Description |
|---|---|---|---|
q | string | Yes | Parameter defines the query you want to search. You can use anything that you would use in a regular Google Trends search. The query is used to retrieve suggested searches. |
hl | string | No | Parameter defines the language to use for the Google Trends Autocomplete search. It's a two or three-letter language code. (e.g., en for English, es for Spanish, or fr for French), optionally followed by a two-letter or three-digit re |
json_restrictor | string | No | Parameter defines the fields you want to include in the output, reducing payload size for faster response. See the JSON Restrictor documentation for more details. |
$0.010 per successful call. Failed calls are not charged.
Start building
Platform API endpoint with unified authentication and usage tracking.
# The quoted heredoc keeps Unicode and shell metacharacters unchanged.
result=$(curl --fail-with-body --silent \
-X POST "https://api.sandbase.ai/v1/api/google/trends-autocomplete" \
-H "Authorization: Bearer $SANDBASE_API_KEY" \
-H "Content-Type: application/json" \
--data-binary @- <<'SANDBASE_JSON'
{
"q": "coffee"
}
SANDBASE_JSON
)
printf '%s\n' "$result"Set your SandBase API key in your server environment. Requests use Bearer authentication.
export SANDBASE_API_KEY="YOUR_API_KEY"Keep your key on the server. Do not expose it in browser code.
qstringrequiredParameter defines the query you want to search. You can use anything that you would use in a regular Google Trends search. The query is used to retrieve suggested searches.
hlstringParameter defines the language to use for the Google Trends Autocomplete search. It's a two or three-letter language code. (e.g., `en` for English, `es` for Spanish, or `fr` for French), optionally followed by a two-letter or three-digit region code (e.g., `en-gb` for British English, or `es-419` for Latin American Spanish). Head to the Google languages page for a full list of supported Google languages.
json_restrictorstringParameter defines the fields you want to include in the output, reducing payload size for faster response. See the JSON Restrictor documentation for more details.
Saved example response for this API; no live request is made when viewing it.
No saved response has been published. Run the API in Playground to inspect its response.
Explore more
| API | Price | Response |
|---|---|---|
Google Trends AutocompleteThis API Google | $0.01 per call | JSON |
Google | $0.01 per call | JSON |
Google | $0.015 per call | JSON |
Google | From $0.002 per call | JSON |
Google | From $0.0015 per call | JSON |
Google | $0.01 per call | JSON |
Questions
Send a POST request to https://api.sandbase.ai/v1/api/google/trends-autocomplete with your SandBase API key in the Authorization header (Bearer) and the parameters as a JSON body. You can also try it in the Playground on this page without writing code.
$0.01 per call, billed from your SandBase balance. You are only charged for calls you make; there is no subscription.
Required: q (string). Optional: hl (string) and json_restrictor (string). The Parameters table and the Playground on this page list every field.
A JSON response returned in the same HTTP request (synchronous).
No. Google Trends Autocomplete runs through SandBase, so one SandBase API key covers this endpoint and every other API and model in the catalog. You do not need to apply for Google API access separately.