Douyin Creator benchmark 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 | — | — |
Compare relative Douyin account indicators without treating them as sales or conversion results. Accepts these parameters: user_id. Returns these fields: user_id, average_comment_count, post_count_percentile, and share_count_percentile.
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
| 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 | douyin | Platform identifier, fixed value. |
action | body | string | Yes | creator_benchmark | Capability identifier, fixed value. |
user_id | body.params | Not declared | Yes | - | The Douyin creator's secUid, usually beginning with MS4w, used to read the available account averages and percentiles. It is not a nickname or short numerical Douyin ID. |
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": "douyin",
"action": "creator_benchmark",
"params": {
"user_id": "https://www.douyin.com/user/MS4wLjABAAAAk1tZ-L085zZf2yW_H5dnVFZWyk8Rt8v4RAvf9KhTyPoVdMDxTs7Q_rvgTJGWXezS"
}
}'[OpenAPI definition (JSON)]Samples read the key from the EVERYINFRA_API_KEY environment variable; copied code never contains your key.
Response example
There is no real sample for these example parameters yet: this shows the response shape and fields from the contract, with … as placeholders. It is not the result of a real call.
{
"id": "req_…",
"platform": "douyin",
"action": "creator_benchmark",
"results": {
"user_id": …,
"average_post_count": …,
"average_comment_count": …,
"average_share_count": …,
"average_follower_growth": …,
"average_like_count": …,
"post_count_percentile": …,
"comment_count_percentile": …,
"share_count_percentile": …,
"follower_growth_percentile": …,
"like_count_percentile": …,
"platform": …
},
"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 |
|---|---|
user_id | User's unique ID on the source platform. |
average_post_count | Keeps the platform's own meaning |
average_comment_count | Keeps the platform's own meaning |
average_share_count | Keeps the platform's own meaning |
average_follower_growth | Keeps the platform's own meaning |
average_like_count | Keeps the platform's own meaning |
post_count_percentile | Keeps the platform's own meaning |
comment_count_percentile | Keeps the platform's own meaning |
share_count_percentile | Keeps the platform's own meaning |
follower_growth_percentile | Keeps the platform's own meaning |
like_count_percentile | Keeps the platform's own meaning |
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).