Plain-language definitions of the identifiers, data concepts and API terms you'll meet when working with TikTok, Douyin, Xiaohongshu and 16 platforms through TikHub.
The unique numeric ID of a Douyin or TikTok video (aweme is the pinyin abbreviation of the original app name 'A-me'). It appears in share URLs and every video-related API response, and is the primary key for fetching a single video's details, statistics or comments.
Douyin/TikTok's encrypted, URL-safe user identifier (secure user ID). Unlike the plain numeric uid, it is stable across sessions and is what profile URLs and most user endpoints expect as input.
item_id
TikTok's alternative name for a video's unique ID — interchangeable with aweme_id in most contexts. Share links, embeds and the web player all reference it.
note_id
The unique ID of a Xiaohongshu (Rednote) post, called a 'note'. Found in share URLs after /item/ or /discovery/item/, it is required to fetch note details or comments.
A short-lived signature token Xiaohongshu attaches to shared note links. Some note endpoints require a valid xsec_token alongside the note_id; TikHub's share-link endpoints extract it automatically.
BV / AV ID
Bilibili's two video ID formats: the legacy numeric AV ID and the newer Base58-encoded BV ID used in today's URLs. They map 1:1 — TikHub provides a conversion endpoint (bv_to_av) so either can be used.
The unique ID of a live-streaming room on Douyin, TikTok, Kuaishou or Bilibili. It is the entry ticket for live-room endpoints and the WebSocket danmaku stream.
The unique ID of an audio track on Douyin/TikTok. Music endpoints use it to return track metadata and the list of videos created with that sound — a common lever for trend analysis.
challenge_id
The ID of a hashtag challenge on Douyin/TikTok. Hashtag endpoints accept it to return the topic's metadata, view counts and associated videos.
Data concepts
Danmaku
Real-time comments that scroll across a video or live stream, originating from Japanese and Chinese video culture (danmu, 'bullet comments'). On Bilibili they overlay videos; in live rooms they are the chat stream. TikHub exposes both recorded video danmaku and live danmaku via WebSocket.
Resolving a platform's share URL (often a shortened link like v.douyin.com/xxxx) into the underlying content ID and structured data. TikHub's fetch_*_by_share_url endpoints handle redirect chains and ID extraction in one call.
Engagement metrics
The measurable interactions on a post: likes (digg_count), comments, shares, collects/favorites and plays. Play counts are the scarcest — Douyin removed them from most endpoints, leaving dedicated statistics endpoints as the reliable source.
Audience portrait
Aggregated demographic and interest data about a creator's followers — age bands, gender split, regions, device types and interest tags. Used for influencer vetting and ad targeting.
Hot list / billboard
Platform-curated rankings of trending content, topics or keywords, refreshed continuously (Douyin hot list, Weibo hot search, Bilibili popular). A primary raw material for trend monitoring and content strategy.
API concepts
Unofficial API
A third-party interface to a platform's publicly visible data, offered without requiring the platform's developer program, app review or OAuth. TikHub provides read-only unofficial APIs over public data — no posting, no account actions on your behalf.
A single callable URL path in an API, e.g. /api/v1/tiktok/app/v3/fetch_one_video. TikHub exposes 1,000+ endpoints across 16 platforms; each has its own price, rate limit and free-credit eligibility.
Cursor pagination
Fetching long lists (comments, followers, feeds) page by page using an opaque cursor returned by the previous call (often named cursor, max_cursor or offset), instead of numeric page numbers. Pass the cursor back until has_more is false.
Rate limit (RPS)
The maximum requests per second an endpoint accepts — 10/second by default on TikHub, upgradeable via RPS plans. Exceeding it returns HTTP 429; back off and retry.
The credential that authenticates your requests, sent as an Authorization: Bearer <token> header. Keys are created in the TikHub dashboard, shown once at creation, and carry configurable permission scopes.
Scopes
Per-key switches that control which endpoint families an API key may call. Calling an endpoint outside your key's scopes returns 403 — update the key's scopes in the dashboard before using newly launched APIs.
request_id
A unique identifier attached to every TikHub API response (and the X-Request-ID header). Quote it when contacting support so the team can trace your exact request in seconds.
cache_url
A link included in every successful TikHub response that re-opens that one exact response for 24 hours, free to access. It's a debugging and sharing aid — recover a response you already paid for when your code mishandled it (e.g. a wrong JSON path), or share a reproduction with a teammate. It does NOT make the API cached: every request returns fresh, real-time data and is billed independently, so repeating a call with identical parameters is a new live request, not a cache hit.
MCP (Model Context Protocol)
An open protocol that lets AI agents (Claude, Cursor, VS Code and others) call external tools directly. TikHub ships 990+ social-data MCP tools, so an agent can fetch live TikTok or Douyin data with one config block.
A persistent ws/wss connection that pushes live-room events — danmaku, gifts, likes, member entries — in real time, instead of polling. TikHub's free HTTP helper endpoints assemble the signed WebSocket URL for you.
TikHub's billing model: you top up a balance and pay per successful request only — no subscription, and balances never expire. Requests that fail (non-200) are never charged.
Your account's total successful requests within a calendar day — the variable that drives tiered discounts. The daily counter resets on the backend's billing timezone (America/Los_Angeles).
Tiered volume discount
Automatic per-day discounts computed cumulatively across volume bands: 0% up to 1,000 requests/day, then −10% to −50% beyond 30,000. Each band's requests are billed at that band's rate — not the whole day at one rate. Note that not every endpoint participates.