RapidAPI Google Trends listings, and where they stop

RapidAPI is not a Trends engine. It is a billing and discovery layer. A search for "Google Trends" returns unofficial APIs from different publishers. Each subscribe creates a RapidAPI key and a host header for that listing. The JSON is whatever that publisher scraped this week. Trends API is the opposite object: one URL, one key, documented source and type strings. The POST is on the API reference.

A marketplace, not one API

X-RapidAPI-Key and X-RapidAPI-Host authenticate the store. They do not name a data source. Two listings can both claim "interest over time" and return different keys for the same date. There is no RapidAPI-wide mode of get_time_series.

Named vendors that also appear as standalone products, such as SerpApi, document their own engines. Buying the same vendor through RapidAPI does not change the Google-only stop. It only changes the invoice.

Listings drift

Store rankings change. A listing that worked in a tutorial can raise its per-request price or stop updating after a Google HTML change. The team then shops again. That loop is the product.

Trends API versioning and source names live in one docs set. google search is a source. Google Trends is a live type. Those spellings are on the sources reference. They do not depend on a store card.

Many store cards wrap the same unofficial Node client, google-trends-api 4.9.2, last published in 2020. A listing that still exposes dailyTrends is wrapping a method whose unofficial endpoint already 404s. The package page is the npm alternative.

{
  "mode": "get_time_series",
  "source": "google search",
  "keyword": "air fryer"
}

Parse the body string. No X-RapidAPI-Host.

Auth is the store plus the vendor

Some listings add a second key. Some hide the upstream scrape. None of that is Google's official alpha. None of it is a multi-source 0-100 index.

Keep RapidAPI when the company already centralizes experimental APIs there and the Trends listing is a spike. Leave when legal or finance needs a named vendor and a stable schema. The unofficial Node package that often sits under those listings is google-trends-api on npm.