POST /api/ruten/sellers
Price: 1 credit
Get a Ruten seller's store: store name and intro, rating and rating counts, item and follower counts, order completion rates, response time, verification and seller badges
The account name is seller_name on ruten/items. Completion rates are shares from 0 to 1.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)seller string required — Ruten seller account name or store URL (examples: "smartmobile", "https://www.ruten.com.tw/store/smartmobile/")@type string (default: "RutenSeller")id string requiredalias string requiredurl string nullablestore_name string nullableintro string nullableimage string nullablebanner string nullablebackground_image string nullablerating number nullablestar_count integer nullablerating_count integer nullableforeign_rating_count integer nullableitem_count integer nullablefollower_count integer nullableresponse_time_hours integer nullableaverage_ship_days number nullableorder_count integer nullablecompletion_rate number nullablecompletion_rate_24h number nullablecompletion_rate_3_days number nullablecompletion_rate_7_days number nullablecompletion_rate_14_days number nullablecompletion_rate_21_days number nullablecompletion_rate_over_21_days number nullableorder_count_24h integer nullableorder_count_3_days integer nullableorder_count_7_days integer nullableorder_count_14_days integer nullableorder_count_21_days integer nullableorder_count_over_21_days integer nullablepi_level string nullableplatform string nullablegroups string nullablelast_active_at integer nullableis_phone_verified boolean nullableis_email_verified boolean nullableis_corporate boolean nullableis_overseas boolean nullableis_brand_seller boolean nullableis_ruten_choice_seller boolean nullableis_suspended boolean nullablehas_auctions boolean nullable422 — 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 — No Ruten seller under that account name 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.