/blibli/sellers

POST /api/blibli/sellers

Price: 5 credits

Get a Blibli merchant (seller) by merchant code or merchant page URL: name, description, badge tier, ratings, review/comment counts, official-store flag, province, fulfillment metrics and logo.

How to use it

Fetch a single Blibli merchant (seller) by merchant code (e.g. SAO-60034) or merchant page URL. Returns one item with id, name, url, description, level, type, is_official, rating, review_count, comment_count, product_quality_rating, order_fulfillment_rating, respond_time_rating, badge (Diamond/Gold/etc), badge_rating, image, province, shipping_type, main_category_id, activation_date (unix ms), fulfilled_orders, order_fulfillment_duration, order_delivery_duration and response_time.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• seller string required — Blibli merchant code or a merchant page URL containing it (examples: "SAO-60034", "https://www.blibli.com/merchant/samsung-flagship-store/SAO-60034"; minLength: 1)

Response

• @type string (default: "BlibliSeller")
• id string required
• name string nullable
• url string nullable
• description string nullable
• level string nullable
• type string nullable
• is_official boolean nullable
• rating number nullable
• review_count integer nullable
• comment_count integer nullable
• product_quality_rating number nullable
• order_fulfillment_rating number nullable
• respond_time_rating number nullable
• badge string nullable
• badge_rating integer nullable
• image string nullable
• province string nullable
• shipping_type string nullable
• main_category_id string nullable
• activation_date integer nullable
• fulfilled_orders string nullable
• order_fulfillment_duration string nullable
• order_delivery_duration string nullable
• response_time string nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — Seller not found (well-formed but nonexistent merchant code) Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.