/douban/music/comments

POST /api/douban/music/comments

Price: 1 credit

Get Douban Music Comments

How to use it

List short comments on a Douban music album in Douban's own ranking, each with its star rating, helpful votes, time and author. Filter to listened or want-to-listen users and to positive, neutral or negative ratings.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• music string required — Douban music album id, or its music.douban.com/subject URL (examples: "1407700"; minLength: 1)
• count integer required — Max number of results (examples: 20; min: 1; max: 100)
• status string — Comments from users who have listened to the album, or from users who want to (default: "done"; one of: "done", "wish")
• rating string nullable — Only comments rated positive (4-5 stars), neutral (3 stars) or negative (1-2 stars) (one of: "positive", "neutral", "negative")

Response

• @type string (default: "DoubanComment")
• id string required
• url string nullable
• text string nullable
• created_at integer nullable
• rating number nullable
• helpful_count integer nullable
• status_label string nullable
• location string nullable
• author object nullable
  • @type string (default: "DoubanUserRef")
  • alias string required
  • name string nullable
  • url string required
  • image 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.
• 403 — Douban shows this comment list only to logged-in users.
• 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 — Album not found. Check the id or URL. 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.