Douban Reviews API
API health
- 24h health
- Normal
- 24h average time
- —
- Last checked
- September 26, 2026 at 18:04 (UTC)
- Healthy / normal
- Available
- Limited
- Mostly down
Last 24 hours
Last 30 days
How health is measured
- Health = the share of calls that returned data, in percent. Empty results, failures and unknown outcomes do not count as returning data.
- Levels: 90% and above is healthy, 70% and above is available, 40% and above is limited; anything lower is mostly down.
- A period (the last 24 hours, one hour or one day) gets a score only once it has at least 50 calls. Periods with fewer calls show as normal: a few failures among a handful of calls do not mean the API is down.
- Calls include real customer calls and our own daily probe calls. Request errors (wrong parameters, no balance) are excluded.
- Average time counts only calls that completed normally: response time for sync calls, acceptance to completion for async ones.
By period
| Time (UTC) | Status | Health | Average time |
|---|---|---|---|
| 2026-09-26 18:00 - 18:59 | Normal | — | — |
| 2026-09-26 17:00 - 17:59 | Normal | — | — |
| 2026-09-26 16:00 - 16:59 | Normal | — | — |
| 2026-09-26 15:00 - 15:59 | Normal | — | — |
| 2026-09-26 14:00 - 14:59 | Normal | — | — |
| 2026-09-26 13:00 - 13:59 | Normal | — | — |
| 2026-09-26 12:00 - 12:59 | Normal | — | — |
| 2026-09-26 11:00 - 11:59 | Normal | — | — |
| 2026-09-26 10:00 - 10:59 | Normal | — | — |
| 2026-09-26 09:00 - 09:59 | Normal | — | — |
| 2026-09-26 08:00 - 08:59 | Normal | — | — |
| 2026-09-26 07:00 - 07:59 | Normal | — | — |
| 2026-09-26 06:00 - 06:59 | Normal | — | — |
| 2026-09-26 05:00 - 05:59 | Normal | — | — |
| 2026-09-26 04:00 - 04:59 | Normal | — | — |
| 2026-09-26 03:00 - 03:59 | Normal | — | — |
| 2026-09-26 02:00 - 02:59 | Normal | — | — |
| 2026-09-26 01:00 - 01:59 | Normal | — | — |
| 2026-09-26 00:00 - 00:59 | Normal | — | — |
| 2026-09-25 23:00 - 23:59 | Normal | — | — |
| 2026-09-25 22:00 - 22:59 | Normal | — | — |
| 2026-09-25 21:00 - 21:59 | Normal | — | — |
| 2026-09-25 20:00 - 20:59 | Normal | — | — |
| 2026-09-25 19:00 - 19:59 | Normal | — | — |
| 2026-09-26 | Normal | — | — |
| 2026-09-25 | Normal | — | — |
| 2026-09-24 | Normal | — | — |
| 2026-09-23 | Normal | — | — |
| 2026-09-22 | Normal | — | — |
| 2026-09-21 | Normal | — | — |
| 2026-09-20 | Normal | — | — |
| 2026-09-19 | Normal | — | — |
| 2026-09-18 | Normal | — | — |
| 2026-09-17 | Normal | — | — |
| 2026-09-16 | Normal | — | — |
| 2026-09-15 | Normal | — | — |
| 2026-09-14 | Normal | — | — |
| 2026-09-13 | Normal | — | — |
| 2026-09-12 | Normal | — | — |
| 2026-09-11 | Normal | — | — |
| 2026-09-10 | Normal | — | — |
| 2026-09-09 | Normal | — | — |
| 2026-09-08 | Normal | — | — |
| 2026-09-07 | Normal | — | — |
| 2026-09-06 | Normal | — | — |
| 2026-09-05 | Normal | — | — |
| 2026-09-04 | Normal | — | — |
| 2026-09-03 | Normal | — | — |
| 2026-09-02 | Normal | — | — |
| 2026-09-01 | Normal | — | — |
| 2026-08-31 | Normal | — | — |
| 2026-08-30 | Normal | — | — |
| 2026-08-29 | Normal | — | — |
| 2026-08-28 | Normal | — | — |
Retrieve public reviews from Douban. Accepts these parameters: url. Returns these fields: text, subject_id, subject_type, and reply_count.
Price $1.39 per 1,000 requests ($0.001389 per call). Failed calls and empty results are not charged. Synchronous. For slow jobs add "mode": "async" to the body, take the job_id and poll.
Request parameters
| Name | In | Type | Required | Default | Description |
|---|---|---|---|---|---|
Authorization | header | string | Yes | - | Bearer followed by your API key. Create it in the console; never put it in a URL or a code repository. |
platform | body | string | Yes | douban | Platform identifier, fixed value. |
action | body | string | Yes | reviews | Capability identifier, fixed value. |
url | body.params | Not declared | Yes | - | Specifies the target subject URL formatted as /subject/<ID>/ on movie.douban.com, book.douban.com, or music.douban.com for reviews or comments actions, or as www.douban.com/group/topic/<ID>/ for group_topic. Long reviews, short comments, and group topic replies are handled by separate action endpoints. |
limit | body.params | integer (1–50) | No | 15 |
Code samples
curl -X POST 'https://api.everyinfra.com/api/v1/social' \
-H "Authorization: Bearer $EVERYINFRA_API_KEY" \
-H 'Content-Type: application/json' \
--data-raw '{
"platform": "douban",
"action": "reviews",
"params": {
"url": "https://book.douban.com/subject/2567698/"
}
}'[OpenAPI definition (JSON)]Samples read the key from the EVERYINFRA_API_KEY environment variable; copied code never contains your key.
Response example
Captured September 26, 2026 at 08:56 (UTC) by calling this API with the parameters in the code sample above. results and count are that call's real response with personal information (names, handles, avatars, profile links, contact details) removed; the list keeps the first 2. id, billing and quota differ on every call, so only their shape is shown.
{
"id": "req_…",
"platform": "douban",
"action": "reviews",
"results": [
{
"id": "1342728",
"url": "https://book.douban.com/review/1342728/",
"subject_id": "2567698",
"subject_name": "三体",
"subject_type": "book",
"title": "《三体》:当代史的科幻书写",
"text": "评论刘慈欣的《三体》是件困难的事情,因为可以选择的角度太多。反复思量过后挑了这个角度,在我看来,写一部好的科幻小说,或者一部适合评论家们的科幻小说都不是难事,但是当作家的心思并不是用在这些上面,而是捎带着完成了这两件事的时候,就并不是那么容易了。很容易看出,刘慈欣在《三体》中表现出来的野心很大,不仅是试图将自己的作品序列进行系统化整理和某种程度上的超越,更重要的是试图给出一些达到“科幻”这个语词内涵之中的尝试。这些尝试的可贵之处勇气可嘉,以至于《三体》作为一部小说这样那样的问题都不足以稍稍削弱这种尝试中闪耀着的光芒。\n\n作为一部小说的《三体》,并不是一部…",
"rating": 4,
"rating_label": "推荐",
"author_name": "(已隐去)",
"author_url": "https://www.douban.com/(已隐去)",
"author_avatar_url": "https://img3.doubanio.com/(已隐去)",
"reply_count": 268,
"posted_at": "2008-04-02T19:20:04+00:00",
"platform": "douban",
"rating_scale": 10
},
{
"id": "1347293",
"url": "https://book.douban.com/review/1347293/",
"subject_id": "2567698",
"subject_name": "三体",
"subject_type": "book",
"title": ",外星人,躲在暗处",
"text": "三个质量相同或相近的物体,会在引力作用下进行着无规律、永不重复的复杂运动。《三体》那本书里,半人马座的三颗星,就是“三体运动”中的“三体”,三颗恒星的光和热蕴育了一种智慧生命。\n只是,太阳有3颗,是件麻烦事儿——有时太热,有时又太冷。那里的人把太阳正常的时期叫恒纪元,其他都是乱纪元。乱纪元时候,休眠;恒纪元的时候,才能繁衍生息,文明才能发展。经常地,当预言师拿出一份万年历,认为一段长期的恒纪元即将开始时,居民刚刚结束休眠,乱纪元却忽然出现,文明毁灭于大火或冰冻中。前191次被毁灭的文明都试图找到一份准确的万年历,直到第192次被毁灭的文明时,人们才终于明…",
"rating": 5,
"rating_label": "力荐",
"author_name": "(已隐去)",
"author_url": "https://www.douban.com/(已隐去)",
"author_avatar_url": "https://img2.doubanio.com/(已隐去)",
"reply_count": 149,
"posted_at": "2008-04-08T01:25:48+00:00",
"platform": "douban",
"rating_scale": 10
}
],
"count": 15,
"billing": { … },
"quota": { … }
}Response fields
Business data is in results. The table lists the fields a record can contain; values the source does not provide are never made up.
| Field | Meaning |
|---|---|
id | The record's unique ID on the source platform. Unique only within one platform; IDs can repeat across platforms. |
url | Link to the record on the source platform. |
subject_id | Keeps the platform's own meaning |
subject_name | Keeps the platform's own meaning |
subject_type | Keeps the platform's own meaning |
title | Title. null when the platform has no titles (for example text-only posts). |
text | Body text with HTML removed. Long text may be truncated. |
rating | Rating. The scale varies by platform: rating_scale on the same row gives the maximum (usually 5; Booking, Douban, iQIYI and NAVER use 10). Convert with rating_scale before comparing across platforms, or the comparison can come out backwards. |
rating_scale | Maximum of rating in the same row: 5 for five-star scales, 10 for ten-point scales. Present only when the row has a rating. |
rating_label | Keeps the platform's own meaning |
author_name | Author's display name. |
author_url | Link to the author's profile on the source platform. |
author_avatar_url | Keeps the platform's own meaning |
reply_count | Replies, usually replies to a comment. null means not disclosed. |
posted_at | Publish time in ISO 8601, UTC (for example 2026-08-07T12:34:56+00:00). Non-standard strings from the platform are passed through as is, so parse defensively. null means the platform does not disclose it. |
platform | Source platform identifier, the same as platform in the request (for example xiaohongshu, tiktok). |
Errors and billing
- 401
- Missing or invalid key. Authentication runs before parameter checks, so unauthenticated requests never see the parameter schema.
- 422
- Wrong parameter name or value. The error lists the parameters and allowed values this capability accepts and the closest match; it happens before any charge.
- 402
- Insufficient balance. Top up first.
- 429
- Per-minute request limit reached. Wait for Retry-After and try again.
- 503
- Could not complete right now. Any charge for the call goes back to your balance automatically, and the billing receipt in the response states the actual outcome, including when it is not yet known. Do not resend blindly.
- 200 empty
- The request completed without data and is not charged (billing.reason = empty_result_refunded).
Official references
Used only to check objects and terms. They do not imply authorization or endorsement of EveryInfra by the platform.
- Douban Movies: Long Reviews, Short Reviews, and Visibility Limits ↗
Douban Movies explains movie reviews and short reviews separately, noting that the short review section does not show all short reviews and that collapsed content has differing public visibility. Movie review lists returned by this endpoint should not be taken as a complete history or all audience opinions; this source does not replace separate rules for books or music.
Checked 2026-09-04