#engagement

Articles, engagement and trending tech tags from Qiita (qiita.com), Japan's largest developer knowledge-sharing community, read keyless from its public v2 API. Qiita is where Japanese engineers post how-tos, deep-dives and notes, and where the community signals quality with LGTM ("looks good to me") likes and "stocks" (saves) — the Japanese counterpart to dev.to or Medium's engineering side, with its own metrics and its own tech-topic rankings. The articles endpoint searches and lists articles, each with its title, LGTM likes, stocks (saves), comment count, tags and author — filterable by keyword, tag and a minimum-stocks threshold so you can surface the popular pieces. The article endpoint returns one article in full by its id. The tags endpoint ranks Qiita's tech tags by how many articles and followers they have — the live map of what Japanese engineers care about (Python, AWS, React and the rest). This is the Qiita platform cut — a distinct social and developer platform, separate from dev.to, Medium and the other blogging and social feeds in the catalogue, with its own LGTM/stock engagement model. Likes are LGTM up-votes and stocks are saves/bookmarks — two distinct Qiita signals; follower and article counts are the real, live community numbers. Titles and tags are in Japanese (and English) as Qiita publishes them. Qiita rate-limits unauthenticated callers, so a longer protective cache fronts the upstream and stale data is served if the limit is hit. Keyless.

api.oanor.com/qiita-api

Live data from SHOWROOM (showroom-live.com), the Japanese live-streaming platform built around idols and talent, read keyless from its public web API. SHOWROOM is where AKB48, Nogizaka46 and thousands of aspiring idols, voice actors and creators broadcast and where fans send virtual gifts in real time — a streaming culture quite unlike Twitch or Kick. This exposes who is live right now, how many are watching, which genres are hot and each room's standing. The live endpoint lists the rooms broadcasting right now across every genre, ranked by viewers, each with its streamer name, current viewer count, genre and how long it has been live (the "Popularity" overlay is de-duplicated so every room is counted once under its real category). The genres endpoint aggregates the live picture by category — idols, talents, virtual streamers, music and more — with each genre's number of live rooms and total viewers, so you can see where the audience is. The room endpoint returns one room's profile by its room id: the room name, its follower count, its room level (SHOWROOM's standing metric) and whether it is live now. This is the SHOWROOM platform cut — a distinct social/streaming platform, separate from the Twitch, Kick, Bilibili, Niconico and other feeds in the catalogue. Viewer and follower counts are live; nothing is stored beyond a short cache. Counts are integers; times are UTC.

api.oanor.com/showroom-api

Live video, search and engagement data from Niconico (nicovideo.jp), the pioneering Japanese video platform that invented danmaku — the comments that scroll across the video itself — read keyless from Niconico's public Snapshot Search API and video-info endpoint. Niconico is one of Japan's biggest video communities, the home of Vocaloid, "Let's Play" culture and a vast catalogue with videos counting tens of millions of views and millions of overlaid comments. This exposes what is popular, who is watching and how each video is performing across Niconico's distinctive engagement signals — views, the famous scrolling comments, mylist bookmarks and likes. The search endpoint finds videos by keyword, sorted by views, comments, mylists, likes or upload date — the way to surface the platform's most-watched and most-discussed content. The tag endpoint browses an exact Niconico tag (the platform's main discovery axis — VOCALOID, ゲーム/games, 音楽/music, アニメ/anime) ranked by views, so you can see what leads a category. The video endpoint returns one video's full detail by its watch id (the sm/nm/so id), including its description, tags, length, upload date and uploader. This is the Niconico platform cut — a distinct social/video platform, separate from the YouTube, Bilibili, TikTok, BitChute and other platform feeds in the catalogue. View, comment, mylist and like counts are live; nothing is stored beyond a short cache. Counts are integers; dates are as the platform reports them (JST).

api.oanor.com/niconico-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

Live data from Wattpad, the world's largest storytelling social platform where writers publish serialized fiction and millions of readers follow, vote and comment, served straight from Wattpad's public API — no key, nothing cached. The search endpoint finds stories by keyword, each with its read, vote and comment counts, part count, completion and maturity flags, tags and author — a popular dragon-romance pulls hundreds of thousands of reads. The story endpoint returns one story in full: its description, cover, the engagement counts, the number of parts, language, tags and the author with their follower count. The user endpoint returns a writer's profile: their follower and following counts, the number of stories they have published, their bio and location — Wattpad's own account has tens of millions of followers. The user-stories endpoint returns a writer's published stories with each one's stats. Everything is live from Wattpad, nothing stored. This is the web-fiction social layer for any reading, discovery, writing-community or recommendation app. Distinct from mainstream social and the book-catalog APIs — this is Wattpad's stories, their engagement and their authors. 4 endpoints, no key on our side.

api.oanor.com/wattpad-api

Live data for any Substack publication, served straight from the publication's own public API — no key, nothing cached. Substack is the newsletter-and-blogging social platform; this reads a writer's public posts and their engagement. The posts endpoint returns a publication's recent or top posts with the title, subtitle, slug, publish date, post type (newsletter, podcast or thread), audience (free or paywalled), the heart-reaction count, the comment count, the word count and the cover image — Noah Smith's Noahpinion shows posts pulling hundreds of reactions and dozens of comments. The search endpoint searches a publication's archive by keyword. The post endpoint returns one post in full, including a plain-text excerpt of the body, its reactions and comment count. Point it at any publication by its Substack subdomain (noahpinion) or its custom domain (astralcodexten.com) and it follows the publication wherever it lives. This is the writer-and-post engagement layer for any media-monitoring, newsletter-analytics, reading or social app. Live from Substack, nothing stored. Distinct from dev-community and microblog APIs — this is Substack newsletter posts and their engagement. 4 endpoints.

api.oanor.com/substack-api

Live wallpaper-community data from Wallhaven as an API — search the large community wallpaper collection by keyword and category (general, anime, people), sorted by favourites, views or freshness, and read any wallpaper's community engagement (favourites and views) along with its resolution, aspect ratio, file type, dominant colours and tags. The visual-community engagement layer for wallpaper, design and dashboard apps. SFW-only by design — every request is forced to safe content. Live, no key, no cache. Distinct from generic image and stock-photo APIs — this is Wallhaven's own community wallpapers, their favourites/views engagement and tags.

api.oanor.com/wallhaven-api

Live profile, project and engagement data from Scratch, MIT's massive creative-coding platform where millions of young creators share interactive projects — served from the public Scratch API. Look up any user for their profile (join date, country, bio and "what I'm working on"), open any project for its engagement stats (views, loves, favourites and remixes) with author and dates, list a user's shared projects with their stats and totals, or search the shared projects. The creative-community-and-engagement layer for social, edtech and dashboard apps. Live, no key, no cache. Distinct from generic coding or game-catalogue APIs — this is the live Scratch community.

api.oanor.com/scratch-api

Live Roblox profile and game stats as an API — community and engagement data from Roblox, the massive user-generated gaming platform. Look up any user by username or id for their profile (display name, description, account age, verified and banned flags) and social reach — friends, followers and followings counts. Look up any experience (game) by its universe id or place id for its live stats: players online right now, all-time visits, favourites, up and down votes and like ratio, max players, genre and creator. The Roblox profile-and-game-stats layer for gaming, social and dashboard apps. Live, no key. Distinct from store-catalogue gaming APIs — this is live Roblox community and engagement data.

api.oanor.com/roblox-api