Kwai APIs
Retrieve public Kwai profiles, one page of account posts, or one known post with normalized identity, content, media, timestamps, and visible engagement.
Available Kwai APIs
Use Profiles for account records, User Posts for one source page from an account, and Posts for one known public post URL.
What Kwai data can you retrieve?
SocQ preserves the public fields available for the selected resource without treating missing values as zero.
Profile identity
Retrieve available profile identity, imagery, websites, and public account flags.
Post content
Retrieve normalized post text, author context, publication time, hashtags, and mentions.
Media and metrics
Keep available media fields and visible account or engagement counts as point-in-time observations.
Kwai API contract overview
Each endpoint has a bounded source request and uses the common asynchronous task-result reader.
| Endpoint | Input | Source scope |
|---|---|---|
| Profiles | Username, supported profile URL, or both | One public profile |
| User Posts | Username, supported profile URL, or both | One returned source page |
| Posts | Supported public post URL | One public post |
How the Kwai APIs work
All three endpoints use the standard SocQ asynchronous task workflow.
1. Submit an identifier
Choose a Kwai endpoint, submit its supported username or URL input, and save task_id.
2. Track the task
Poll /v1/tasks/{task_id} until processing succeeds or fails.
3. Read stored results
Read data.results.items and follow next_cursor only when has_more is true.
Authenticate with a SocQ API key and submit a supported public identifier.
curl -X POST "https://api.socq.ai/v1/kwai/profile" \
-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.itemsCommon Kwai API use cases
Profile enrichment
Add public identity, imagery, account flags, source URLs, and visible account signals to known account records.
Content inventory
Build a bounded snapshot of public account posts or enrich a known public post URL.
Public signal monitoring
Store repeated results with collected_at to compare visible public fields over time.
Limits and public-data policy
Kwai results are point-in-time public records and do not provide publishing or account-management functions.
- Profiles and User Posts require at least one of username or url; both can be supplied together.
- Supported URLs use HTTP(S) on kwai.com, kwai-video.com, or a subdomain of either host.
- User Posts does not follow source pagination; task-result cursors only paginate records already stored by SocQ.
- Posts resolves one supported public post URL and does not accept results_limit.
- Each successful task has a fixed charge of 0.19 credits.
Kwai API frequently asked questions
What are the Kwai APIs?
The three Kwai APIs retrieve one public profile, one page of public account posts, or one known public post.
Can I submit a username and URL together?
Yes for Profiles and User Posts. Either field satisfies the requirement, and both are forwarded when supplied.
Which Kwai URL hosts are supported?
Use an HTTP or HTTPS URL on kwai.com, kwai-video.com, or a subdomain of either host.
Does User Posts follow source pagination?
No. It saves records from one returned source page; task-result cursors only read stored SocQ records.
How is Kwai collection priced?
Every successful Kwai task costs a fixed 0.19 SocQ credits.
Combine data across platforms for more complete business insights
Bring public profiles, content, and engagement data from different platforms into one workflow to track brands, creators, and topics and run cross-platform monitoring and analysis more efficiently.
Truth Social API
Retrieve public account details, collect one source page of account posts, or resolve one known post URL into normalized records.
Google Ad Library API
Discover public advertisers, collect creatives for a company, or retrieve one known Transparency Center creative by URL for research and review.
Google Maps API
Discover public places, retrieve normalized details for known Maps URLs, and collect public reviews with source-linked place and author context.
Amazon API
Search public Amazon products and collect normalized product details, Best Sellers, reviews, and seller-profile records from supported marketplaces.
Apple App Store API
Collect public Apple App Store app details, category rankings, and reviews from known store URLs as normalized app and review records.
SEO API
Query live Google organic results, compare keyword demand and ranking difficulty, expand seed terms, uncover the keywords and pages driving a site's search visibility, and classify search intent. Every endpoint uses the same SocQ API key, asynchronous task flow, and normalized result format.