/netease/tracks/comments

POST /api/netease/tracks/comments

Price: 10 credits

Get listener comments on a NetEase Cloud Music track, with their likes and reply threads

How to use it

The three sorts are three different corpora, not three orderings of one: `newest` runs out after about 1,100 comments however busy the track is, while `hot` and `oldest` keep going into the tens of thousands. NetEase only began recording `location` in 2022, so the commenter's province is there on recent comments and blank on older ones, and `oldest` — which walks the thread from its first comment — never returns one. `replied_to` carries the comments this one answers, not the answers to it; `reply_count` is the number of answers and nothing here walks them. An id that is not a track at all comes back as an empty list, exactly like a real track nobody has commented on, so confirm the id through the track endpoint when that matters.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• track string required — Track id, or a NetEase Cloud Music track page URL (examples: "186016", "https://music.163.com/song?id=186016"; minLength: 1)
• count integer required — Max number of comments to return (min: 1; max: 10000)
• sort string — `newest` walks back from the latest comment, `hot` from the most-liked, `oldest` forward from the first comment ever posted (default: "newest"; one of: "newest", "hot", "oldest")

Response

• @type string (default: "NeteaseComment")
• id string required
• text string nullable
• author object nullable
  • @type string (default: "NeteaseCommentAuthor")
  • id string required
  • name string nullable
  • url string nullable
  • image string nullable
  • expert_tags array (default: [])
  • user_type integer nullable
  • vip_type integer nullable
• published_at integer nullable
• like_count integer nullable
• reply_count integer nullable
• location string nullable
• thread_id string nullable
• parent_comment_id string nullable
• image string nullable
• is_pinned boolean nullable
• replied_to array (default: [])
  • @type string (default: "NeteaseRepliedComment")
  • id string required
  • text string nullable
  • author object nullable
    • @type string (default: "NeteaseCommentAuthor")
    • id string required
    • name string nullable
    • url string nullable
    • image string nullable
    • expert_tags array (default: [])
    • user_type integer nullable
    • vip_type integer nullable
  • location string nullable
  • status_code string 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 — The entity was not found, or a precondition failed 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.