Douyin Billboard rise list API

POST

API health

24h health: Normal
24h average time: —

Healthy / normal
Available
Limited
Mostly down

Normal

Last 24 hours

Last 30 days

Spot the trends climbing fastest on Douyin, from the rising board in Hot Spot Treasure. Each trend has its rank and places gained, title, ID, heat, related video count, category, creation time and an hourly heat curve. Keep only trends containing a keyword if you like. 50 per page; page on with next_page_token.

Price $0.81 per 1,000 requests ($0.000806 per call). Failed calls and empty results are not charged. Synchronous. For slow jobs add "mode": "async" to the body, take the job_id and poll.

AI prompt

Please help me write a data collection script with the EveryInfra Douyin Billboard rise list endpoint (douyin/billboard_rise_list).

How the endpoint works:
- Request: POST https://api.everyinfra.com/api/v1/social with the header Authorization: Bearer <API key>. Read the key from the EVERYINFRA_API_KEY environment variable and never hard-code it.
- In the request body, set platform to douyin and action to billboard_rise_list, and put the parameters inside params.
- No required parameters.
- Optional parameters:
  - keyword: Optional: keep only trends that contain this word, such as game; leave it out for the whole rising board.
  - page_token: Page token. Leave it out for the first page (the top 50 trends), then pass back the previous response's next_page_token exactly as received, with the other parameters unchanged.
- Returns a list of records. Main fields of each record: rank (Position from 1: the trending rank on t…), rank_change (Places gained since the board's previou…), title, topic_id (Hot Spot Treasure ID of the trend (bill…), hot_value (Heat value, Douyin's own measure, compa…), video_count (Video count: the account's videos on pr…), category, created_at, hot_trend (Recent heat of the trend: hourly on bil…), next_page_token (Page token (search / user_posts / comme…).
- Example request body:
{
  "platform": "douyin",
  "action": "billboard_rise_list",
  "params": {}
}
- Price: $0.81 per 1,000 requests; failed and empty results are not charged.
- For dozens or hundreds of targets, add "mode": "async" to the body: you get a job_id at once and poll GET https://api.everyinfra.com/api/v1/jobs/{job_id} for the result.
- On 422, fix the request using the suggested parameter names and allowed values in the error; on 429 or 503, wait for Retry-After and try again.

Before writing code, ask me which targets I need, how many, which fields, and what output format I want; then confirm the plan and the rough cost with me.

Request parameters

Name	In	Type	Required	Default	Description
`Authorization`	header	`string`	Yes	-	Bearer followed by your API key. Create it in the console; never put it in a URL or a code repository.
`platform`	body	`string`	Yes	`douyin`	Platform identifier, fixed value.
`action`	body	`string`	Yes	`billboard_rise_list`	Capability identifier, fixed value.
`keyword`	body.params	`string`	No	-	Optional: keep only trends that contain this word, such as `game`; leave it out for the whole rising board.
`page_token`	body.params	`string`	No	-	Page token. Leave it out for the first page (the top 50 trends), then pass back the previous response's `next_page_token` exactly as received, with the other parameters unchanged. Each page holds up to 50 trends and is one call; tokens last 24 hours, and the last page has no `next_page_token`.

Code samples

bash

curl -X POST 'https://api.everyinfra.com/api/v1/social' \
  -H "Authorization: Bearer $EVERYINFRA_API_KEY" \
  -H 'Content-Type: application/json' \
  --data-raw '{
  "platform": "douyin",
  "action": "billboard_rise_list",
  "params": {}
}'

OpenAPI definition (JSON)Samples read the key from the EVERYINFRA_API_KEY environment variable; copied code never contains your key.

Response example

Field preview

No sample response is available for these parameters yet. This preview shows the response shape and fields from the API definition, with … as placeholders; it is not the result of a live call.

json

{
  "id": "req_…",
  "platform": "douyin",
  "action": "billboard_rise_list",
  "results": [
    {
      "rank": …,
      "rank_change": …,
      "title": …,
      "topic_id": …,
      "hot_value": …,
      "video_count": …,
      "category": …,
      "created_at": …,
      "hot_trend": …,
      "next_page_token": …,
      "platform": …
    }
  ],
  "next_page_token": …,
  "pagination": { … },
  "count": …,
  "billing": {
    "charged": …,
    "charged_usd": …,
    "balance_after_usd": …,
    …
  },
  "quota": { … }
}

Response fields

Business data is in results. The table lists the fields a record can contain; values the platform does not show are never made up.

Field	Meaning
`rank`	Position from 1: the trending rank on trending, the position on the Xingtu board on xingtu_creator_rankings, the position on the search board on billboard_search_hot, and the suggestion's place in Douyin's search box on search_suggest.
`rank_change`	Places gained since the board's previous snapshot (billboard_rise_list); negative means it dropped.
`title`	Title. null when the platform has no titles (for example text-only posts).
`topic_id`	Hot Spot Treasure ID of the trend (billboard_rise_list, billboard_challenge_hot); the same trend keeps it across snapshots.
`hot_value`	Heat value, Douyin's own measure, comparable only within one board and window: on trending, the heat of the entry (often empty on the hotspot board); on the Hot Spot Treasure video boards, the board's heat score, rows ordered highest first; on billboard_search_hot, the term's search heat in the window.
`video_count`	Video count: the account's videos on profile and billboard_account_search, videos related to the entry on trending.
`category`	Category name in the platform's own taxonomy, not normalized across platforms.
`created_at`	Creation time, same format as posted_at.
`hot_trend`	Recent heat of the trend: hourly on billboard_rise_list, about every ten minutes on billboard_challenge_hot, as [{time (UTC, ISO 8601), hot_value}] from oldest to newest.
`next_page_token`	Page token (search / user_posts / comments / comment_replies / billboard_video_hot / billboard_low_fan_explosion / billboard_high_completion / billboard_account_search / music_search): pass it back unchanged as page_token to fetch the next page, keeping the other parameters the same; valid for 24 hours. Every row of a page carries the same value, which also appears at the top level of the response. Absent on the last page. Comment pages walk all top-level comments page by page.
`platform`	Source platform identifier, the same as platform in the request (for example xiaohongshu, tiktok).

Errors and billing

401: Missing or invalid key.
402: Insufficient balance. Top up first.
422: Invalid parameter name or value. Fix it using the suggestions in the error. No charge.
429: Per-minute request limit reached. Wait for Retry-After, then try again.
503: Could not complete. The held charge is returned to your balance. If the outcome is unknown, verify it before you retry.
200 empty: No data. No charge.

Errors