# Kwai User Posts API (https://www.socialcrawl.dev/platforms/kwai/user-posts)

> Returns a paginated list of public Kwai posts for a user: captions, media URLs, covers, engagement counts, and author info. Forward the returned `cursor` for the next page. Pass either `handle` or `url`.

TL;DR: `GET /v1/kwai/user/posts` costs 1 credit per call and returns SocialCrawl's unified JSON schema. Single x-api-key auth, 100 free credits on signup.

## Parameters

| Parameter | Required | Description |
| --- | --- | --- |
| `handle` | no | Kwai profile handle (without the @) |
| `url` | no | Kwai profile URL |
| `cursor` | no | Cursor from the previous response for the next page |
| `count` | no | Number of posts to return (max 50) |
| `since` | no | Only rows published on or after this date: YYYY-MM-DD (midnight UTC) or an ISO 8601 timestamp. Rows older than it are left off each page. This list is not in date order, so the walk does not stop at the date: keep following `next_cursor`, and each page costs what a page costs even when every row on it is filtered out. A row with no date is kept. `published_after`, `start_date`, `from_date`, `publish_time` (`yesterday`, `this-week`, `this-month`, `last-3-months`, `last-6-months`) and `max_age_days` are accepted and applied as `since`. |
| `until` | no | Only rows published on or before this date: YYYY-MM-DD (that whole UTC day is included) or an ISO 8601 timestamp. Newer rows are left off each page and the walk does not stop, so older pages follow. A row with no date is kept. `published_before`, `end_date` and `to_date` are accepted and applied as `until`. |
| `max_pages` | no | 1 to 50 (default 1, or 50 when `max_items` or `max_credits` is sent). Walk up to this many pages in one call and return the rows from all of them. Each page walked is billed exactly as one call to this endpoint (a cached page is free) and counts against your rate limit; its charge and any refund are recorded under the page's own request id, listed in `data.walk.request_ids`. The walk stops early at the last page, or when the request's time budget runs low; `data.walk.stopped` says why (`end`, `max_pages`, `max_items`, `max_credits`, `time_budget`, `page_error`) and `pagination.next_cursor` continues from where it stopped. |
| `max_items` | no | 1 to 5000. Get more in one call: keep walking pages until the response holds at least this many rows, then stop with `data.walk.stopped: "max_items"`. The last page is returned whole (it was billed), so `data.items` can hold up to one page more than this, and `pagination.next_cursor` resumes right after it without skipping a row. Walks up to 50 pages unless `max_pages` says fewer; each page is billed as one call (a cached page is free). Add `max_credits` to cap the spend. A long walk can stop on the time budget first (`"time_budget"`): send the returned cursor with the same params to continue. |
| `max_credits` | no | 1 to 100000. The most this call may spend, across every page it walks. A page starts only while the credits already spent plus that page's price (or, when higher, the most any page of this walk has cost) still fit, so the call never goes past it; the walk then stops with `data.walk.stopped: "max_credits"` and the cursor to resume. Sent alone, it walks as far as the budget goes (up to 50 pages). A value below the price of one page is a free 400 whose `error.details.page_credits` names that price. Credits a row join (`include=`) adds are known only once a page has run, so page 1 is checked against its own price. |

## Code example

```bash
curl -G "https://www.socialcrawl.dev/v1/kwai/user/posts" \
  --data-urlencode "handle=KwaiBrasilOficial" \
  -H "x-api-key: sc_YOUR_API_KEY"
```

## FAQ

### How do I list a Kwai user's posts with an API?

Send a GET request to /v1/kwai/user/posts with either a handle (KwaiBrasilOficial) or a profile URL. SocialCrawl returns the user's video feed: captions, media URLs, cover images, engagement counts, and author info, in one normalized JSON response.

### What fields does the Kwai User Posts API return?

Each post includes its caption, video and cover URLs, view/like/comment/share counts, timestamps, and author info, normalized into the unified PostList schema shared with TikTok and Instagram, so the same parsing code handles all three platforms.

### How does pagination work on the Kwai feed?

The response includes a cursor. Forward it as the cursor parameter on your next request to get the following page, and use count to control page size (up to 50 posts per call). Repeat until the cursor runs out to archive a full account.

### How much does the Kwai User Posts API cost?

Each request costs 1 credit on the standard tier. A 50-post page costs the same as a single-post page, so set count high when archiving. New accounts get 100 free credits with no credit card required.

### Can I use this for brand monitoring in Brazil and LatAm?

Yes. Pull a brand's or creator's Kwai feed on a schedule, rank posts by views or likes, and feed the results into the same dashboard you already run for TikTok. The unified schema means zero extra parsing work for the LatAm market.

See the full Kwai API: https://www.socialcrawl.dev/platforms/kwai

## Pricing

- Standard endpoints: 1 credit per call
- Advanced endpoints: 5 credits per call
- Premium endpoints: 10 credits per call
- 100 free credits on signup, no credit card required. Cached responses cost 0 credits. Credit packs never expire.
- Full pricing: https://www.socialcrawl.dev/pricing

## Explore with AI

Questions this API answers, phrased for an AI assistant:

- How to list a Kwai user's videos with the SocialCrawl API
- What does the SocialCrawl Kwai User Posts API return?