raw.cljx.star_searchCljx creator search
https://api.qovia.ai/v1/raw/cljx/star_searchSearch Kuaishou creators on the Cljx (磁力聚星) marketplace by name keyword, content category and sort order. Returns followers, expected plays, expected CPM, engagement and completion rates and quotes in CNY. Paged, up to 50 per page.
Typical uses: Tracking trends and topics, monitoring keywords and following competitors.
- Price
- $0.0015 / call$1.5 per 1k · fixed price
- Billing
- Charged only for successful, non-empty resultsthe charge is in meta.charged_usd
- Scope
raw:cljxThe API key needs this scope- Rate limit
- NoneNo per-account or per-endpoint request limit
Parameters
Only these parameters are accepted; any other one returns 400.
keywordCreator nickname keyword; leave out to browse by category and sort
Max 50 charsExample
美食tag_idTop-level content category ID, such as 673 food, 677 lifestyle, 695 comedy
Pattern^[0-9]{3}$sub_idsSecond-level category IDs, comma-separated; needs tag_id
Pattern^[0-9]{3}(,[0-9]{3}){0,19}$sort_bySort field: 3 default, 2 followers, 20 expected plays, 21 expected CPM, 22 engagement rate, 23 completion rate, 24 follower gain, 25 follower growth rate, 42 deeply connected users, 1 price; live creators also have 26 expected viewers, 27 peak concurrent viewers
Default3One of3 · 1 · 2 · 20 · 21 · 22 · 23 · 24 · 25 · 26 · 27 · 42sort_orderSort direction: 1 ascending, 2 descending; must be 0 when sort_by is 3 (default order), and 1 or 2 for any other sort_by
Default0One of0 · 1 · 2star_type1 short-video creators, 4 live-stream creators
Default1One of1 · 4pagePage number; the response's cursor is the next page
Default1Range1–50page_sizeItems per page
Default20Range1–50
- sub_ids requires tag_id
Combined constraints (JSON Schema)
{
"allOf": [
{
"if": {
"required": [
"sort_by"
],
"properties": {
"sort_by": {
"not": {
"const": 3
}
}
}
},
"then": {
"required": [
"sort_order"
],
"properties": {
"sort_order": {
"enum": [
1,
2
]
}
}
},
"else": {
"properties": {
"sort_order": {
"const": 0
}
}
}
}
]
}Response
A success is HTTP 200 with the shared envelope: request_id, data (this endpoint's data, see the example) and meta (the charge). An empty result is also 200, with meta.empty true, not charged, and data may be an empty structure or null.
Errors
| code | HTTP | Billing | Description |
|---|---|---|---|
scope_denied | 403 | Not charged | This API key lacks the scope the endpoint requires. |
endpoint_unavailable | 503 | Not charged | The endpoint is not available right now (no data source connected yet, or no price configured); nothing ran. |
invalid_params | 400 | Not charged | The parameters failed validation: a required one is missing, a type or format is wrong, an array has more items than allowed, an unknown one was sent, or the POST body is not a JSON object. An error in one parameter starts with its name (item_id: …); a missing or unknown parameter starts with params: …. |
insufficient_balance | 402 | Not charged | The balance cannot pay for this call; top up first. |
upstream_busyRetryable | 503 | Refunded | The data source is busy or cooling down; refunded. Retry after Retry-After. |
upstream_timeout | 504 | Refunded | The data source timed out; refunded. |
upstream_error | 502 / 503 | Refunded | The data source failed; refunded. |
upstream_rejected | 400 | Refunded | The data source rejected these parameters (well-formed, but not accepted); refunded. |
not_found | 404 | Refunded | The data source has no such item (deleted, or the ID does not exist); refunded. |
reservation_expired | 504 | Refunded | The call took too long and was refunded automatically; no data is returned. |
Any request can also fail authentication: 401 invalid_api_key, 403 account_disabled, 429 too_many_auth_failures.
Needs an account with a balance; playground calls are billed like API calls.