Exploding Topics describes its API as programmatic access to a database of more than 1.1 million curated trends, plus products, startups, and meta trends. Humans filter fads. Machine learning adds a 12-month forecast. The same page states the API cannot do custom keyword and geo lookups. Trends API is the opposite shape: send a keyword and a source. POST https://api.trendsapi.ai/api. body is a JSON string and must be parsed a second time. Docs: the API reference. Caps: pricing.

A catalog of 1.1 million curated rows

Exploding Topics collects social, search, forums, news, commerce, and podcasts, then stores a row. The caller filters that table. The caller does not invent a term Google has never seen and expect a series. Docs live at api.explodingtopics.com/docs.

Any keyword versus a row that already exists

POST https://api.trendsapi.ai/api
Authorization: Bearer <api_key>
Content-Type: application/json

{"mode":"get_growth","source":"google search","keyword":"air fryer","percent_growth":["12M"]}

That string does not have to exist in a curated catalog. If the source has no series, the inner payload says so. Exploding Topics will simply omit a term that never entered the database.

Add-on pricing on Pro Business

API access is not a standalone key. The public page required Pro Business, then a request pack. Commercial embedding of their data is a custom conversation. Trends API keys are this product's keys. Do not paste an Exploding Topics key into the Bearer header.

Forecasts and products are not a source string

Trending products, trending startups, growth speed, and a 12-month forecast are Exploding Topics objects. They are not source tiktok or source amazon. If the warehouse needs a verdict on "is this exploding," keep ET. If the warehouse needs a 0-100 next to Google on a name the catalog never stored, use this POST.