raw.xiaohongshu.kol_core_dataXiaohongshu creator core data (Pugongying)
https://api.qovia.ai/v1/raw/xiaohongshu/kol_core_dataPugongying core data for a creator over 30 or 90 days: impressions, reads and engagements in total and per day, with CPM, CPV (per read), CPE (per engagement) and CPUV in CNY. Empty results are free.
- Price
- $0.01 / call$10 per 1k · fixed price
- Billing
- Charged only for successful, non-empty resultsno free quota
- Scope
raw:xiaohongshuThe API key needs this scope- Rate cap
- 3 req/s globalAcross all users, plus your per-minute limit
Parameters
Only these parameters are accepted; any other one returns 400.
user_idCreator user ID (24 hex characters)
Pattern^[0-9a-f]{24}$Example
5f4efa82000000000100717edate_typePeriod: 1 last 30 days, 2 last 90 days
Default1One of1 · 2note_typeNote type: 1 image posts, 2 videos, 3 all
Default3One of1 · 2 · 3ad_switchTraffic: 1 all traffic, 0 organic only
Default1One of0 · 1businessNotes: 0 regular notes, 1 sponsored notes
Default0One of0 · 1
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 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: …. |
rate_limitedRetryable | 429 | Not charged | Over the account's per-minute limit (sliding 60-second window); wait for Retry-After. |
too_many_unbilledRetryable | 429 | Not charged | In the last 10 minutes at least 50 of your calls to data sources, and over 80% of them, came back empty, not found or rejected; slow down. |
endpoint_busyRetryable | 429 | Not charged | The endpoint's per-second capacity across all users is full; retry in 1 second. This does not count toward your per-minute limit. |
insufficient_balance | 402 | Not charged | The balance cannot pay for this call (the free quota is used up, or the endpoint does not use it). |
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; playground calls are billed like API calls.