> **For coding agents and LLMs:** This is one Social Fetch marketing page (markdown export). For API orientation start with [`/llms.txt`](https://www.socialfetch.dev/llms.txt); for auth and crawl rules use [`/agents.txt`](https://www.socialfetch.dev/agents.txt); for every operation use [`/llms-endpoints.txt`](https://www.socialfetch.dev/llms-endpoints.txt). ## This page - **On-site (HTML):** - **Markdown (.mdx) URL:** --- # Google Trends Trending API Trending searches for a place and window, with volume, growth, times and category ids and names, ready to page. `GET /v1/google-trends/trending` reads the trending list for a place. `geo` takes a country (`US`, `DE`) or a subdivision (`US-CA`, `DE-BY`); `hours` takes 4, 24, 48 or 168 and defaults to 24. `category` filters to one of the trending list's own category ids (0 all, 1 Autos and Vehicles, 2 Beauty and Fashion, 3 Business and Finance, 4 Entertainment, 5 Food and Drink, 6 Games, 7 Health, 8 Hobbies and Leisure, 9 Jobs and Education, 10 Law and Government, 11 Other, 13 Pets and Animals, 14 Politics, 15 Science, 16 Shopping, 17 Sports, 18 Technology, 19 Travel and Transportation, 20 Climate); `active` keeps only live or only ended trends, and `sort` orders by `recency` or `volume`. On `found`, `data.trends[]` carries one row per trend: `query`, the echoed `geo`, `startedAt` and `endedAt` in ISO 8601 UTC, a numeric `searchVolume` bucket, `growthPercent`, `relatedSearches` and `categories` ids with matching `categoryNames`. `data.limit` is the page size you asked for and `data.page` holds `hasMore` and `nextCursor`. Send `cursor` back with the same filters to continue. A geo Google Trends does not serve is a 400 with an input message, not a billed not-found. ## Request - **Endpoint:** `GET /v1/google-trends/trending` - **Credits:** 1 credit Failed requests are free - **Input:** by geo, window and category - **Full reference:** [docs](https://www.socialfetch.dev/docs/api/v1/google-trends/trending/get) - **Platform page:** [/platforms/google-trends](https://www.socialfetch.dev/platforms/google-trends) ## FAQ ### Which windows can I ask for? hours accepts 4, 24, 48 and 168. The default is 24. Any other number is refused by the schema, so the request does not reach the lookup. ### How do I get the next page? Read data.page.nextCursor and send it as cursor with the same geo, hours, category, active and sort values. Repeat while data.page.hasMore is true. A cursor issued for different filters is refused instead of returning the wrong rows. ### Is searchVolume a count? No. It is a bucket: 100, 1000, 2000 or 500000 for example. Google Trends publishes the bucket, not the number of searches, so use it to rank rows rather than to sum traffic. ### Can I filter to one category? Yes. Pass category with one of the trending ids listed on this page, for example 17 for Sports. The answer echoes the filter in data.category, and null means no category filter was applied. The trending ids are not the explore category tree: 17 is Sports here, and a number that is not in this set is refused. ### How many credits does a trending lookup cost? Pricing is documented on the operation in the API registry (shown on this page). Confirm on every response with meta.creditsCharged: that field is the billing source of truth.