Kwai Post
Kwai posts are public content records that can pair text and media with author identity, hashtags, mentions, publication time, and visible engagement. These fields support URL catalog enrichment, content review, and point-in-time comparison of selected posts.
Features
- Single known-URL lookupResolve one public URL on kwai.com, kwai-video.com, or their subdomains without adding an unverified path rule.
- Post and author contextReturn post identity, source URL, text, publication time, and available author ID, username, display name, profile URL, avatar, and account flags.
- Media and content entitiesKeep available media references, previews, dimensions, duration, hashtags, and mentions alongside the post record.
- Visible engagement snapshotNormalize available like, comment, share, and view counts with collected_at so the record has a clear observation time.
Parameters
| Parameters | Required | Description |
|---|---|---|
url | Required | Required non-empty URL with a parseable kwai.com or kwai-video.com hostname, including supported subdomains. The runtime does not require a particular path pattern. |
How to Use
Submit one accepted Kwai URL, track the asynchronous task, and read the normalized post record after completion.
- Confirm that the URL includes a parseable hostname on kwai.com, kwai-video.com, or an accepted subdomain.
- POST the url string to /v1/kwai/post and save the returned task_id.
- Poll /v1/tasks/{task_id} until the task succeeds or fails.
- Read data.results.items after success. The detail provider can save at most one post, so has_more should normally be false even though the task-results route exposes next_cursor.
curl -X POST "https://api.socq.ai/v1/kwai/post" \
-H "Authorization: Bearer $SOCQ_API_KEY" \
-H "Content-Type: application/json" \
-d '{"url":"https://www.kwai.com/@ShortShortz8/photo/5235021727595785285"}'
# Poll GET /v1/tasks/{task_id}
# Read the normalized post from data.results.itemsBest Use Cases
- Enrich a known-post catalog: Replace a stored Kwai link with normalized post ID, text, author identity, publication time, and source fields.
- Review selected post content: Use text, media references, hashtags, mentions, and author context to inspect an approved set of individual posts.
- Compare engagement snapshots: Repeat lookups at defined times and pair visible like, comment, share, and view counts with collected_at for point-in-time comparison.
Pro Tips
- Include a URL scheme so the hostname can be parsed, and use the exact public post link rather than a bare account name.
- Submit one URL per task because this detail endpoint accepts a single url field and has no results_limit or batch input.
- Preserve the submitted URL when a successful task returns no item, since an accepted hostname does not guarantee that the provider can resolve the resource.
- Store optional author, media, entity, and engagement fields defensively because a public post may not expose every normalized field.
- Use collected_at with every metric comparison and do not treat visible counters as a live feed.
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 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.