Douyin Xingtu creator rate card API

POST

API health

24h health: Normal
24h average time: —

Healthy / normal
Available
Limited
Mostly down

Normal

Last 24 hours

Last 30 days

See the rate tiers a Douyin creator lists on Xingtu, each with format, current and original quote, settlement note, video type and open status. Use the douyin_id from creator_search; these are posted rates, not an accepted contract or final settlement.

Douyin Xingtu creator rate card reads the quote tiers a creator publishes on Xingtu for brand collaborations, given the creator's douyin_id, the handle displayed on their Douyin profile. Each entry in rate_tiers describes one way to work together: the format, the current quote and the original quote, how the fee is settled, the video type it covers and whether the tier is open. Campaign planners rely on it to set budgets, compare creators of similar reach on price and see which formats a creator takes on.

Treat the tiers as the prices the creator displays, not as an accepted contract or a final settlement. Where the current quote sits below the original, the gap shows a discount on display. Take the douyin_id from Douyin Creator search or the profile, because Xingtu creator search results do not carry it. creator_id is Xingtu's own ID for the creator, separate from both the public profile ID and the Douyin ID you pass.

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 Xingtu creator rate card endpoint (douyin/xingtu_rate_card).

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 xingtu_rate_card, and put the parameters inside params.
- Required parameters:
  - douyin_id: The visible Douyin account ID (unique_id) returned by the ordinary creator_search action and required by xingtu_creator_analytics and xingtu_rate_card; xingtu_creator_search does not return it.
- Returns one object. Main fields: creator_id, rate_tiers.
- Example request body:
{
  "platform": "douyin",
  "action": "xingtu_rate_card",
  "params": {
    "douyin_id": "XiaoZhenlla"
  }
}
- 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	`xingtu_rate_card`	Capability identifier, fixed value.
`douyin_id`	body.params	Not declared	Yes	-	The visible Douyin account ID (`unique_id`) returned by the ordinary `creator_search` action and required by `xingtu_creator_analytics` and `xingtu_rate_card`; `xingtu_creator_search` does not return it. It is distinct from a `user_id` (`secUid`), Xingtu `creator_id`, and nickname.

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

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": "xingtu_rate_card",
  "results": {
    "creator_id": …,
    "rate_tiers": …,
    "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
`rate_tiers`	Keeps the platform's own meaning
`platform`	Source platform identifier, the same as platform in the request (for example xiaohongshu, tiktok).

FAQ

Are the quotes in `rate_tiers` final prices?

No. They are the quotes Xingtu shows for each tier, not an agreed contract and not what is finally settled. Use them to plan budgets and compare creators, and treat the terms of a real booking as a separate agreement made when the deal is done.

What does each tier contain?

A description of the collaboration format, the current quote, the original quote, a note on how the fee is settled, the video type the tier covers and whether it is open. Compare creators tier by tier on the same video type; mixing types can make one creator look cheaper than another.

How do I weigh a quote against a creator's reach?

Read the same creator with the Douyin Xingtu creator analytics capability, using the same douyin_id; it returns follower count and the play average Xingtu publishes for the creator. Dividing a tier's quote by average plays gives a rough cost per view, a fairer way to compare creators than price alone.

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).