trends.google.com APItrends.google.com ↗
Retrieve real-time trending searches from Google Trends for any country. Get search volume, growth percentage, related queries, and category filters via one endpoint.
curl -X GET 'https://api.parse.bot/scraper/dd96362a-dd1b-43d9-a5e8-ed8db3cd66ae/get_trending?geo=GB&hours=48&limit=3' \ -H 'X-API-Key: $PARSE_API_KEY'
Get currently trending searches from Google Trends for a specific country. Returns ranked trending topics with search volume, growth metrics, related queries, and topic categories.
| Param | Type | Description |
|---|---|---|
| geo | string | ISO 2-letter country code (e.g., US, GB, DE, JP, BR) |
| hours | integer | Time window in hours to look back for trends (e.g., 4, 24, 48, 168) |
| limit | integer | Maximum number of trending topics to return (1-500) |
| category | integer | Category filter. 0=All, 1=Business, 2=Entertainment, 3=Health, 4=Sci/Tech, 5=Top Stories, 7=Sports, 11=World, 18=Gaming, 20=Weather |
| language | string | Language code for results (e.g., en, es, fr, de, ja) |
{
"type": "object",
"fields": {
"geo": "string - country code used for the request",
"hours": "integer - time window in hours",
"trends": "array of trend objects with title, geo, started_at, search_volume, search_volume_formatted, growth_percentage, related_queries, categories, article_count, and rank",
"category": "integer - category filter used",
"language": "string - language code used for the request",
"returned": "integer - number of trends returned (limited by limit param)",
"total_available": "integer - total trends available from Google"
},
"sample": {
"data": {
"geo": "US",
"hours": 24,
"trends": [
{
"geo": "US",
"rank": 1,
"title": "cruz azul - guadalajara",
"categories": [
"Sports"
],
"started_at": 1778721000,
"article_count": 34,
"search_volume": 200000,
"related_queries": [
"cruz azul - guadalajara",
"cruz azul vs guadalajara",
"liga mx"
],
"growth_percentage": 1000,
"search_volume_formatted": "200K+"
},
{
"geo": "US",
"rank": 2,
"title": "alex murdaugh",
"categories": [
"Lifestyle"
],
"started_at": 1778682000,
"article_count": 15,
"search_volume": 200000,
"related_queries": [
"alex murdaugh",
"murdaugh murders"
],
"growth_percentage": 1000,
"search_volume_formatted": "200K+"
}
],
"category": 0,
"language": "en",
"returned": 2,
"total_available": 474
},
"status": "success"
}
}About the trends.google.com API
The Google Trends API exposes 1 endpoint — get_trending — that returns up to 500 ranked trending search topics for any supported country, including 7 response fields per trend such as search volume, growth percentage, and related queries. You can filter by ISO country code, time window, content category, and language, making it straightforward to pull region-specific trend data for any supported market.
What the API Returns
The get_trending endpoint returns an array of trend objects, each containing a title, search_volume, search_volume_formatted, growth_percentage, related_queries, started_at timestamp, and geographic context via geo. The response also surfaces metadata: the total_available count of trends Google holds for the request window versus the returned count actually delivered, letting you paginate or adjust the limit parameter (1–500) accordingly.
Filtering and Scope
The geo parameter accepts any ISO 3166-1 alpha-2 country code (e.g., US, GB, JP, BR). The hours parameter controls the lookback window — pass 4 for near-real-time bursts, 168 for a full week of trend data. The category parameter narrows results to one of eight verticals: All (0), Business (1), Entertainment (2), Health (3), Sci/Tech (4), Top Stories (5), Sports (7), or World (11). The language parameter controls the display language of returned titles and related queries.
Response Shape and Data Points
Each trend object includes related_queries, which is an array of associated search terms that provide context around why a topic is trending. The growth_percentage field indicates relative momentum — useful for distinguishing a high-volume evergreen topic from a fast-accelerating breakout term. The started_at field marks when the trend was first detected within the selected window.
Official API Status
Google does not publish an official public API for Google Trends data. The Parse API fills that gap with a structured, consistently-shaped response you can integrate directly.
- Monitor hourly breakout searches in a target country using
hours=4to catch viral topics before they peak - Filter Sci/Tech trending searches with
category=4to track emerging technology interest signals - Compare
growth_percentageacross trending topics to rank the fastest-accelerating searches in a market - Pull
related_queriesarrays to expand keyword lists for SEO and content planning - Use
search_volumedata to weight trending topics by actual query frequency for media monitoring dashboards - Segment trending searches by country and category to inform regional marketing campaign timing
- Track
started_attimestamps to reconstruct trend timelines and identify recurring seasonal spikes
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 250 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Google provide an official public API for Google Trends?+
What does the `get_trending` endpoint return beyond just trend titles?+
search_volume, search_volume_formatted, growth_percentage, started_at, related_queries (an array of associated search terms), and the geo the trend belongs to. The response wrapper also tells you total_available versus returned, so you know whether you've hit your limit ceiling.Does the API support historical trend data or interest-over-time charts?+
hours lookback window (from 4 hours up to 168 hours). Interest-over-time series, regional breakdowns by sub-region, and compare-term data are not exposed. You can fork this API on Parse and revise it to add those missing endpoints.How fresh is the trending data returned by the API?+
started_at field on each trend object indicates when Google first detected the trend. Using hours=4 returns topics that emerged within the last four hours, giving you a close approximation of real-time trend state. There is no sub-minute refresh guarantee; freshness depends on how frequently Google updates its trends index for the requested geo.Can I retrieve trend data for cities or states rather than whole countries?+
geo parameter accepts country-level ISO codes only; metro or sub-region granularity is not supported by this endpoint. You can fork the API on Parse and revise it to add sub-region filtering if your use case requires city-level trend data.