/trendyol/products

POST /api/trendyol/products

Price: 10 credits

Get full Trendyol product details by contentId (or product URL): name, brand, price, list_price, discount, images, rating, reviews count, attributes, variants, category, seller, other sellers and active promotions.

How to use it

Fetch a single Trendyol product by contentId (numeric) or a product URL. Returns one item with name, brand/brand_id/brand_url, price/list_price/discount_percentage/currency (TRY), image+images, rating, rating_count, review_count, favorite_count, is_in_stock, category+category_hierarchy+breadcrumbs, gender, max_installment, is_refundable, is_global_brand, energy_class, attributes (name/value specs), variants (size/color options with per-variant price and stock), seller (id/name/official_name/city/rating/image), other_sellers (other merchants offering the same product with their price and rating) and promotions.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• product string required — Trendyol product contentId or a product URL containing it (examples: "689227641", "https://www.trendyol.com/apple/yenilenmis-iphone-12-64-gb-beyaz-cep-telefonu-12-ay-garantili-a-kalite-p-689227641"; minLength: 1)

Response

• @type string (default: "TrendyolProduct")
• id string required
• url string required
• name string nullable
• product_group_id string nullable
• brand string nullable
• brand_id string nullable
• brand_url string nullable
• price number nullable
• list_price number nullable
• discount_percentage number nullable
• currency string nullable
• image string nullable
• images array (default: [])
• rating number nullable
• rating_count integer nullable
• review_count integer nullable
• favorite_count integer nullable
• is_in_stock boolean nullable
• category string nullable
• category_hierarchy string nullable
• breadcrumbs array (default: [])
• gender string nullable
• max_installment integer nullable
• is_refundable boolean nullable
• is_global_brand boolean nullable
• energy_class string nullable
• attributes array (default: [])
  • @type string (default: "TrendyolProductAttribute")
  • name string required
  • value string nullable
• variants array (default: [])
  • @type string (default: "TrendyolProductVariant")
  • item_number string required
  • value string nullable
  • is_selected boolean nullable
  • is_in_stock boolean nullable
  • price number nullable
  • barcode string nullable
• seller object nullable
  • @type string (default: "TrendyolSeller")
  • id string required
  • name string nullable
  • official_name string nullable
  • city string nullable
  • rating number nullable
  • image string nullable
• other_seller_count integer nullable
• other_sellers array (default: [])
  • @type string (default: "TrendyolProductOffer")
  • seller_id string required
  • seller_name string nullable
  • rating number nullable
  • price number nullable
  • list_price number nullable
  • currency string nullable
  • url string nullable
  • has_free_cargo boolean nullable
• promotions array (default: [])
  • @type string (default: "TrendyolProductPromotion")
  • id string nullable
  • name string nullable
  • type string nullable
  • is_applied boolean 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 contentId, 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.