/douban/books

POST /api/douban/books

Price: 5 credits

Get Douban Book

How to use it

Get one Douban book by id or book.douban.com/subject URL, with its publication details, description, author bio and Douban rating. Related books carry ids for this endpoint. A movie or music id returns 412.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• book string required — Douban book id, or its book.douban.com/subject URL (examples: "1084336", "https://book.douban.com/subject/1084336/"; minLength: 1)

Response

• @type string (default: "DoubanBook")
• id string required
• url string required
• subtitle string nullable
• original_title string nullable
• image string nullable
• authors array (default: [])
  • @type string (default: "DoubanPersonRef")
  • id string nullable
  • name string required
  • url string nullable
• translators array (default: [])
  • @type string (default: "DoubanPersonRef")
  • id string nullable
  • name string required
  • url string nullable
• publisher string nullable
• producer string nullable
• publish_date string nullable
• page_count integer nullable
• binding string nullable
• price string nullable
• series string nullable
• isbn string 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
• author_summary string nullable
• tags array (default: [])
• comment_count integer nullable
• review_count integer nullable
• reading_count integer nullable
• read_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 — Book 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.