kwai/
user-posts

Use the Kwai User Posts API to collect one page of public Kwai posts from a username or supported profile URL, returning text, author, media, hashtags, timestamps, and visible engagement as normalized records.

Kwai User Posts API

Username or profile URL
One source page
Normalized public posts
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 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.

Kwai User Posts API 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 contextEvery Kwai User Posts API record carries 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.

Kwai User Posts API Parameters

ParametersRequiredDescription
urlRequired (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.
usernameRequired (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 the Kwai User Posts API

Submit a supported Kwai identity to the Kwai User Posts API, follow the asynchronous task, and page through the stored normalized results after completion.

  1. Prepare either a Kwai username or a public profile URL on kwai.com or kwai-video.com.
  2. POST url or username to /v1/kwai/user-posts, then store the returned task_id.
  3. Poll /v1/tasks/{task_id} until the task succeeds or reports a failure.
  4. 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 true

Kwai User Posts API 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.

Kwai User Posts API 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.

Beyond the Kwai User Posts API, 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.

Explore other platforms

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

Kwai User Posts API — FAQ

Kwai User Posts API collects one page of public post records from a Kwai username or supported profile URL. It returns normalized content, author context, media, timestamps, hashtags, mentions, and visible engagement when those public fields are available.

Provide at least one of url or username. A username may begin with @ and use letters, numbers, dots, underscores, or hyphens; a URL must use kwai.com, kwai-video.com, or a subdomain of either host.

No. The submission contract has no results_limit or source cursor and makes one provider request. The cursor on GET /v1/tasks/{task_id} only pages results already stored for the completed task.

A post can include its ID and URL, text, public author identity, visible like, comment, share, and view counts, media, hashtags, mentions, published_at, and collected_at. Optional source fields can be null or empty.

Each successful task costs a fixed 0.19 SocQ credits. The charge does not change with the number of post records returned by that one-page request.