Kwai API

Scrape Kwai data with one API

Name: Kwai Data API
Brand: SocialCrawl
Availability: InStock

Fetch public Kwai data as structured JSON with one SocialCrawl API key. Same Post, Comment, and Author schema as every other platform. Reads are priced in credits.

Read the docs How it works Try live

/v1/kwai

3 active endpoints

GET /v1/kwai/profile
GET /v1/kwai/user/posts
GET /v1/kwai/post

What Kwai endpoints does SocialCrawl ship?

3 live read endpoints for public Kwai data. Profiles, user posts, and single posts. Data API only.

Profile

1 credit

/v1/kwai/profile

Get a Kwai user profile.

handle, url

User posts

1 credit

/v1/kwai/user/posts

List a Kwai user's posts.

handle, url, cursor, count

Post

1 credit

/v1/kwai/post

Get a Kwai post.

url

Kwai API3 endpoints supported

View docs

Returns a Kwai account's public profile: username, bio, avatar, verification status, and follower, following, like, and post counts.

Use it for a snapshot of an account by handle or profile URL, before pulling what it has posted with user/posts.

1 credit

GET/v1/kwai/profile?handle=KwaiBrasilOficial

handleurl

$ curl https://www.socialcrawl.dev/v1/kwai/profile?handle=KwaiBrasilOficial \
    -H "x-api-key: sc_YOUR_API_KEY"

idle

// Running this live needs your own API key. Hit "Try it" to see an example response

How the Kwai API works

Kwai is a normal SocialCrawl social surface. You call GET /v1/kwai/… with an API key, spend credits on live misses, and get a single JSON envelope back. No second SDK.

Authenticate every call

Send your key in the x-api-key header. The same key works across the SocialCrawl catalog.

GET with query params

Routes are GET. Pass handles, urls, queries, and cursors as query strings. We validate formats before charging.

Pay in credits, not seats

Live misses debit the route tier. Cache hits cost 0. Empty or hard failures refund.

Read one JSON envelope

Every response is the same shape: success, data, credits_used, credits_remaining, request_id, cached.

The usual integration chain

Most products resolve an account, page content, then deepen only the posts that matter.

01Account

GET /v1/kwai/profile

Author-shaped profile

Resolve the handle or id once.

02Feed

GET /v1/kwai/user/posts

PostList of recent public items

Page with cursor or after when the route supports it.

03Item

GET /v1/kwai/post

Full Post for one URL or id

List rows are not enough when you need the full record.

04Comments

GET /v1/kwai/post

CommentList when the platform exposes it

Expand only when a thread matters.

request

GET /v1/kwai/profile
  ?handle=KwaiBrasilOficial
Host: www.socialcrawl.dev
x-api-key: sc_your_api_key_here

response envelope

{
  "success": true,
  "data": { "/* Author | Post | PostList | CommentList | … */": true },
  "credits_used": 1,
  "credits_remaining": 9999,
  "request_id": "req_…",
  "cached": false
}

What lands in data

Field names match the rest of SocialCrawl where archetypes align.

Authorprofile

id, username, display_name, avatar_url, bio, followers, url, ext

PostList / Postuser/posts

items[].post with id, url, content, engagement, author, published_at, ext

CommentListpost

items[] with author, content.text, engagement, published_at when comments ship

Search / Mediapost

search hits, media metadata, or transcripts depending on route

Inside the gateway

Same request lifecycle as every other /v1 platform endpoint.

Edge receives the call

Next.js catch-all routes into the Hono social API. We mint a request_id, authenticate the key, then enforce rate limit and concurrency.

Validate, then debit

Registry lookup finds the route. Required params run first. Invalid input returns 400 with no charge. Valid calls debit before upstream work.

Cache or fetch

A deterministic cache key is built from platform + resource + params. Hit: credits_used = 0. Miss: upstream fetch with retries and circuit breaker.

Normalize and return

Upstream JSON is mapped to Author / Post / PostList / CommentList (or route archetype), validated, wrapped in the success envelope, and logged for billing audit.

Billing rules that matter in production

Standard live miss: tier cost (often 1 credit)
Advanced reads: typically 5 credits
Premium reads: typically 10 credits
Metered routes: min floor when documented
Cache hit: 0 credits
Empty / hard fail: auto-refund
Bad params: 400, never charged
No credits: 402, never charged
Disabled routes: 503, never charged

How we get the data

Kwai is public-read data on SocialCrawl. We normalize it into the shared schema so your code does not learn a second OAuth flow.

What Kwai is for this API

Public Kwai surfaces exposed by the registry. Read-only for research, monitoring, and product jobs.

How SocialCrawl reaches it

Social-read upstreams behind one gateway. Prism composites combine legs when a fat route is registered.

What leaves our edge

Unified JSON envelope: success, data, credits_used, request_id, cached. Shared Author / Post / Comment leaves where archetypes align.

What we do not ship live

No write endpoints and no private inbox. Disabled routes stay out of the active count. Prefer registry docs for the live inventory.

field map sketch

public profile / channel→ author.*profile identity and counters

public post / media→ post.* / items[].postpost content and engagement

list / search page→ items[] or hitscomments or search hits when present

What this API is used for

The jobs this API is most often used for.

3active Kwai endpoints in the registry

1 / 5 / 10credit ladder across standard, advanced, premium

Kwai monitoring and content intelligence

Callers concentrate on profile, content lists, search, and deepen paths on Kwai. Structured Kwai JSON on the shared schema with one SocialCrawl API key.

Detail reads are typically a few seconds on live miss. Search and fat composites are slower paths.

Use case examples

Common ways teams put this data to work, and the stack each one tends to run.

Monitoring jobs

Python, cron, Slack bots

Poll profiles and feeds on Kwai. Alert when engagement velocity jumps.

Research and VoC

Node, notebooks, BI loads

Search and expand posts for brand, product, and competitor language on Kwai.

Backend product jobs

Go, workers, Explorer

Wire resolve to list to detail into pipelines. Cache hits keep recurring runs cheap.

Call it in two lines

Live misses spend credits by tier. Cache hits are free. Empty or hard failures refund.

curl "https://www.socialcrawl.dev/v1/kwai/profile?handle=KwaiBrasilOficial" \
  -H "x-api-key: sc_your_api_key_here"

curl "https://www.socialcrawl.dev/v1/kwai/user/posts?handle=KwaiBrasilOficial" \
  -H "x-api-key: sc_your_api_key_here"

Kwai on SocialCrawl

Same key as the rest of the catalog

Platform docs Get an API key

Endpoints

What data does the Kwai API return?

Every endpoint returns structured JSON in a unified envelope. Computed fields such as engagement rate and content category are included only where the endpoint supports them and the required source inputs are present.

ProfileGet a Kwai user profile User PostsList a Kwai user's posts PostGet a Kwai post

Comparison

How does SocialCrawl compare to DIY scraping for Kwai data?

Same Kwai data, two very different paths. Auth, rate limits, schema, and cost, side by side.

Feature	SocialCrawl	DIY scraping
Setup	Sign up and send one GET request	Reverse-engineer kwai.com, then build proxies and parsers
Authentication	One x-api-key header	None: you manage IP rotation and bot detection yourself
Response schema	Unified JSON, same shape as TikTok and Instagram	Raw HTML or private JSON you normalize yourself
Pricing	1 credit per request; 100 free credits on signup	Proxy, server, and engineering costs that scale with volume
Data coverage	Profiles, paginated post feeds, and video details	Whatever your scraper can reach before it breaks
Maintenance	SocialCrawl absorbs Kwai frontend changes upstream	Every Kwai update can silently break your pipeline

Setup

SocialCrawl

DIY scraping

Reverse-engineer kwai.com, then build proxies and parsers

Authentication

SocialCrawl

One x-api-key header

DIY scraping

None: you manage IP rotation and bot detection yourself

Response schema

SocialCrawl

Unified JSON, same shape as TikTok and Instagram

DIY scraping

Raw HTML or private JSON you normalize yourself

Pricing

SocialCrawl

1 credit per request; 100 free credits on signup

DIY scraping

Proxy, server, and engineering costs that scale with volume

Data coverage

SocialCrawl

Profiles, paginated post feeds, and video details

DIY scraping

Whatever your scraper can reach before it breaks

Maintenance

SocialCrawl

SocialCrawl absorbs Kwai frontend changes upstream

DIY scraping

Every Kwai update can silently break your pipeline

FAQ

Have a question? We got answers

Find answers to frequently asked questions about SocialCrawl's API, pricing, and capabilities.

How do I scrape Kwai data with an API?

SocialCrawl exposes 3 Kwai endpoints: profile, user posts, and post details. Send a GET request with your x-api-key and a handle (KwaiBrasilOficial) or a kwai.com URL; you get normalized JSON back in the same unified schema SocialCrawl uses for TikTok and Instagram.

What is Kwai and why does it matter for data teams?

Kwai is Kuaishou's international short-video app and the #1 short-video platform in Brazil and much of Latin America. If your social coverage stops at TikTok, you are blind to a market of hundreds of millions of LatAm users. Kwai endpoints close that gap with the schema you already parse.

What Kwai endpoints does SocialCrawl offer?

3 endpoints: Profile, User Posts, and Post. All return the unified SocialCrawl schema.

Does Kwai have an official public data API?

No. Kwai offers no public read API for profiles or videos. Data teams normally resort to fragile scrapers. SocialCrawl wraps Kwai behind the same plain REST surface as all 65 platforms: one x-api-key header, standard GET requests, one response envelope.

Is there a Kwai data API?

Yes. SocialCrawl is the Kwai data API: 3 endpoints for creator profiles, paginated post feeds, and single-video details, all returned in the same unified JSON schema SocialCrawl uses for TikTok. There is no official public Kwai data API for reading arbitrary public profiles or videos, which normally leaves teams maintaining brittle scrapers. SocialCrawl covers Kwai on one x-api-key at 1 credit per request, with 100 free credits on signup and no card.

How much does the Kwai API cost?

Each Kwai request costs 1 credit on the standard tier. New accounts get 100 free credits with no credit card required, enough to test all 3 endpoints against real Brazilian creator accounts before you pay anything.

Is scraping Kwai data legal?

SocialCrawl reads only publicly visible Kwai data: public profiles, public videos, and their public engagement counts. You are responsible for complying with Kwai's Terms of Service and applicable data protection law, including Brazil's LGPD if you process Brazilian users' data. SocialCrawl operates under a documented GDPR legitimate-interest framework: public, logged-out data only, no credential use, short-lived caches (2 to 30 minutes) with no persistent store, and a public opt-out channel for anyone whose public info appears in responses. Full details: socialcrawl.dev/legal/public-data-notice.

What is the best Kwai scraper API?

SocialCrawl is the most practical Kwai scraper API: 3 endpoints covering profiles, paginated post feeds, and video details at 1 credit per request, with 100 free credits and no card. Kwai has no official read API, and DIY scrapers break with every frontend update. SocialCrawl returns the same unified schema as TikTok.

Ask AI about SocialCrawl

Ask ChatGPT Ask Perplexity Ask Gemini Ask Claude Ask Grok

Read the Kwai API reference in the docs

🤖 AI agent or LLM? Read this page as markdown