/street11/sellers

POST /api/street11/sellers

Price: 5 credits

Get an 11Street seller (store) by store id or store URL: store name, business name, representative, performance grades and store likes.

How to use it

Fetch a single 11Street (11번가) seller (store) by numeric store id or a store URL (shop.11st.co.kr/stores/{id}). Returns one item with id, name (store name), url, like_count (store favorites), business_name (legal entity), representative, business_type, positive_review_rate, response_rate (24h Q&A response), sales_grade (1-5), order_fulfillment_rate and shipping_on_time_rate (all percentages). Content is Korean.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• seller string required — 11Street store id or a store URL containing it (examples: "1188", "https://shop.11st.co.kr/stores/1188"; minLength: 1)

Response

• @type string (default: "Street11Seller")
• id string required
• name string nullable
• url string nullable
• like_count integer nullable
• business_name string nullable
• representative string nullable
• business_type string nullable
• positive_review_rate number nullable
• response_rate number nullable
• sales_grade number nullable
• order_fulfillment_rate number nullable
• shipping_on_time_rate number 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 store id, or page has no store data) 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.