/qqmusic/charts

POST /api/qqmusic/charts

Price: 20 credits

Get a QQ Music chart with its ranked songs, each song's move since the last edition, and the chart's own update date

How to use it

Charts refresh on their own cadence, so read `period` and `updated_date` off the result rather than assuming today. To walk history, send `period` in the format the chart reports in `period_format` - the two formats are not interchangeable. Archive coverage is patchy and differs per chart. `rank_change` is signed positions moved and is null on charts that publish no movement.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• chart string required — Which QQ Music chart to read (one of: "soaring", "hot_songs", "new_songs", "pop_index", "recognized_songs", "mainland_china", "hong_kong", "taiwan", "western", "korea", "japan", "joox_local", "tvb_gold_songs", "kkbox_taiwan", "rap", "electronic", "game_music", "anime_music", "film_and_tv", "variety_show_new_songs", "chinese_style", "karaoke", "douyin", "dj_dance", "internet_songs", "billboard", "melon", "uk_official", "oricon")
• song_count integer — Max number of ranked songs to return (default: 100; min: 1; max: 300)
• period string nullable — Read an archived edition instead of the current one. Daily charts take `YYYY-MM-DD`, weekly charts `YYYY_WW`; the response reports which one a chart uses in `period_format` (examples: "2026-08-20", "2026_30")

Response

• @type string (default: "QqmusicChart")
• id string required
• name string required
• subtitle string nullable
• description string nullable
• url string nullable
• image string nullable
• period string nullable
• period_format string nullable
• updated_date string nullable
• ranked_song_count integer nullable
• listen_count integer nullable
• songs array (default: [])
  • @type string (default: "QqmusicChartSong")
  • mid string required
  • id string nullable
  • name string nullable
  • subtitle string nullable
  • url string nullable
  • image string nullable
  • singers array (default: [])
    • @type string (default: "QqmusicSongSinger")
    • mid string required
    • id string nullable
    • name string nullable
    • url string nullable
    • image string nullable
  • album object nullable
    • @type string (default: "QqmusicSongAlbum")
    • mid string required
    • id string nullable
    • name string nullable
    • published_date string nullable
    • url string nullable
    • image string nullable
  • duration_seconds integer nullable
  • published_date string nullable
  • disc_number integer nullable
  • track_number integer nullable
  • bpm integer nullable
  • is_exclusive boolean nullable
  • is_paid_play boolean nullable
  • is_paid_download boolean nullable
  • is_vip_only boolean nullable
  • rank integer required
  • rank_change integer nullable
  • is_new_entry boolean nullable
  • growth_percent number nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — This chart has no edition for the requested period. Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.