#trends
12 APIs with this tag
Google Trends API
Live trending Google searches by country, with no key. This reads Google's own public Daily Search Trends RSS feed and returns it as clean JSON: what people are searching for right now in any country, each trend with its approximate search volume, the news stories driving it and a representative image. The trending endpoint lists the current trending searches for a country (term-centric, ranked, with volume and the top news story); the news endpoint flattens the news articles powering those trends (article-centric — the "what is driving search right now" view, each article tagged with its trend, source and link); and the geos endpoint lists the supported countries. The real-time search-interest / trends-discovery layer for news, marketing, SEO, social-listening and content tools. Distinct from wiki-pageview and platform-specific trend APIs — this is Google web-search trends. Live from Google Trends; short cache only.
api.oanor.com/googletrends-api
Steem API
Read the Steem blockchain and its social layer (Steemit) live — no key needed. The account endpoint returns a Steemit account's social profile and on-chain stats: display name, about, location, website, reputation score, post count, STEEM and SBD balances and the account-creation date. The trending endpoint returns the posts trending on Steemit right now (author, title, votes, pending payout, optional tag). The network endpoint returns chain-wide stats — head block and current/virtual STEEM supply. Data comes live from Steem's own public RPC node — nothing cached, nothing stored. Steem is a distinct blockchain-social network, separate from Hive since the 2020 fork. Built for social dashboards, creator analytics, on-chain explorers and trend monitoring.
api.oanor.com/steem-api
Minds API
Read any public Minds channel and the platform's live hashtag trends — no key needed. Minds is an open-source, decentralised social network; this API returns a public channel's display name, bio, subscriber and subscription counts, lifetime impressions, Plus/Pro and verified flags and join date, plus the hashtags trending on Minds right now with their volume. Pass a username (the handle without the @). Data comes live from Minds' own public API — nothing cached, nothing stored. Distinct from the Mastodon/fediverse APIs — Minds runs its own platform. Built for social dashboards, creator analytics and trend monitoring.
api.oanor.com/minds-api
GETTR API
Read any public GETTR profile and the platform's live trends — no key needed. GETTR is a global microblogging social network; this API returns a public account's display name, bio, website, language, follower and following counts, imported-Twitter follower count, influencer level and join date, plus what is trending on GETTR right now. Pass a username (the handle without the @). Data comes live from GETTR's own public web API — nothing cached, nothing stored. Built for social dashboards, audience analytics, creator tooling and trend monitoring on the platform.
api.oanor.com/gettr-api
Wikipedia Trends API
Live readership-trend data from the Wikimedia Pageviews API — the official measure of what the world is reading on Wikipedia and its sister projects. See the most-viewed articles on any Wikipedia language edition for a given day (the daily trending list); pull the daily or monthly pageview trend for any single article over a date range; read a whole project's total pageviews over a range as a barometer of overall traffic; or rank several articles head-to-head by total views for topic-engagement comparison. Special / namespace pages (Main Page, Search, Portal…) are filtered out by default so the trending list is real articles. Read live from Wikimedia, nothing stored — data lags about 1-2 days, so ranges default to ending two days back. This is the Wikipedia readership-trend and topic-engagement layer for any trends, research, newsroom or analytics app — distinct from Wikipedia content APIs: this is the pageview, trending and engagement signal of what people are actually reading and how it changes.
api.oanor.com/wikitrends-api
Coub API
Live looping-video data from Coub, the social platform built around short, seamlessly looping video clips, served straight from Coub's public API — no key, nothing cached. The explore endpoint returns the trending feed (rising, hot or random coubs across the whole site), each with its title, view, like and recoub counts, duration, channel and tags, plus ready-to-use loop-preview image URLs at several sizes. The tag endpoint returns the newest coubs for a tag — cats, gaming, music — the hashtag feed of Coub. The channel endpoint returns a creator's profile (title, follower and recoub counts) together with their most recent coubs. Every clip comes back cleaned up: the watch URL, the channel handle, the human tags and several preview-image sizes. Everything is live from Coub, nothing stored. This is the looping-video discovery layer for any feed, meme, moodboard, embed or social app. Distinct from YouTube, Vimeo, Dailymotion and other video APIs — this is Coub's looping clips by trend, tag and channel. 3 endpoints, no key on our side.
api.oanor.com/coub-api
4chan API
Live read-only access to the 4chan imageboard, served straight from its official JSON API — one of the most influential anonymous forums on the internet and a primary source of internet culture, exposed as clean JSON with the HTML stripped to plain text. The boards endpoint lists every one of 4chan's ~77 boards with its code, title, worksafe flag, pages, threads-per-page and a description, from /g/ (Technology) and /v/ (Video Games) to /news/, /sci/ and /pol/. The catalog endpoint returns every live thread on a board summarized — the opening post's subject and a plain-text teaser of its comment, the reply and image counts, the sticky and closed flags and when it was last bumped — sorted by activity, replies or images: the front page of the board as data. The hot endpoint self-discovers and returns the single most active thread on a board right now, fully expanded with the original post and its top replies, so you never need a thread id that has expired. The thread endpoint returns one specific thread in full by its id — the original post and every reply with author name, timestamp, plain-text comment and image filename — and falls back to the current top thread when no id is given. Everything is the live board state, nothing stored. This is the imageboard layer for any social-listening, trend-tracking, meme-research, moderation or bot app. Live from 4chan's JSON API. Distinct from Reddit, Hacker News and Lemmy APIs — this is 4chan's boards, catalogs and threads. Some boards are NSFW (worksafe flag provided). 5 endpoints, no key on our side, nothing cached.
api.oanor.com/fourchan-api
Reading Trends API
A live read on what the Open Library reading community is into right now, as an API. Pull the trending books over the last day, week, month or year — with author, first-published year and edition count — or open a book for its social reading stats: the average star rating and number of ratings, and how many people have it on their "want to read", "currently reading" and "already read" shelves. The pulse of community reading delivered as clean JSON for book, social and dashboard apps. Live data, no key. Distinct from book-catalogue search/ISBN APIs — this is the reading-popularity and shelf-engagement layer.
api.oanor.com/readingtrends-api
Misskey API
A live window into Misskey.io — the largest instance of Misskey, a decentralised Fediverse microblogging platform distinct from Mastodon — as an API. Pull the currently trending hashtags with how many people are posting them; the featured, most-reacted notes with their author, reaction and renote counts; a user's profile (followers, notes, bio); that user's recent notes; or instance-wide stats. The Fediverse microblog's pulse delivered as clean JSON for social, trends and community-dashboard apps. Live data, no key.
api.oanor.com/misskey-api
npm Download Stats API
How popular is that npm package? Get download counts and trends for any npm package straight from npm's public download API. Pull the total downloads over a period (last day, week, month, year or any custom YYYY-MM-DD:YYYY-MM-DD range), the full per-day download time series, the monthly totals over the last year to spot growth or decline, and compare several packages side by side ranked by downloads (up to 128 at once, scoped @org/name packages supported). Every call is live (no cache). 5 endpoints. Built for popularity dashboards, package-comparison pages, trend charts, dependency-health scoring and "which library won" analyses. Distinct from an npm registry-metadata lookup — this is the download time series. No upstream key, no cache.
api.oanor.com/npmstats-api
Wikipedia Pageviews API
Wikipedia pageview statistics as an API, live from the official Wikimedia REST API. See the most-viewed Wikipedia articles for any day — a real-time pulse of what the world is reading and searching for — with junk namespaces filtered out by default, and get the daily (or monthly) view counts and totals for any individual article over any date range. Works for any language edition (en.wikipedia, de.wikipedia, fr.wikipedia and 300+ projects) and any access method (desktop, mobile-web, mobile-app). Ideal for trend analysis, news, research, dashboards, SEO and content strategy. Public Wikimedia data.
api.oanor.com/pageviews-api
Baby Names API
US given-name popularity from 1880 to 2008 as an API — the top 1,000 names per year for each sex (SSA-derived dataset, 6,782 names). Pull a name's full popularity trend (e.g. Emma → girls: rank #1 in 2008, peaked again in 1881), get the top names for any year (e.g. 1990 → Jessica, Ashley, Brittany), or search names by prefix/substring. Each data point carries the year, the share of births (percent and per-million) and the rank. Ideal for name-trend visualisations, baby-name apps, nostalgia/genealogy tools and data journalism.
api.oanor.com/babynames-api