Developers search for a Google Trends API key because every other Google API works that way. Trends is the exception. The official Trends API is an application-gated alpha, so no self-serve key exists to find. The working routes are two: apply to Google and wait, or take a Bearer key from a managed API and call today. This page lays out both, so the hunt ends with a decision instead of another console tab. The endpoint itself sits on Google Trends API.
The official route: an application, not a credential
Google documents the alpha on Search Central. Access goes to approved projects, the window is a rolling five years, and the series is not the 0-100 index from the website. There is no quota page to buy past and no key to rotate. For a Google-only research project with time to wait, that shape can be right.
The managed route: one Bearer key
Signup on Trends API issues a key. REST sends it in one header:
POST https://api.trendsapi.ai/api
Authorization: Bearer <api_key>
{"mode":"get_growth","source":"google search","keyword":"heat pumps","percent_growth":["12M"]}
The same key authorizes the MCP server at https://api.trendsapi.ai/mcp, so an editor or chat host and a cron job share one credential. Rotation is one change in each caller. Header mistakes and the 401 they cause are covered on authentication.
What not to use as a key
Session cookies, scraped request tokens, and shared keys pasted into public repos all fail the same way: silently, at the worst time, with no support path. The pytrends route is free and familiar, and the repository is archived; its failure modes sit on pytrends 429 errors. The free options are weighed on Free Google Trends API. Plan caps sit on pricing, and only successful 200 responses count against them.