TrendHunter APItrendhunter.com ↗
Access TrendHunter trend articles via API. List trends by category with pagination or fetch full article details including body text, author, score, and metadata.
What is the TrendHunter API?
The TrendHunter API provides two endpoints for accessing trend content from TrendHunter.com. The list_trends endpoint returns up to 30 trend summaries per page — including title, subtitle, trend label, description, publication date, and image URL — organized by category slug. The get_trend endpoint retrieves the complete article body, author, popularity score (0–100), breadcrumb path, and category for any individual trend by its URL slug.
curl -X GET 'https://api.parse.bot/scraper/02c53b04-2fe6-4839-816e-ac8f789abd7d/list_trends?page=1&category=eco' \ -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 trendhunter-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.
"""Walkthrough: TrendHunter SDK — browse eco trends and drill into article details."""
from parse_apis.trendhunter_com_api import TrendHunter, TrendNotFound, Category
client = TrendHunter()
# List eco trend summaries — limit caps total items fetched across pages.
for summary in client.trend_summaries.list(category=Category.ECO, limit=5):
print(summary.title, "|", summary.date, "|", summary.trend_label)
# Drill into the first result for full article details.
first = client.trend_summaries.list(category=Category.ECO, limit=1).first()
if first:
trend = first.details()
print(trend.title, "|", trend.author, "|", trend.date_published)
print(trend.body[:200])
# Direct lookup by slug via the trends collection.
try:
detail = client.trends.get(slug="blue-ocean-closures-paperplug")
print(detail.title, detail.score, detail.category)
except TrendNotFound as exc:
print(f"Trend not found: {exc.slug}")
print("exercised: trend_summaries.list / summary.details / trends.get")
List trend articles from a category page with pagination. Returns 30 trends per page including title, subtitle, trend label, short description, publication date, and image. Categories correspond to top-level navigation sections on TrendHunter. Results are auto-iterated across pages.
| Param | Type | Description |
|---|---|---|
| page | integer | Page number for pagination. Each page returns up to 30 trends. |
| category | string | Category slug for the trend listing page. |
{
"type": "object",
"fields": {
"page": "integer",
"count": "integer",
"trends": "array of trend summary objects with slug, title, subtitle, date, trend_label, description, image_url, url",
"category": "string"
},
"sample": {
"data": {
"page": 1,
"count": 30,
"trends": [
{
"url": "https://www.trendhunter.com/trends/hydrogen-train",
"date": "JUL 1, 2026",
"slug": "hydrogen-train",
"title": "Sleek Emissions-Free Trains",
"subtitle": "This Hydrogen Train Was Developed for Narrow-Gauge Italian Tracks",
"image_url": "https://cdn.trendhunterstatic.com/phpthumbnails/620/620207/620207_1_468.jpeg",
"description": "Hydrogen propulsion tailored for compact rail corridors creates new possibilities for decarbonizing legacy transit systems.",
"trend_label": "Narrow-Gauge Hydrogen Rail"
}
],
"category": "eco"
},
"status": "success"
}
}About the TrendHunter API
Listing Trends by Category
The list_trends endpoint accepts a category parameter (a slug matching TrendHunter's top-level navigation sections, such as eco, fashion, or tech) and an optional page integer for pagination. Each response includes a trends array of up to 30 objects, each carrying slug, title, subtitle, date, trend_label, description, image_url, and url. The response also echoes back the current page number, item count, and the active category string, making it straightforward to iterate across pages programmatically.
Fetching Full Article Detail
The get_trend endpoint takes a slug — typically obtained from a list_trends result — and returns the complete article. Key fields include body (full article text), author, score (an integer from 0 to 100 representing article popularity), breadcrumb (an ordered array of strings showing the category path), image_url, and a short description. The category field aligns with the category returned in list results, allowing you to cross-reference listings with detail data.
Data Shape and Coverage
TrendHunter organizes content into named categories that correspond to site navigation sections. The trend_label field in list results gives a short thematic tag distinct from the broader category — useful for clustering or filtering results downstream. Publication dates are available in list results via the date field. The score field in detail responses is a site-assigned popularity percentage, not a derived metric.
The TrendHunter API is a managed, monitored endpoint for trendhunter.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when trendhunter.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 trendhunter.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?+
- Track emerging trends in a specific category by polling
list_trendswith a category slug and storing newsluganddatevalues over time. - Build a trend digest newsletter using
title,description,image_url, andurlfrom paginatedlist_trendsresponses. - Analyze trend velocity by comparing
scorevalues across articles retrieved withget_trendfor a given category. - Extract and index full article
bodytext fromget_trendfor keyword or topic modeling across multiple trend categories. - Map content hierarchies using the
breadcrumbarray fromget_trendto understand how articles nest within TrendHunter's taxonomy. - Aggregate
authorattribution fromget_trendto identify which contributors cover specific trend topics most frequently. - Build a category browser that surfaces
trend_labeltags fromlist_trendsto let users filter and explore related articles.
| 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 TrendHunter have an official developer API?+
What does the `list_trends` endpoint return for each trend, and can I filter by date?+
trends array includes slug, title, subtitle, date, trend_label, description, image_url, and url. The endpoint does not currently support filtering by date range — it returns results as ordered by TrendHunter's category pages. You can iterate pages using the page parameter to retrieve older content.What does the `score` field in `get_trend` represent?+
score field is an integer from 0 to 100 representing the article's popularity percentage as assigned by TrendHunter. It reflects the article's standing relative to other content on the site, not an external engagement metric.Does the API support searching for trends by keyword rather than browsing by category?+
list_trends and individual article retrieval via get_trend. Keyword search across TrendHunter's content is not exposed. You can fork this API on Parse and revise it to add a search endpoint.Are trend comments, user reactions, or related article links available from these endpoints?+
get_trend endpoint returns article-level fields — body text, author, score, breadcrumb, category, image, and description — but does not include comment threads, user reactions, or related article references. You can fork this API on Parse and revise it to add those fields.