/douban/music

POST /api/douban/music

Price: 5 credits

Get Douban Music Album

How to use it

Get one Douban music album by id or music.douban.com/subject URL: title, performers, genre, release date, label, track list, Douban rating with its star distribution, description, tags and related albums.

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", "https://music.douban.com/subject/1407700/"; minLength: 1)

Response

• @type string (default: "DoubanMusic")
• id string required
• url string required
• image string nullable
• performers array (default: [])
  • @type string (default: "DoubanPersonRef")
  • id string nullable
  • name string required
  • url string nullable
• genres array (default: [])
• album_type string nullable
• medium string nullable
• release_date string nullable
• publisher string nullable
• disc_count integer nullable
• isrc string nullable
• barcode string nullable
• aliases array (default: [])
• tracks array (default: [])
  • @type string (default: "DoubanTrack")
  • position integer nullable
• rating number nullable
• rating_count integer nullable
• rating_distribution array (default: [])
  • @type string (default: "DoubanRatingShare")
  • stars integer required
  • percent number required
• summary string nullable
• tags array (default: [])
• comment_count integer nullable
• review_count integer nullable
• listening_count integer nullable
• listened_count integer nullable
• wish_count integer nullable
• recommendations array (default: [])
  • @type string (default: "DoubanSubjectRef")
  • id string required
  • url string required
  • image string nullable
  • rating 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 — 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.