Douyin Creator audience API

Q: What is the device price band?

device_price_band, the default dimension, groups a creator's followers by the price range of the phones they use, which helps when you match a product's price level with a creator's audience. As with the other dimensions, each bucket comes back as a share from 0 to 1 with its own TGI.

Q: Can I get all four dimensions in one call?

No. Each call returns one dimension, chosen with dimension: device_price_band when you leave it out, or gender, age or province. Call once per dimension you need. dimension_code in each response records which one it holds, so results from separate calls stay labeled when you store them together.

POST

API health

24h health: Normal
24h average time: —

Healthy / normal
Available
Limited
Mostly down

Normal

Last 24 hours

Last 30 days

Break down a Douyin creator's followers by device price band, gender, age or province, with each bucket's share and its TGI index. Shares are decimals between 0 and 1, not percentages, and the buckets are not buyer records or individual people.

Douyin Creator audience reads who follows one creator, given the creator's user_id, along one dimension: device price band (the default), gender, age or province. Each bucket in audience_distribution carries the share of followers it holds, and audience_tgi shows how strongly that group is represented compared with the Douyin average. Brands and agencies use it to check that a creator's followers match the customers they want to reach before they book a campaign.

Shares are decimals from 0 to 1 rather than percentages, so 0.42 means 42 percent of followers; they are neither follower counts nor shares of buyers. TGI sits on a separate scale and is the number to read for fit, since a bucket with a modest share can still be strongly over-represented. For user_id, pass the creator's secUid, the long string that usually begins with MS4w, or the whole profile link that contains it, as the example does.

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.

AI prompt

Paste this into your AI assistant. It already holds this endpoint's parameters, response fields and an example request, so the assistant can ask what you need and then write the scraper.

Please help me write a data collection script with the EveryInfra Douyin Creator audience endpoint (douyin/creator_audience).

Endpoint contract:
- Request: POST https://api.everyinfra.com/api/v1/social with the header Authorization: Bearer <API key>. Read the key from the EVERYINFRA_API_KEY environment variable and never hard-code it.
- In the request body, set platform to douyin and action to creator_audience, and put the parameters inside params.
- Required parameters:
- user_id: The Douyin creator's secUid, usually beginning with MS4w, used to read the available audience distribution and TGI signals. Use user_id from creator discovery, not a nickname, short Douyin ID, or buyer identifier.
- Optional parameters:
- dimension: Selects the creator_audience follower-segment view: device_price_band (default), gender, age, or province. Distribution values are raw share decimals from 0 to 1, not percentages; TGI remains a separate index. (allowed: age / device_price_band / gender / province)
- Returns one object. Main fields: user_id, audience_distribution, audience_tgi, dimension_code.
- Example request body:
{
"platform": "douyin",
"action": "creator_audience",
"params": {
"user_id": "https://www.douyin.com/user/MS4wLjABAAAAk1tZ-L085zZf2yW_H5dnVFZWyk8Rt8v4RAvf9KhTyPoVdMDxTs7Q_rvgTJGWXezS"
}
}
- Price: $0.56 per 1,000 requests; failed and empty results are not charged.
- For dozens or hundreds of targets, add "mode": "async" to the body: you get a job_id at once and poll GET https://api.everyinfra.com/api/v1/jobs/{job_id} for the result.
- On 422, fix the request using the suggested parameter names and allowed values in the error; on 429 or 503, wait for Retry-After and try again.

Before writing code, ask me which targets I need, how many, which fields, and what output format I want; then confirm the plan and the rough cost with me.

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_audience`	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 audience distribution and TGI signals. Use `user_id` from creator discovery, not a nickname, short Douyin ID, or buyer identifier.
`dimension`	body.params	`enum`	No	-	Selects the `creator_audience` follower-segment view: `device_price_band` (default), `gender`, `age`, or `province`. Distribution values are raw share decimals from 0 to 1, not percentages; TGI remains a separate index. This parameter does not request individual follower records or buyer data.Allowed values`agedevice_price_bandgenderprovince`

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": "creator_audience",
  "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

Field preview

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.

json

{
  "id": "req_…",
  "platform": "douyin",
  "action": "creator_audience",
  "results": {
    "user_id": …,
    "audience_distribution": …,
    "audience_tgi": …,
    "dimension_code": …,
    "platform": …
  },
  "billing": {
    "charged": …,
    "charged_usd": …,
    "balance_after_usd": …,
    …
  },
  "quota": { … }
}

Response fields

Business data is in results. The table lists the fields a record can contain; values the platform does not show are never made up.

Field	Meaning
`user_id`	User's unique ID on the platform.
`audience_distribution`	Keeps the platform's own meaning
`audience_tgi`	Keeps the platform's own meaning
`dimension_code`	Keeps the platform's own meaning
`platform`	Source platform identifier, the same as platform in the request (for example xiaohongshu, tiktok).

FAQ

What is the device price band?

device_price_band, the default dimension, groups a creator's followers by the price range of the phones they use, which helps when you match a product's price level with a creator's audience. As with the other dimensions, each bucket comes back as a share from 0 to 1 with its own TGI.

What does `audience_tgi` add to the share?

TGI compares each bucket with the Douyin platform average and is measured independently of the share. A group can be a small slice of followers yet have a high TGI, meaning the creator draws that group more than Douyin does overall. Use the share to size a group and TGI to judge how distinctive the audience is.

Can I get all four dimensions in one call?

No. Each call returns one dimension, chosen with dimension: device_price_band when you leave it out, or gender, age or province. Call once per dimension you need. dimension_code in each response records which one it holds, so results from separate calls stay labeled when you store them together.

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: The account's per-minute request limit was reached (all of its API keys count together; a key's own lower limit applies first). Wait for Retry-After and try again; a rate package in the console raises the limit.
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).