Youku Details API
API health
- 24h health
- Normal
- Healthy / normal
- Available
- Limited
- Mostly down
Last 24 hours
Last 30 days
Check a Youku creator from the encoded creator ID. Get name, bio, gender, location, follower and like counts and verification note. Use the encoded UID from video author data, not a username, show ID or channel URL. Private analytics are not exposed.
Send POST https://api.everyinfra.com/api/v1/social with platform set to youku and action set to profile. Price $1.39 per 1,000 requests ($0.001389 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.
Youku Details reads one creator's public profile from the encoded user_id and returns the name, bio, avatar, gender, location, follower and like counts, verification status with its description, the numeric ID and the profile link. Brands, agencies and media researchers use it to vet Youku creators before a partnership, compare accounts by audience size, or keep a current record of the channels they follow.
user_id is an encoded creator UID such as UMzkwNzY4NzQw, not a username, show ID or profile URL. numeric_id is the same account's numeric ID, worth keeping for matching. location is passed through as Youku shows it, and a null follower_count or like_count means the number is not public, not that it is zero.
AI prompt
#Please help me write a data collection script with the EveryInfra Youku Details endpoint (youku/profile).
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 youku and action to profile, and put the parameters inside params.
- Required parameters:
- user_id: The encoded creator UID required by the profile action, retrieved from video author metadata. Do not provide a username, show ID, or full channel homepage URL.
- Returns one object. Main fields: user_id, numeric_id, name, url, bio, avatar_url, gender, like_count, follower_count, is_verified, verified_desc, location.
- Example request body:
{
"platform": "youku",
"action": "profile",
"params": {
"user_id": "UMzkwNzY4NzQw"
}
}
- Price: $1.39 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 | youku | Platform identifier, fixed value. |
action | body | string | Yes | profile | Capability identifier, fixed value. |
user_id | body.params | string | Yes | - | The encoded creator UID required by the profile action, retrieved from video author metadata. Do not provide a username, show ID, or full channel homepage URL. |
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": "youku",
"action": "profile",
"params": {
"user_id": "UMzkwNzY4NzQw"
}
}'OpenAPI definition (JSON)Samples read the key from the EVERYINFRA_API_KEY environment variable; copied code never contains your key.
Response example
#{ "id": "req_…", "platform": "youku", "action": "profile", "results": { "user_id": "•••", "numeric_id": "•••", "name": "YKYX0728249", "url": "https://m.youku.com/profile?uid=UMzkwNzY4NzQw", "avatar_url": "https://static.youku.com/•••", "gender": 0, "like_count": 0, "is_verified": false, "platform": "youku" }, "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. |
numeric_id | Keeps the platform's own meaning |
name | Name of the object itself, for account, product and business capabilities. |
url | Link to the record on the platform. |
bio | Profile bio written by the account; may contain line breaks and emoji. |
avatar_url | Avatar image link. Some platforms return sized CDN links that can expire. |
gender | Keeps the platform's own meaning |
like_count | Likes. null means the platform or this capability does not disclose it; it is not 0. |
follower_count | Followers. null means not disclosed, not 0. |
is_verified | Whether the platform verified the account. null means it cannot be determined. |
verified_desc | Keeps the platform's own meaning |
location | Location description passed through as is; the format varies by platform. |
platform | Source platform identifier, the same as platform in the request (for example xiaohongshu, tiktok). |
FAQ
#Where do I find the encoded user_id?
#Read one of the creator's videos with the Youku Video details capability: the author details it returns include the creator's encoded UID, a string such as UMzkwNzY4NzQw. Pass that string alone; a full profile URL in this field does not work.
What is the difference between user_id and numeric_id?
#Both identify the same account. user_id is the encoded UID this capability takes as input, and numeric_id is the plain numeric form. Store both so you can match the account whichever form another source uses.
How do I read a creator's verification?
#is_verified says whether Youku verified the account; when it is null, the status is unknown rather than negative. verified_desc carries the verification note Youku shows, which helps tell official channels from personal accounts.
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.