/n11/products

POST /api/n11/products

Price: 10 credits

Get full N11 product details by product id (or product URL): name, brand, price, list_price, discount, images, rating, review counts and star breakdown, attributes, variants, category, breadcrumbs, seller and other sellers offering the same product.

How to use it

Fetch a single N11 product by numeric product page id or a product URL. Returns one item with name, subtitle, brand, price/list_price/discount_percentage/currency (TRY), image+images, rating, rating_count, review_count, favorite_count, stock, is_in_stock, is_free_shipping, shipment_city, preparation_time, category+category_id+breadcrumbs, per-star review counts, attributes (name/value specs), variants (sku options with price and stock), seller (id/name/company_name/rating/grade) and other_sellers (other merchants offering the same product with their price and rating).

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• product string required — N11 product page id or a product URL containing it (examples: "43821353", "https://www.n11.com/urun/apple-iphone-15-128-gb-apple-turkiye-garantili-43821353"; minLength: 1)

Response

• @type string (default: "N11Product")
• id string required
• page_id string nullable
• url string required
• name string nullable
• subtitle string nullable
• brand string nullable
• price number nullable
• list_price number nullable
• discount_percentage number nullable
• currency string (default: "TRY")
• image string nullable
• images array (default: [])
• rating number nullable
• rating_count integer nullable
• review_count integer nullable
• favorite_count integer nullable
• stock integer nullable
• is_in_stock boolean nullable
• is_free_shipping boolean nullable
• shipment_city string nullable
• preparation_time string nullable
• category string nullable
• category_id string nullable
• breadcrumbs array (default: [])
• five_star_count integer nullable
• four_star_count integer nullable
• three_star_count integer nullable
• two_star_count integer nullable
• one_star_count integer nullable
• badges array (default: [])
• attributes array (default: [])
  • @type string (default: "N11ProductAttribute")
  • name string required
  • value string nullable
• variants array (default: [])
  • @type string (default: "N11ProductVariant")
  • sku_id string required
  • product_id string nullable
  • gtin string nullable
  • price number nullable
  • is_in_stock boolean nullable
  • options array (default: [])
• seller object nullable
  • @type string (default: "N11ProductSeller")
  • id string required
  • name string nullable
  • company_name string nullable
  • rating number nullable
  • grade integer nullable
  • image string nullable
  • is_official boolean nullable
  • is_quick_seller boolean nullable
  • feedback_count integer nullable
• other_seller_count integer nullable
• other_sellers array (default: [])
  • @type string (default: "N11ProductOffer")
  • seller_id string required
  • seller_name string nullable
  • rating number nullable
  • grade integer nullable
  • price number nullable
  • list_price number nullable
  • review_count integer nullable
  • has_free_cargo boolean nullable
  • is_official_seller boolean nullable
  • url 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 — Product not found (well-formed but nonexistent product id, or page has no product) 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.