Douyin Comments API

POST

API health

24h health
Normal
24h average time
—
Last checked
September 26, 2026 at 18:04 (UTC)
  • Healthy / normal
  • Available
  • Limited
  • Mostly down
Health APINormal
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)StatusHealthAverage time
2026-09-26 18:00 - 18:59Normal——
2026-09-26 17:00 - 17:59Normal——
2026-09-26 16:00 - 16:59Normal——
2026-09-26 15:00 - 15:59Normal——
2026-09-26 14:00 - 14:59Normal——
2026-09-26 13:00 - 13:59Normal——
2026-09-26 12:00 - 12:59Normal——
2026-09-26 11:00 - 11:59Normal——
2026-09-26 10:00 - 10:59Normal——
2026-09-26 09:00 - 09:59Normal——
2026-09-26 08:00 - 08:59Normal——
2026-09-26 07:00 - 07:59Normal——
2026-09-26 06:00 - 06:59Normal——
2026-09-26 05:00 - 05:59Normal——
2026-09-26 04:00 - 04:59Normal——
2026-09-26 03:00 - 03:59Normal——
2026-09-26 02:00 - 02:59Normal——
2026-09-26 01:00 - 01:59Normal——
2026-09-26 00:00 - 00:59Normal——
2026-09-25 23:00 - 23:59Normal——
2026-09-25 22:00 - 22:59Normal——
2026-09-25 21:00 - 21:59Normal——
2026-09-25 20:00 - 20:59Normal——
2026-09-25 19:00 - 19:59Normal——
2026-09-26Normal——
2026-09-25Normal——
2026-09-24Normal——
2026-09-23Normal——
2026-09-22Normal——
2026-09-21Normal——
2026-09-20Healthy99%21.00 s
2026-09-19Normal——
2026-09-18Normal——
2026-09-17Limited68%54.05 s
2026-09-16Limited52%56.08 s
2026-09-15Healthy100%34.28 s
2026-09-14Normal——
2026-09-13Healthy98%13.22 s
2026-09-12Normal——
2026-09-11Healthy99%13.80 s
2026-09-10Normal——
2026-09-09Normal——
2026-09-08Normal——
2026-09-07Normal——
2026-09-06Normal——
2026-09-05Normal——
2026-09-04Normal——
2026-09-03Normal——
2026-09-02Normal——
2026-09-01Normal——
2026-08-31Normal——
2026-08-30Normal——
2026-08-29Normal——
2026-08-28Normal——

Retrieve public comments from Douyin. Accepts these parameters: url. Returns these fields: like_count, author_name, reply_count, and posted_at.

Price $0.56 per 1,000 requests ($0.000556 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

NameInTypeRequiredDefaultDescription
AuthorizationheaderstringYes-Bearer followed by your API key. Create it in the console; never put it in a URL or a code repository.
platformbodystringYesdouyinPlatform identifier, fixed value.
actionbodystringYescommentsCapability identifier, fixed value.
urlbody.paramsNot declaredYes-Full URL of the target Douyin video, formatted as https://www.douyin.com/video/<video_id>. Fetches video details in video, comments in comments, or audio transcripts in transcript. Do not pass user profile or search page URLs.
limitbody.paramsinteger (1–150)No20

Code samples

bash
curl -X POST 'https://api.everyinfra.com/api/v1/social' \
  -H "Authorization: Bearer $EVERYINFRA_API_KEY" \
  -H 'Content-Type: application/json' \
  --data-raw '{
  "platform": "douyin",
  "action": "comments",
  "params": {
    "url": "https://www.douyin.com/video/7633646113853104116"
  }
}'

[OpenAPI definition (JSON)]Samples read the key from the EVERYINFRA_API_KEY environment variable; copied code never contains your key.

Response example

Real response

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.

json
{
  "id": "req_…",
  "platform": "douyin",
  "action": "comments",
  "results": [
    {
      "id": "(已隐去)",
      "text": "也夸夸我好吗?毕竟辛苦了大半天",
      "like_count": 36358,
      "reply_count": 3916,
      "author_name": "(已隐去)",
      "author_id": "(已隐去)",
      "ip_location": "(已隐去)",
      "liked_by_author": false,
      "is_reply": false,
      "posted_at": "2026-05-16T07:44:26+00:00",
      "platform": "douyin"
    },
    {
      "id": "(已隐去)",
      "text": "女人也可以做漂亮饭[抠鼻][抠鼻][抠鼻][抠鼻]",
      "like_count": 7615,
      "reply_count": 645,
      "author_name": "(已隐去)",
      "author_id": "(已隐去)",
      "ip_location": "(已隐去)",
      "liked_by_author": false,
      "is_reply": false,
      "posted_at": "2026-05-12T15:26:16+00:00",
      "platform": "douyin"
    }
  ],
  "count": 42,
  "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.

FieldMeaning
idThe record's unique ID on the source platform. Unique only within one platform; IDs can repeat across platforms.
textBody text with HTML removed. Long text may be truncated.
like_countLikes. null means the platform or this capability does not disclose it; it is not 0.
reply_countReplies, usually replies to a comment. null means not disclosed.
author_nameAuthor's display name.
author_idAuthor's unique ID on the source platform.
ip_locationKeeps the platform's own meaning
liked_by_authorKeeps the platform's own meaning
is_replyKeeps the platform's own meaning
reply_to_idKeeps the platform's own meaning
posted_atPublish 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.
platformSource 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).