Surface the queries and hashtags climbing right now, then pull the posts driving them without changing keys or schemas. Poll it on your own cadence and keep the history in your own store.
Rising term, then the posts
A trend detection API surfaces the search terms, hashtags and feeds that are rising right now, and lets you pull the content driving them. SocialCrawl pairs rising query data and regional trending feeds with keyword, hashtag and reels search across 46 platforms, so one job moves from a breakout term to the posts behind it on a single key and one schema.
Every one of these is a shipped pattern, not a roadmap item. The endpoint chain under each card is the actual call sequence.
Pull the related and rising queries for a seed keyword, then run the winner straight into social search and open the posts that rank. This is the most repeated trend workflow on the API, and the value is being early rather than being complete.
trends/rising -> tiktok/search -> postRequest the trending feed for the market you actually sell in, rather than reading a global average and hoping it applies. Re-run it daily and diff against yesterday to see what entered.
tiktok/trending (by region)Search a hashtag, then search reels on the same term, so you can tell whether a topic is moving or whether one format is carrying it.
instagram/search/hashtag -> search/reelsInterest over time for a fixed keyword list, polled on your schedule and stored on your side. Watching the slope over several days is what separates a trend from a spike.
google_trends/explore (keyword panel)Trending shorts as a second read on the same movement. Two independent feeds agreeing is a stronger signal than either one alone.
youtube/shorts/trendingClick share trends for keywords inside a Naver shopping category, indexed from 0 to 100. It shows relative demand between terms rather than listings or prices, which is what you want when sizing a Korean category.
naver/shopping-insight (Korean demand)Four calls take you from a seed keyword to the content behind a breakout. Two are trend reads, two are content pulls.
Reads are priced in credits. Trend endpoints are advanced reads at a flat rate, content search bills per page, and failed upstream calls are refunded automatically.
GET /v1/google_trends/risingSend a seed keyword and a location and get the related and rising queries around it. This is the input to everything downstream.
5 credits per callGET /v1/tiktok/searchRun the rising term as a keyword search and page through the videos that are actually ranking for it right now.
1 credit per pageGET /v1/instagram/search/reelsSearch reels on the same term to confirm the topic is moving across formats rather than inside one feed.
1 credit per pageGET /v1/google_trends/exploreAdd the term to a keyword panel and poll interest over time so you can see the slope on your next run.
5 credits per callEach of these is a live lane on the same key. Follow a link to see that platform's full endpoint surface.
Most teams read a trends dashboard, then start a separate project to find the content behind the line going up. Here is what changes.
| Capability | SocialCrawl | Typical setup |
|---|---|---|
| From signal to evidence | Take a breakout term straight into keyword and hashtag search and read the posts behind it. | Export the term, then begin a separate scraping project to see what caused it. |
| Region | Trending feeds and interest data requested per market. | Global averages that hide the market you sell in. |
| Cadence | Poll as often as your job needs and keep the full history in your own store. | Fixed refresh windows and history that lives inside the vendor's dashboard. |
| Korean demand | Naver search trends and shopping click share sit alongside the global sources on the same key. | Korea handled by a separate local vendor, if at all. |
| Coverage | Trend reads and content pulls across 46 platforms and 375 endpoints. | One trends product, one social scraper, two contracts. |
| Pricing model | Credit packs that never expire, charged per call, so a research sprint is a one-off cost. | Annual licence with a seat count. |
A trend detection API returns the search terms, hashtags and feed entries that are climbing, as structured data rather than a chart. Because the same key also reads social search, you can go from a rising term to the posts that are driving it inside one job.
Earliness comes from cadence, not from a magic feed. Rising queries and regional trending feeds are the earliest public signals available, and how early you catch a term depends on how often you poll them and how tightly you diff each run against the last.
Yes. Rising and interest over time take a location, and the TikTok trending feed takes a region. Requesting per market matters because a term that is flat globally can be sharply up in one country, which is exactly the case you want to catch.
Feed the term into keyword search on the platforms you care about, then open the individual posts that rank. The trend read and the content pull use the same API key and return on the same schema, so the handoff is one variable rather than one integration.
Yes. Naver returns Korean search term trends and shopping click share by category and keyword, indexed from 0 to 100 as relative demand. Threads search with date windows is the practical lane for South East Asian product and commerce terms, and the news lane takes a language and region.
Trend jobs on the API are polled rather than pushed. You call the endpoints from cron, a worker or an automation tool on your own schedule, store what comes back and diff it yourself. That keeps the full history in your store, which is what you need to define what a spike means for your category.
Trend reads are advanced calls at 5 credits, and the content searches that follow are single credits per page. Credits come from never-expire packs rather than a subscription, so an occasional research sprint costs what it costs. Signup includes 100 free credits and no card is required.
Ask AI about SocialCrawl
100 free credits on signup. No card, no dashboard licence, no sales call.
curl -G "https://socialcrawl.dev/v1/google_trends/rising" \
-H "x-api-key: $SOCIALCRAWL_API_KEY" \
--data-urlencode "keyword=air fryer" \
--data-urlencode "location=US"curl -G "https://socialcrawl.dev/v1/tiktok/trending" \
-H "x-api-key: $SOCIALCRAWL_API_KEY" \
--data-urlencode "region=GB"Both calls run against live data. Swap the key and the keyword and they work as written.