kwai/
profile

The Kwai Profile API retrieves one public Kwai profile by username or supported profile URL with normalized identity, profile imagery, account flags, visible counts, and collection context.

Kwai Profile API

Username or profile URL
Normalized profile identity
Fixed 0.19-credit task
0.19 credits / request
Ready
Ready

Enter parameters and send a request. The task status and normalized results will appear here.

README

By SocQ · Updated

Kwai Profile

Kwai profiles are public account pages with usernames, display names, biographies, profile imagery, websites, account flags, and visible follower, following, and post counts. These identity details and point-in-time signals support profile enrichment, account comparison, and repeat snapshot monitoring.

Kwai Profile API Features

  • Two supported identifiersResolve one public profile from a valid username, a profile URL on kwai.com or kwai-video.com, or both identifiers in the same task.
  • Normalized public identityThe Kwai Profile API returns profile ID, source URL, username, display name, biography text, avatar, cover image, and website in a consistent account record.
  • Account signals with observation timeKeep available verification and privacy flags, visible follower, following, and post counts, and collected_at together as a point-in-time profile snapshot.

Kwai Profile API Parameters

ParametersRequiredDescription
usernameRequired (at least one)One of username or url is required. A username may start with @, followed by 1 to 64 ASCII letters, numbers, dots, underscores, or hyphens.
urlRequired (at least one)One of url or username is required. The non-empty reference must parse to a hostname of kwai.com, kwai-video.com, or a subdomain of either host. Any scheme is accepted when an authority and hostname are present; protocol-relative references are also accepted.

How to Use the Kwai Profile API

Submit one supported identifier to the Kwai Profile API, follow the asynchronous task, and read the normalized profile record from the stored result page.

  1. Prepare a valid username or a Kwai profile reference whose parsed hostname is kwai.com, kwai-video.com, or a subdomain of either host.
  2. Submit username, url, or both to /v1/kwai/profile and save the returned task_id.
  3. Poll /v1/tasks/{task_id} until the task succeeds or returns a failure.
  4. Read the profile in data.results.items and follow next_cursor only if has_more is true.
curl -X POST "https://api.socq.ai/v1/kwai/profile" \
  -H "Authorization: Bearer $SOCQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"url":"https://www.kwai.com/@ShortShortz8"}'

# Poll GET /v1/tasks/{task_id}
# Read data.results.items and follow next_cursor only while has_more is true

Kwai Profile API Use Cases

  • Profile record enrichment: Add normalized public identity, profile imagery, website, account flags, and source URL to a record linked to a known Kwai account.
  • Visible account comparison: Compare available follower, following, and post counts across selected profiles without treating the values as real-time totals.
  • Profile snapshot monitoring: Store repeat Kwai Profile API results with collected_at to track changes in public identity fields, account flags, and visible counts over time.

Kwai Profile API Pro Tips

  • Provide at least one identifier. When both username and url are present, the backend forwards both rather than selecting one on your behalf.
  • Validate usernames with ^@?[A-Za-z0-9._-]{1,64}$ and require the parsed URL hostname to be kwai.com, kwai-video.com, or a subdomain before submission.
  • Treat biography, avatar, cover image, website, account flags, and individual metrics as optional because a public profile may expose only part of the schema.
  • Use id as the primary deduplication key, fall back to url when needed, and keep collected_at beside every point-in-time metric snapshot.

Beyond the Kwai Profile API, use these APIs when you need a different type of public Kwai data.

  • Kwai User Posts API — Collect one page of public Kwai posts by username or supported profile URL with normalized content, authors, media, timestamps, hashtags, mentions, and visible engagement.
  • Kwai Post API — Resolve one known public Kwai post URL into normalized content, author, media, timestamps, entities, and visible engagement fields.

Explore other platforms

Combine Kwai data with public data from other supported social platforms.

Kwai Profile API — FAQ

Kwai Profile API is a programmatic interface for retrieving one public Kwai profile by supported username or profile URL. It returns normalized identity, profile imagery, account flags, visible counts, and collection context when available.

Submit username, url, or both. A username may have one leading @ followed by 1 to 64 ASCII letters, numbers, dots, underscores, or hyphens. A URL reference must parse to kwai.com, kwai-video.com, or a subdomain; any scheme with an authority and hostname, plus protocol-relative references, is accepted.

A result can include ID, source URL, username, display name, biography text, avatar, cover image, website, verification and privacy flags, visible follower, following, and post counts, and collection time.

No. One task resolves one profile and the request has no results_limit. The stored result reader still exposes items, next_cursor, and has_more using the common asynchronous result contract.

Each successful Kwai Profile API task costs a fixed 0.19 SocQ credits. The charge does not vary with the number of fields or result items.