# Kwai (/docs/kwai) Kwai profiles, user feeds, and single post detail. Short-form video coverage for Brazil, Latin America and Southeast Asia Kwai is Kuaishou's international short-video app, and it is where a large share of Brazilian, Latin American and Southeast Asian short-form creators publish, audiences that barely register on TikTok's international index. Three endpoints cover it, all 1 credit. Base URL: `/v1/kwai/...` Kwai post URLs take the form `kwai.com/@{handle}/photo/{id}` **for videos as well as photos**. Do not filter on the `/photo/` path segment to detect media type. ## Quickstart ### 1. Fetch a profile ```bash title="cURL" curl "https://www.socialcrawl.dev/v1/kwai/profile?handle=KwaiBrasilOficial" \ -H "x-api-key: YOUR_API_KEY" ``` ### 2. Fetch their content ```bash title="cURL" curl "https://www.socialcrawl.dev/v1/kwai/user/posts?handle=KwaiBrasilOficial&count=50" \ -H "x-api-key: YOUR_API_KEY" ``` ### 3. Read computed fields When an endpoint supports a computed field and the required source inputs are present, the unified response includes that optional field. Depending on the endpoint, optional fields can include `engagement_rate`, `language`, `content_category`, and `estimated_reach`. See [Computed fields](/docs/computed-fields.md) for formulas, clamping rules, and null semantics. ## Accounts and posts | Endpoint | Credits | What it returns | Key parameters | | ------------------------- | ------- | ---------------------------------------------------------------------------------- | --------------------------------------------- | | `GET /v1/kwai/profile` | 1 | Username, bio, avatar, verification, and follower, following, like and post counts | `handle` or `url` | | `GET /v1/kwai/user/posts` | 1 | A page of public posts: caption, video and cover URLs, engagement counts, author | `handle` or `url`, `count` (max 50), `cursor` | | `GET /v1/kwai/post` | 1 | One video in full, including **the music track used** | `url` | Accounts are addressable by `handle` without the `@` or by profile `url`. One of the two is required, and sending neither is a `400` before billing. `user/posts` is the endpoint to walk when you are building a creator's history: the response carries a `cursor` to pass back for the next page. The music track is the reason to reach for `post` over a feed row when you are tracking a sound. ```bash title="cURL" curl "https://www.socialcrawl.dev/v1/kwai/post?url=https://www.kwai.com/@KwaiBrasilOficial/photo/5193363430624671876" \ -H "x-api-key: YOUR_API_KEY" ``` ## All endpoints ## Platform notes **Post URLs say `/photo/` even for videos.** A Kwai post URL takes the form `kwai.com/@{handle}/photo/{id}` regardless of media type, so do not filter on the path segment. **There is no keyword search and no comment endpoint here.** Discovery and comment threads are not covered on this platform. Start from a handle or a URL you already have. For cross-platform keyword discovery, [`/v1/search/everywhere`](/docs/search/everywhere.md) is the right call. **Regional coverage is the point.** If you are researching a Brazilian or Southeast Asian creator and TikTok's index looks thin, checking Kwai for the same handle is usually worth one credit. **Only `user/posts` paginates,** and it does so with the universal `cursor`. ## Next steps - [Pagination](/docs/pagination.md): Cursor and page walks, and what has_more actually means. - [Credits](/docs/credits.md): What each tier costs and when a call is refunded. - [API reference](/docs/api-reference.md): Every parameter and response field, endpoint by endpoint. - [TikTok](/docs/tiktok.md): The short-form surface to check the same creator against. - [Universal search](/docs/search/everywhere.md): Keyword discovery across sources, where Kwai has none of its own.