Kwai
GET /v1/kwai/profile

Kwai Profile API

Fetch Kwai profile — display name, bio, counts, and verification as structured JSON.

1 credit per request
TL;DR
Fetch Kwai profile — display name, bio, counts, and verification as structured JSON. The Kwai Profile API (Kwai) is a single authenticated GET request to /v1/kwai/profile that responds with clean JSON and costs 1 credit. Pass cache=true for a free 24h cache hit; default is always fresh. Start with 100 free credits — no credit card.

What is the Kwai Profile API?

Pass a Kwai profile URL or @handle and get the public account as clean JSON — one fixed key set on every profile: id (Kwai's opaque eid string — no twin eid key), username, displayName, bio, avatar, verified, verifiedDescription, gender, followers, following, likedCount, publicPostCount, privatePostCount, postCount (= public + private when both known), isPrivate. Sparse fields are null, never omitted (verifiedDescription / gender / privatePostCount included). No videoCount (Kwai posts are videos — structurally equal to postCount). No verifiedNumber (Kwai's verified_num is an undocumented enum; use verified + verifiedDescription). No redundant raw{}. Parsed from Kwai's public web page (JSON-LD + Nuxt SSR state). Note: Kwai's web surface sometimes stubs follower/following to 1; when that happens we prefer schema.org counts for followers and set following to null rather than ship a fake 1. Flat 1 credit.

What you get

  • verifiedDescription / gender / privatePostCount always present
  • postCount = public + private when both known
  • No eid twin, no videoCount, no verifiedNumber

Platform limits

Honest ceilings from the upstream platform surface — not Captapi bugs. Unexpected truncation here is usually the platform, not us.

  • publicPostCount can diverge from postCount when privatePostCount > 0; videoCount is never emitted (posts ≡ videos).
  • verifiedNumber is not exposed — Kwai's verified_num values beyond 0 (none) and 3 (Conta Oficial) are not documented upstream.

Try it

Open in Playground

Fill in the parameters below and copy a ready-to-run request, or open the live Playground to run it against your account (no API key paste).

Parameters

Sign in to run live
curl "https://api.captapi.com/v1/kwai/profile?url=https%3A%2F%2Fwww.kwai.com%2F%40KwaiBrasilOficial" \
  -H "Authorization: Bearer capt_live_..."
# or: -H "x-api-key: capt_live_..."

Edit the parameters and the code updates instantly. Switch languages and hit copy.

Example response

{
  "success": true,
  "data": {
    "platform": "kwai",
    "id": "3xyutri4afq3qks",
    "eid": "3xyutri4afq3qks",
    "url": "https://www.kwai.com/@KwaiBrasilOficial",
    "username": "KwaiBrasilOficial",
    "displayName": "Kwai Brasil Oficial",
    "bio": "Aqui, Geral Brilha ✨",
    "avatar": "https://aws-br-pic.kwai.net/bs2/overseaHead/20260729230605_BNTU4ODQzMDkz_s.jpg",
    "verified": true,
    "verifiedDescription": "Conta Oficial",
    "verifiedNumber": 3,
    "followers": 414136454,
    "likedCount": 17600139,
    "publicPostCount": 3707,
    "privatePostCount": 0,
    "postCount": 3707,
    "isPrivate": false,
    "videoCount": 3707
  }
}

Billing metadata is returned in response headers: X-Captapi-Credits (credits charged), X-Captapi-Cache (hit or miss), and X-Captapi-Source. Failed requests (4xx/5xx) are never charged. See the full list of error codes in the error reference.

Response structure

A successful call returns success, cached, creditsUsed, and a data object with the following fields:

Top-level fields

  • platformAlways "kwai" on this endpoint.
  • idKwai opaque profile eid (same value as eid).
  • eidKwai opaque profile eid.
  • urlCanonical URL of the item.
  • usernameAccount username / handle.
  • displayNameDisplay name of the account. Canonical across profile endpoints (prefer over name).
  • bioProfile bio when Kwai's public page exposes it.
  • avatarAvatar / profile picture URL. Canonical across profile endpoints.
  • verifiedWhether Kwai shows a verified badge on this profile.
  • verifiedDescriptionKwai verification label text when present (e.g. Conta Oficial).
  • verifiedNumberKwai verification tier number when present.
  • followersFollower count when Kwai exposes a non-stub value.
  • likedCountTotal likes received across the creator's posts.
  • publicPostCountPublic posts count.
  • privatePostCountPrivate posts count when Kwai exposes it.
  • postCountPublic post/video count (same as publicPostCount / videoCount).
  • isPrivateWhether the account is private.
  • videoCountAlias of postCount — public video/post count for cadence joins.

Parameters

NameTypeRequiredDescription
urlstringYesKwai profile URL or @handle, e.g. https://www.kwai.com/@topfilmeseseriesnatv. The URL platform must match this endpoint's platform. Do not pass cross-platform URLs, e.g. YouTube to TikTok, Instagram to Facebook, LinkedIn to X/Twitter, or Pinterest to Rumble.
cachebooleanNoSet true to serve from the 24h response cache (0 credits on hit). Default false — always fetch fresh. Envelope includes cached + cachedAt on hits.

Authentication: send your key as Authorization: Bearer capt_live_.... A typical call costs 1 credit. Pass cache=true for a free 24h cache hit; default is always fresh.

Using an AI agent? This endpoint is the MCP tool kwai_profile via @captapi/mcp. Set it up →

How it works

  1. 1. Sign up — get 100 free credits, no card required.
  2. 2. Create a key from your dashboard.
  3. 3. Send one request to /v1/kwai/profile and parse the JSON response.

Use cases

Profile Enrichment

Resolve a Kwai @handle to bio, avatar, verified, and follower/like/post counts.

Creator Verification

Confirm verified + verifiedDescription before outreach on Brazilian/Kwai audiences.

Competitive Analysis

Track followers, likedCount, and postCount over time for accounts you already follow.

Partnership Qualification

Vet Kwai creators with publicPostCount and audience size at 1 credit.

Frequently asked questions

What does the Kwai Profile API do?+

The Kwai Profile API lets you fetch profile or page details and audience stats from a public Kwai profile or page using one GET request to /v1/kwai/profile. It returns clean JSON — no OAuth or infrastructure setup required.

How many credits does the Kwai Profile API cost?+

Each successful call costs 1 credit. Pass cache=true to serve from the 24h cache (0 credits on hit); default is always fresh. Hits include cached + cachedAt. Selected profile endpoints also accept cacheMaxAge=1d|3d|7d|14d|30d. Failed or empty results are never charged.

Do I need a Kwai API key or OAuth?+

No. A single Captapi key works across every platform Captapi supports — YouTube, TikTok, Instagram, Facebook, Twitter/X, Reddit, Threads, Bluesky, Pinterest, LinkedIn, Rumble, Spotify, Kwai, and more. We handle proxies, rate limits, retries, and authentication for you.

Is the Kwai Profile API suitable for production use?+

Yes. It is a stable REST endpoint with predictable JSON and automatic retries. Pass cache=true to serve from the 24h cache (0 credits on hit); default is always fresh. Hits include cached + cachedAt. Selected profile endpoints also accept cacheMaxAge=1d|3d|7d|14d|30d. Use it for analytics, monitoring, and content automation.

More Kwai APIs

Ready to use the Kwai Profile API?

Sign up, grab your key, and make your first call in 60 seconds.