/qqmusic/songs/comments

POST /api/qqmusic/songs/comments

Price: 20 credits

Get listener comments on a QQ Music song, with their replies, likes and stated province

How to use it

Song mid, numeric song id and a song page URL all resolve here. `hot` and `newest` are two separate corpora, not two orderings of one: `hot` is a curated subset that runs out after a few thousand comments however large the song's discussion is, while `newest` walks the whole discussion from the most recent backwards. `location` is the province the commenter's account reports and only some comments carry one, so treat a missing value as unstated rather than as somewhere outside China. `replies` carries at most one preview reply per comment; `reply_count` is the true total and is routinely far larger than `len(replies)`, so do not read `replies` as the complete thread.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• song string required — Song mid, numeric song id, or a QQ Music song page URL (examples: "0039MnYb0qxYhV", "97773", "https://y.qq.com/n/ryqq/songDetail/0039MnYb0qxYhV"; minLength: 1)
• count integer required — Max number of comments to return (min: 1; max: 3000)
• sort string — `hot` returns the listeners' most-liked comments, `newest` the most recently posted (default: "hot"; one of: "hot", "newest")

Response

• @type string (default: "QqmusicComment")
• id string required
• seq_no string nullable
• text string nullable
• author object nullable
  • @type string (default: "QqmusicCommentAuthor")
  • uin string required
  • name string nullable
  • image string nullable
• published_at integer nullable
• like_count integer nullable
• reply_count integer nullable
• location string nullable
• device string nullable
• image string nullable
• is_liked_by_artist boolean nullable
• replies array (default: [])
  • @type string (default: "QqmusicCommentReply")
  • id string required
  • text string nullable
  • author object nullable
    • @type string (default: "QqmusicCommentAuthor")
    • uin string required
    • name string nullable
    • image string nullable
  • like_count integer nullable
  • is_liked_by_artist boolean 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 — No song exists for the given id. 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.