Exploding Topics APIexplodingtopics.com ↗
Access trending topics, startups, websites, and blog posts from Exploding Topics via 8 endpoints. Filter by category, volatility, period, and more.
What is the Exploding Topics API?
The Exploding Topics API exposes 8 endpoints covering trending topics, emerging startups, top websites, and blog content from explodingtopics.com. The get_trending_topics endpoint returns paginated trend objects with keyword, growth percentages across configurable time periods, search history going back to 2004, category tags, and volatility signals — giving developers structured access to early-stage trend data without manual browsing.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/67aaa11a-d73d-4946-bffa-82a5760b2c39/get_categories' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace explodingtopics-com-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
"""
Exploding Topics SDK — discover trending topics, startups, and websites.
Demonstrates: trends.search, topic().related, startups.search, websites.list, articles.list
"""
from parse_apis.exploding_topics_api import (
ExplodingTopics, TopicSort, TopicPeriod, Period, Volatile, StartupSort, TopicNotFound
)
et = ExplodingTopics()
# Search trending topics sorted by growth over 2 years, stable only
for trend in et.trends.search(sort=TopicSort.GROWTH, period=TopicPeriod.TWO_YEARS, volatile=Volatile.STABLE, limit=3):
print(trend.keyword, trend.path, trend.categories)
# Drill into one trend's full detail, then explore related topics
trend = et.trends.search(sort=TopicSort.GROWTH, limit=1).first()
if trend:
detail = trend.details()
print(detail.keyword, detail.brief_description[:80], detail.growth)
for related in detail.related(period=Period.TWO_YEARS, limit=3):
print(related.keyword, related.brief_description[:60])
# Browse trending startups with funding data
startup = et.startups.search(sort=StartupSort.GRADIENT, period=Period.TWO_YEARS, limit=1).first()
if startup:
print(startup.keyword, startup.path, startup.brief_description[:80])
if startup.startup_data:
print(startup.startup_data.location, startup.startup_data.total_funding)
# Typed error handling: catch a missing topic
try:
missing = et.topic("nonexistent-slug-xyz-99999").related(limit=1).first()
except TopicNotFound as exc:
print(f"Topic not found: {exc.slug}")
# List top websites
site = et.websites.list(limit=1).first()
if site:
print(site.path, site.ranks, site.results)
# List blog articles
article = et.articles.list(tag="featured", limit=1).first()
if article:
print(article.title, article.slug, article.published, article.author.first_name)
print("exercised: trends.search / details / related / startups.search / websites.list / articles.list")
Returns all topic category names mapped to their topic counts. The response is a flat object whose keys are category slugs and whose values are integers (topic counts), plus a lastUpdated Unix timestamp. Use these category names as filter values in get_trending_topics.
No input parameters required.
{
"type": "object",
"fields": {
"automation": "integer, topic count for the automation category",
"technology": "integer, topic count for the technology category",
"lastUpdated": "integer, Unix timestamp of when counts were last refreshed"
},
"sample": {
"data": {
"beauty": 109872,
"health": 304420,
"automation": 37819,
"technology": 211669,
"lastUpdated": 1780790401
},
"status": "success"
}
}About the Exploding Topics API
Trending Topics and Categories
The get_trending_topics endpoint accepts filters including categories (comma-separated slugs from get_categories), period (24 or 60 months), volatile, and exclude_peaked. Each result in the trends array includes a keyword, path slug, growth percentages, briefDescription, categories, and a searchHistory array. The get_categories endpoint provides a flat object mapping every available category slug to its topic count, along with a lastUpdated Unix timestamp — use it to validate category names before filtering.
Topic Detail and Related Topics
Pass any path slug from get_trending_topics into get_topic_detail to retrieve the full trend object. This includes weekly searchHistory volumes since 2004, regressions models, socialChannelResults, TikTok activity data, Amazon productData, growth predictions, and relatedTopics. The get_related_topics endpoint accepts the same slug plus an optional period parameter (3, 6, 12, 24, or 60 months) and returns an array of thematically adjacent trend objects with their own growth, searchHistory, and briefDescription fields.
Startups and Websites
get_trending_startups returns paginated startup records with a startupData sub-object containing location, website, employees, funding details, and founding date. The period filter accepts values from 3 to 60 months. get_top_websites returns a ranked array of website objects with engagement metrics including visit counts, pages per visit, bounce rate, and average session duration, along with a display_date indicating when the dataset was compiled.
Blog Posts and Homepage Highlights
get_blog_posts supports an optional tag filter and returns post objects with title, slug, HTML body, summary, author, tags, categories, and published date, plus meta pagination fields (count, next_page, previous_page). get_home_highlights combines the top 3 trending topics, top 3 trending startups, and the full top websites list into a single response — useful for dashboard overviews that need a quick snapshot without issuing multiple paginated requests.
The Exploding Topics API is a managed, monitored endpoint for explodingtopics.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when explodingtopics.com changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official explodingtopics.com API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Monitor search volume growth for emerging keywords using
searchHistoryweekly data going back to 2004 - Identify early-stage startups by filtering
get_trending_startupsresults on funding stage and employee count - Build a category-scoped trend tracker using
get_categoriesslugs as live filter inputs toget_trending_topics - Discover adjacent opportunities by pulling
get_related_topicsfor a given trend slug and comparing growth rates - Track engagement shifts across top websites using bounce rate, pages per visit, and session duration from
get_top_websites - Enrich a content calendar by pulling
get_blog_postsfiltered by tag and matching topics to trend keywords - Create a homepage intelligence widget using
get_home_highlightsto surface the current top 3 topics and startups in one request
| 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 | 100 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 Exploding Topics have an official developer API?+
What does `get_topic_detail` return beyond what `get_trending_topics` includes?+
get_topic_detail adds several fields not present in the list endpoint: weekly searchHistory going back to 2004, regressions models, socialChannelResults, TikTok activity data, Amazon productData, and growth predictions. The list endpoint returns a briefDescription and aggregate growth metrics, but the detail endpoint is the only place to get per-channel social data and Amazon product signals.Can I filter trending topics by geographic region?+
categories, period, volatile, and exclude_peaked, but does not expose a region or country parameter. Search history data is not broken out by geography. You can fork this API on Parse and revise it to add a geographic filter endpoint if the underlying data supports it.What is the `volatile` parameter in `get_trending_topics` and what values does it accept?+
volatile parameter filters results by volatility level — separating steadily growing trends from spiky or unpredictable ones. The endpoint accepts it as a string, but the specific accepted values (such as 'true'/'false' or named tiers) are not enumerated in the spec. Test with the get_home_highlights endpoint first to see example volatility values on returned trend objects before applying the filter.