Kwai User Posts
Kwai user posts are public account publications with captions, author identity, attached media, hashtags, mentions, timestamps, and visible engagement counts. These content and context fields support account research, media-format review, and point-in-time engagement comparison.
Features
- Two supported identity inputsStart with either a username or a public profile URL on kwai.com or kwai-video.com; at least one identity field must be present.
- One-page public post collectionCollect the posts returned by one provider page for the selected public account without exposing a source cursor or a caller-supplied result limit.
- Normalized content and author contextReceive post text, public author fields, source URLs, media references, hashtags, mentions, publication time, and collection time in a consistent post shape.
- Visible engagement snapshotsKeep available like, comment, share, and view counts with collected_at so comparisons remain anchored to their observation time.
Parameters
| Parameters | Required | Description |
|---|---|---|
url | Required (at least one) | A non-empty Kwai profile reference whose parsed hostname is 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. Provide url or username; both may be supplied. |
username | Required (at least one) | A Kwai username with one optional leading @ followed by 1 to 64 ASCII letters, numbers, dots, underscores, or hyphens, for a maximum total length of 65 characters. The provider receives this value as handle. |
How to Use
Submit a supported Kwai identity, follow the asynchronous task, and page through the stored normalized results after completion.
- Prepare either a Kwai username or a public profile URL on kwai.com or kwai-video.com.
- POST url or username to /v1/kwai/user-posts, then store the returned task_id.
- Poll /v1/tasks/{task_id} until the task succeeds or reports a failure.
- Read data.results.items and use the task result next_cursor while has_more is true; this cursor pages stored results, not the Kwai source.
curl -X POST "https://api.socq.ai/v1/kwai/user-posts" \
-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 the stored-result next_cursor while has_more is trueBest Use Cases
- Public account content research: Review captions, author attribution, public media references, hashtags, mentions, and publication times from one selected account.
- Media-format review: Group returned posts by available media type, duration, thumbnail, and dimensions while retaining the source post and author.
- Point-in-time engagement comparison: Compare visible likes, comments, shares, and views across collected posts while using collected_at to identify the observation window.
Pro Tips
- Normalize usernames to the accepted optional-@ form before submission, and validate profile URL hosts against kwai.com or kwai-video.com.
- Do not add cursor or results_limit to the source request: each task asks the provider for one page using only the supported identity fields.
- Use GET /v1/tasks/{task_id} cursor and limit only after submission when paging stored task results; limit accepts 1 through 500 and defaults to 50.
- Treat text, author details, individual metrics, media, hashtags, mentions, and publication time as optional, and anchor snapshots with collected_at.
Related APIs
Use these APIs when you need a different type of public Kwai data.
- Kwai Profile API — Retrieve one public Kwai profile by username or supported URL with normalized identity, imagery, account flags, visible counts, and collection context.
- Kwai Post API — Resolve one known public Kwai post URL into normalized content, author, media, timestamps, entities, and visible engagement fields.