/street11/products

POST /api/street11/products

Price: 10 credits

Get full 11Street product details by product number (or product URL): name, brand, price, list price, discount, image, rating, review count, on-sale flag, category breadcrumbs and seller.

How to use it

Fetch a single 11Street (11번가) product by prdNo (numeric) or a product URL. Returns one item with name (Korean), brand, image, price/list_price/discount_percent/discount_amount (KRW), currency, is_in_stock, is_on_sale, is_adult, rating (0-5) and review_count, image_count, delivery_fee, category + breadcrumbs (Korean) + category_id, catalog_no and seller (store_no, name, url, satisfaction_rate, response_rate, sales_grade). Content is Korean (KR-only marketplace).

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• product string required — 11Street product number (prdNo) or a product URL containing it (examples: "5917614041", "https://www.11st.co.kr/products/5917614041"; minLength: 1)

Response

• @type string (default: "Street11Product")
• id string required
• url string required
• name string nullable
• brand string nullable
• image string nullable
• price number nullable
• list_price number nullable
• discount_percent number nullable
• discount_amount number nullable
• currency string nullable
• is_in_stock boolean nullable
• is_on_sale boolean nullable
• is_adult boolean nullable
• rating number nullable
• review_count integer nullable
• image_count integer nullable
• delivery_fee number nullable
• category string nullable
• breadcrumbs array (default: [])
• category_id string nullable
• catalog_no string nullable
• seller object nullable
  • @type string (default: "Street11ProductSeller")
  • store_no string nullable
  • name string nullable
  • url string nullable
  • satisfaction_rate number nullable
  • response_rate number nullable
  • sales_grade 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 — Product not found (well-formed but nonexistent prdNo, or page has no product 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.