Google Trends
Retrieve Google Trends data for one to five comma-separated terms. time_range accepts all, now 1-H, now 4-H, now 1-d, now 7-d, today 1-m, today 3-m, today 12-m, today 5-y, or an ordered YYYY-MM-DD date pair from 2004 through today.
Request
- Base URL: https://api.prismcrawl.com
- URL: https://api.prismcrawl.com/v1/google/trends
- Auth: API key in header x-api-key
Request body
Text to search for on the selected service. At most 8,192 UTF-8 bytes.
Two-letter country or storefront code, such as us or gb.
Provider-supported language code, such as en.
A category identifier supported by this operation.
Provider-supported time filter.
Device presentation for the source request.
Return the encoded original response rather than parsed JSON.
Do not archive source or parsed response artifacts.
Chart: TIMESERIES (default), GEO_MAP for comparing terms, GEO_MAP_0 for one term, or related topics/queries. Cannot be combined with the legacy category selector.
Google Trends location code. An empty string selects worldwide. A comma-separated location per term is supported for TIMESERIES. Overrides country.
Geographic chart resolution, for GEO_MAP and GEO_MAP_0 only.
Google Trends topic category ID. Defaults to 0 (all categories).
Search property: empty for web search, images, news, froogle (shopping), or youtube.
Relative or custom date range; alias of time_range. For TIMESERIES, comma-separated custom ranges match the query order.
Also retrieve the source CSV rows.
Include low search volume regions in geographic charts.
UTC offset in minutes, using the browser convention (420 = UTC-07:00). Defaults to 0.
Response content format. md returns Markdown in data.content with data.format=md; the JSON success/request envelope remains. Accept: text/markdown also selects Markdown unless output or html=true is explicit. html is an alias for html=true and retains the existing Brotli/Base64 source format.
Select fields within data.content for JSON or Markdown. Supports comma-separated paths, non-negative array indices, half-open slices [0:3] (either bound may be omitted), [] and .{nested,subqueries}. Up to128 selections and16 levels. Missing fields are omitted; selected declared fields retain their zero defaults. The request envelope and credit headers remain. Include next_page_token when pagination is needed. Incompatible with HTML output. This changes response presentation only; tracing-enabled history retains the complete JSON result.
Accepted for compatibility. Searches are always fetched without a result cache for either value; normal successful-request billing applies.
Example request
{
"json_restrictor": "results[].{title,url},has_next_page,next_page_token"
}Response
Request completed. One credit is charged, including recognized empty or unavailable source results and source inventory changes discovered after a valid continuation is fetched. These completed responses may preserve verified partial results; operational failures remain errors.
Changes
No recorded changes to this operation across all 1 revision of this API.