Douyin Xingtu connected-user sources API
API health
- 24h health
- Normal
- 24h average time
- —
- Healthy / normal
- Available
- Limited
- Mostly down
Last 24 hours
Last 30 days
See which content categories a Douyin creator's connected users came from, as Xingtu counts them: a tree of up to three levels, usually personal versus Xingtu content, then category and subcategory, each with a count.
Price $16 per 1,000 requests ($0.016 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
Please help me write a data collection script with the EveryInfra Douyin Xingtu connected-user sources endpoint (douyin/xingtu_touch_distribution).
How the endpoint works:
- 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 xingtu_touch_distribution, and put the parameters inside params.
- Required parameters:
- douyin_id: The creator's visible Douyin ID (unique_id, from creator_search) or the 19-digit Xingtu creator_id returned by xingtu_creator_search. A creator who is not on Xingtu gives an empty result, which is not charged.
- Returns one object. Main fields: creator_id, categories (On xingtu_conversion_ability, the promo…).
- Example request body:
{
"platform": "douyin",
"action": "xingtu_touch_distribution",
"params": {
"douyin_id": "XiaoZhenlla"
}
}
- Price: $16 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 | xingtu_touch_distribution | Capability identifier, fixed value. |
douyin_id | body.params | string | Yes | - | The creator's visible Douyin ID (unique_id, from creator_search) or the 19-digit Xingtu creator_id returned by xingtu_creator_search. A creator who is not on Xingtu gives an empty result, which is not charged. |
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": "xingtu_touch_distribution",
"params": {
"douyin_id": "XiaoZhenlla"
}
}'OpenAPI definition (JSON)Samples read the key from the EVERYINFRA_API_KEY environment variable; copied code never contains your key.
Response example
No sample response is available for these parameters yet. This preview shows the response shape and fields from the API definition, with … as placeholders; it is not the result of a live call.
{
"id": "req_…",
"platform": "douyin",
"action": "xingtu_touch_distribution",
"results": {
"creator_id": …,
"categories": …,
"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 |
|---|---|
creator_id | Keeps the platform's own meaning |
categories | On xingtu_conversion_ability, the promoted product categories: [{name, share (0 to 1), sales_range_cny}], only when the creator promoted products. On xingtu_touch_distribution, the content categories connected users came from, up to three levels: [{name, touch_count, subcategories (same shape)}]. |
platform | Source platform identifier, the same as platform in the request (for example xiaohongshu, tiktok). |
Errors and billing
- 401
- Missing or invalid key.
- 402
- Insufficient balance. Top up first.
- 422
- Invalid parameter name or value. Fix it using the suggestions in the error. No charge.
- 429
- Per-minute request limit reached. Wait for Retry-After, then try again.
- 503
- Could not complete. The held charge is returned to your balance. If the outcome is unknown, verify it before you retry.
- 200 empty
- No data. No charge.