Check whether a Kuaishou user is currently broadcasting · Kuaishou API
Check whether a Kuaishou user is currently broadcasting
curl https://api.unifapi.com/kuaishou/users/{user_id}/live-info \
-H "Authorization: Bearer $UNIFAPI_KEY"Path parameters
- user_id
- The public Kuaishou identifier shown in the endpoint path. Use the URL-visible slug or platform id described in the docs for this operation.
This operation is part of the Kuaishou API in the social platforms category. It uses the same Bearer token, request tracing, error model, and billing envelope as every UnifAPI endpoint, so agents can switch between platforms without custom per-vendor glue code.
Use it when a workflow needs Kuaishou public data but should still keep one API key, one account balance, and one predictable JSON contract across social, live public-data sources.
Common agent workflows
- Resolve a public Kuaishou identity into structured profile metadata for enrichment agents.
- Refresh creator, company, or account snapshots without managing upstream-specific response shapes.
- Give an AI agent a stable Kuaishou data source without building a per-platform integration.
- Normalize Kuaishou responses into the same UnifAPI envelope used across the catalog.
Unified envelope, platform-native fields
- Lookup responses return one canonical object in `data` with stable identifiers, source URLs where available, and platform-specific metadata normalized into predictable JSON.
- Successful responses include `request_id` for support/debugging and `billing` with credits charged, records charged, and remaining balance.
- A not-found or invalid-input condition uses the unified UnifAPI error shape, so callers do not need special handling for each upstream platform.
Billing
Every successful call costs at least one credit. List and search operations charge by billable records returned; single-object lookups charge one record when they succeed. Platform-caused failures can be refunded, and public responses include billing metadata with the credits charged and remaining workspace balance.
Errors and retries
Authentication, validation, rate-limit, not-found, and upstream errors use the unified UnifAPI error format. Agents should log `request_id`, retry only retryable failures, and treat invalid API keys, disabled keys, and expired keys as the same public `unauthorized` error type.
More Kuaishou operations
Combine endpoints from the same platform, then join the results with other UnifAPI categories without changing authentication or response parsing.
List Kuaishou hot-board categories
List Kuaishou hot-board categories
List Kuaishou trending personalities
List Kuaishou trending personalities
Search Kuaishou videos by keyword
Search Kuaishou videos by keyword
Get a Kuaishou user profile
Get a Kuaishou user profile