POST

API health

24h health
0%
  • Healthy / normal
  • Available
  • Limited
  • Mostly down
Mostly down

Last 24 hours

Last 30 days

Read buyer reviews of a Taobao product, up to 100 per call, and page through for more. Each review has rating, variant bought, helpful votes, photos, follow-up review and seller reply. Pass the item ID, a product link or share text with one product link. The batch may not include every review.

Send POST https://api.everyinfra.com/api/v1/social with platform set to taobao and action set to reviews. Price $5.56 per 1,000 requests ($0.005556 per call). Failed calls and empty results are not charged. Every 20 rows you ask for count as one call: limit sets the charge, and blocks that come back with no rows are not charged. Synchronous. For slow jobs add "mode": "async" to the body, take the job_id and poll.

Taobao Reviews reads buyer reviews for one product: the review text, rating, publish time, the variant purchased, the buyer's nickname, images, and the seller's reply. Use it to learn whether buyers are satisfied and where complaints cluster, for reputation analysis, tracing negative reviews to causes, or pulling selling points and pain points from a competitor's product.

url takes the same product identifiers as Product details: a numeric ID, a product link or share text with exactly one product link. sku ties each review to a specific variant, so you can compare feedback across colors or sizes, and seller_reply shows how the shop handles criticism. Check rating_scale on the same row before comparing ratings.

AI prompt

#
Please help me write a data collection script with the EveryInfra Taobao Reviews endpoint (taobao/reviews).

How the endpoint works:
- Request: POST https://api.everyinfra.com/api/v1/social with the header Authorization: Bearer <API key>. Read the key from the EVERYINFRA_API_KEY environment variable and never hard-code it.
- In the request body, set platform to taobao and action to reviews, and put the parameters inside params.
- Required parameters:
  - url: For product_detail, reviews, or questions, use a numeric item ID, a Taobao/Tmall product URL, or a share message containing exactly one product URL.
- Optional parameters:
  - page: Page number of the item's reviews, from 1 to 50, newest first, usually 20 reviews per page and fewer on the last. With page, you get that whole page directly and limit has no effect.
  - page_token: Page token. Leave it out for the first page. When the response has a next_page_token, pass it back as page_token, exactly as received, to get the next page, with the other parameters unchanged (limit can change).
  - limit: The most rows to return in this call, an integer from 1 to 100. The default applies when you leave it out, and a call can return fewer rows. Larger values return 422 before any charge. (default: 20)
- Returns a list of records. Main fields of each record: id, text, rating, rating_scale, posted_at, sku (Variant the buyer purchased (reviews),…), buy_count (How many times the reviewer bought the…), useful_count (How many times the review was marked us…), author_name, author_avatar_url (Reviewer avatar link (reviews)), images (Image links: product photos on product_…), review_append (Buyer's follow-up (appended) review text); 14 fields in total, full list at https://api.everyinfra.com/api/v1/social/catalog?platform=taobao.
- Example request body:
{
  "platform": "taobao",
  "action": "reviews",
  "params": {
    "url": "https://item.taobao.com/item.htm?id=744983869996"
  }
}
- Price: $5.56 per 1,000 requests; failed and empty results are not charged.
- For dozens or hundreds of targets, add "mode": "async" to the body: you get a job_id at once and poll GET https://api.everyinfra.com/api/v1/jobs/{job_id} for the result.
- On 422, fix the request using the suggested parameter names and allowed values in the error; on 429 or 503, wait for Retry-After and try again.

Before writing code, ask me which targets I need, how many, which fields, and what output format I want; then confirm the plan and the rough cost with me.

Request parameters

#
NameInTypeRequiredDefaultDescription
AuthorizationheaderstringYes-Bearer followed by your API key. Create it in the console; never put it in a URL or a code repository.
platformbodystringYestaobaoPlatform identifier, fixed value.
actionbodystringYesreviewsCapability identifier, fixed value.
urlbody.paramsstringYes-For product_detail, reviews, or questions, use a numeric item ID, a Taobao/Tmall product URL, or a share message containing exactly one product URL. e.tb.cn and m.tb.cn links work only when they can be safely resolved to a product page. TaoPassword-only tokens, expired links, and non-product pages are rejected.
pagebody.paramsintegerNo-Page number of the item's reviews, from 1 to 50, newest first, usually 20 reviews per page and fewer on the last. With page, you get that whole page directly and limit has no effect; without it, paging starts at page 1 as before and continues with next_page_token. Each page is billed as one call; a page past the last one returns an empty result and is not charged. Taobao shows at most the first 1,000 reviews of an item (page 50), so pages above 50 are rejected before charging. pagination.has_more true means there is a next page: ask for page + 1, or pass next_page_token back as page_token. When both page and page_token are sent, page_token wins. If new reviews arrive while you page, neighbouring pages can repeat a review or two, so dedupe by review id when merging.
page_tokenbody.paramsstringNo-Page token. Leave it out for the first page. When the response has a next_page_token, pass it back as page_token, exactly as received, to get the next page, with the other parameters unchanged (limit can change). You can also skip the token and ask for a page number with page; when both are sent, page_token wins. A token is valid for 24 hours and works only for the same product and the same account; a token used with another product is rejected with 422 and not charged. No next_page_token (or pagination.has_more false) means you have reached the end. Each page returns limit reviews (default 20, up to 100), and the next page continues after the last review returned. Reviews are newest first; if new reviews arrive while you page, neighbouring pages can repeat a review or two, so dedupe by review id when merging. Each page is billed on its own by its row count, one call per 20 rows (20 rows is one call, 21–40 is two, 100 is five); calls not used because fewer rows came back are refunded, and an empty page is not charged.
limitbody.paramsinteger (1–100)No20The most rows to return in this call, an integer from 1 to 100. The default applies when you leave it out, and a call can return fewer rows. Larger values return 422 before any charge.

Code samples

#
bash
curl -X POST 'https://api.everyinfra.com/api/v1/social' \
  -H "Authorization: Bearer $EVERYINFRA_API_KEY" \
  -H 'Content-Type: application/json' \
  --data-raw '{
  "platform": "taobao",
  "action": "reviews",
  "params": {
    "url": "https://item.taobao.com/item.htm?id=744983869996"
  }
}'

OpenAPI definition (JSON)Samples read the key from the EVERYINFRA_API_KEY environment variable; copied code never contains your key.

Response example

#
Captured September 26, 2026 at 08:56 (UTC) by calling this API with the parameters in the code sample above. results and count are that call's real response with personal information (names, handles, avatars, profile links, contact details) removed. id, billing and quota differ on every call, so only their shape is shown.
json
{  "id": "req_…",  "platform": "taobao",  "action": "reviews",  "results": [    {      "text": "質量過關,用着挺放心的,之前那個用了幾年時間,用不了,綠聯質量太好了",      "rating": 5,      "posted_at": "2026.08.27 21:28",      "platform": "taobao",      "rating_scale": 5    }  ],  "next_page_token": …,  "pagination": { … },  "count": 1,  "billing": {    "charged": …,    "charged_usd": …,    "balance_after_usd": …,    …  },  "quota": { … }}

Response fields

#

Business data is in results. The table lists the fields a record can contain; values the platform does not show are never made up.

FieldMeaning
idThe record's unique ID on the platform. Unique only within one platform; IDs can repeat across platforms.
textBody text with HTML removed, returned in full and never cut short (on a few platforms the list results themselves carry only an excerpt; the platform's field notes say so).
ratingRating. The scale varies by platform: rating_scale on the same row gives the maximum (usually 5; Booking, Douban, iQIYI and NAVER use 10). Convert with rating_scale before comparing across platforms, or the comparison can come out backwards.
rating_scaleMaximum of rating in the same row: 5 for five-star scales, 10 for ten-point scales. Present only when the row has a rating.
posted_atPublish time in ISO 8601, UTC (for example 2026-08-07T12:34:56+00:00). Non-standard strings from the platform are passed through as is, so parse defensively. null means the platform does not disclose it.
skuVariant the buyer purchased (reviews), such as color or size, as written on the review.
buy_countHow many times the reviewer bought the product, as shown on the review.
useful_countHow many times the review was marked useful.
author_nameAuthor's display name.
author_avatar_urlReviewer avatar link (reviews).
imagesImage links: product photos on product_detail, the buyer's photos on reviews (absent when the review has none).
review_appendBuyer's follow-up (appended) review text. Several follow-ups are joined with line breaks in posting order; the field is absent when there is none.
platformSource platform identifier, the same as platform in the request (for example xiaohongshu, tiktok).
next_page_tokenPage token: pass it back unchanged as page_token, with the other parameters the same, to fetch the next page; valid for 24 hours and only for the same product. Every row of a page carries the same value, which also appears at the top level of the response. Absent on the last page.
seller_replyThe seller's reply to the review; absent when there is none.

FAQ

#

Can I separate reviews by variant?

#

Yes. sku on each review is the variant the buyer purchased, so grouping by it compares feedback across colors, sizes or bundles. useful_count, the number of times a review was marked useful, helps you pick the most informative ones.

How do I see how a shop responds to complaints?

#

Read seller_reply, the seller's reply to that review. Reading low ratings next to the replies shows which problems keep coming up and how the shop usually deals with them.

Can I page through reviews or jump to a page, and how is it billed?

#

Yes, two ways. By page number: pass page (1–50) to get that page directly, usually 20 reviews; each page is one call and limit has no effect. By token: pass the response's next_page_token back unchanged as page_token; each page returns limit reviews (default 20, up to 100), billed one call per 20 reviews, and calls not used because fewer reviews came back are refunded. Either way, a next_page_token in the response means there is a next page, an empty page is not charged, and page_token wins when both are sent. Taobao shows at most the first 1,000 reviews of an item.

Errors and billing

#
401
Missing or invalid key.
402
Insufficient balance. Top up first.
422
Invalid parameter name or value. Fix it using the suggestions in the error. No charge.
429
Per-minute request limit reached. Wait for Retry-After, then try again.
503
Could not complete. The held charge is returned to your balance. If the outcome is unknown, verify it before you retry.
200 empty
No data. No charge.

Errors

Official references

#

Used only to check objects and terms. They do not imply authorization or endorsement of EveryInfra by the platform.

  • Taobao: Product ID and SKU Terminology ↗

    Taobao defines the product ID as the digits following id= in a product link, while an SKU describes specific attribute combinations such as color and size. Product IDs and SKUs must not be used interchangeably.

    Checked 2026-09-04

Google Analytics needs consent. Privacy