Taobao & Tmall · Product search
Beta
Public data from social platforms, billed per call, on the same API key and balance as your model calls.
Unpaid accounts: up to 50 calls per day. Paid accounts: no daily call limit. Resets at 00:00 UTC. · A call is charged only when it returns HTTP 200 with a non-empty data; empty results, rejected parameters and upstream failures are free.
Request parameters
Parameters go in the query string under the platform's own names. Examples come from the catalog; replace identifiers with the content you want to retrieve.
| Name | Type | Required | Example | Description |
|---|---|---|---|---|
keyword | string | Yes | "保温杯" | Search keyword. Results are normalized product records, not the raw platform response. |
limit | integer | No | 5 | Maximum records returned per call: 5. Price covers this single bounded batch; larger requests are rejected before dispatch. Default 5 |
Request example
curl --get "https://api.chinaapi.ai/v1/social/taobao/product-search" \
-H "Authorization: Bearer $CHINAAPI_KEY" \
--data-urlencode 'keyword=保温杯'Response shape
A successful response returns this endpoint’s data inside data. It may be raw platform data or a normalized object/array. Check the endpoint schema and the catalog’s data_type, when present. Send paging tokens unchanged to the same endpoint.
{
"object": "social.result",
"platform": "taobao",
"capability": "product-search",
"data": { … }
}Pagination
This endpoint has no paging parameters.
Errors and what is not charged
| Status Code | Error code | Meaning |
|---|---|---|
| 400 | — | A parameter is unknown, repeated, too long, of the wrong type or missing, including when no member of an "at least one of" group is given. The error code says which, such as unknown_parameter or missing_parameter. |
| 403 | — | The API key does not have permission for this request. |
| 404 | social_data_no_result | The platform and capability pair does not exist, or the platform found nothing for these parameters (social_data_no_result). |
| 429 | data_api_daily_limit_exceededsocial_data_capacity_reached | The beta's capacity for the day is used up and resets at 00:00 UTC, or the platform is busy and a retry a few seconds later will do. Do not retry in a tight loop. Unpaid accounts: up to 50 calls per day. Paid accounts: no daily call limit. Resets at 00:00 UTC. |
| 502 | social_data_no_result | The data source did not answer, or answered without data. |
| 503 | social_data_unavailable | This endpoint is paused right now; the live catalog lists it as paused. |
None of these responses is charged.
Every response carries an X-Oneapi-Request-Id header; include it when you contact support and we can find that exact call.
Beta terms
Unpaid accounts: up to 50 calls per day. Paid accounts: no daily call limit. Resets at 00:00 UTC. The beta has no SLA, and its platforms, endpoints and prices may change.
Follow each platform's terms and the data-protection rules that apply to you. Do not use this API to build profiles of individuals. Logging in, extracting contact details, manipulating engagement and reaching private or paid content are outside this beta.
Data API rate benefits
Data API rate benefits
Paid accounts start at 10 requests/second and automatically increase with cumulative net spending, up to 100 requests/second.
Unpaid accounts: up to 50 calls per day. Paid accounts: no daily call limit. Resets at 00:00 UTC.
| Cumulative net spending | Requests per second |
|---|---|
| Paid default | 10/s |
| Over USD 50 | 20/s |
| Over USD 500 | 50/s |
| Over USD 1500 | 100/s |
Spending basis: settled Data API charges minus API refunds. Top-ups and model API spending do not count.
All API keys in an account share this rate. It measures requests per second, not simultaneous requests.
Supplier endpoints have separate capacity limits that also affect the available throughput.