/magazineluiza/products

POST /api/magazineluiza/products

Price: 1 credit

Get full Magazine Luiza (Magalu) product details by SKU/id or product URL: name, brand, price, installments, images, rating, seller (buybox), availability, description, attributes and category.

How to use it

Fetch a single Magalu product by SKU/id (e.g. ke2kf0a6kg or 238803400) or a product URL. Returns one item with name, brand, reference, image, description, price (best/full/list price, discount, currency), installment plan, rating, seller buybox (name, score, location), category/subcategory, attributes, availability and url. Optionally pass a zipcode (CEP) for locality-aware price/availability, or a seller_id to select a specific marketplace offer.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• zipcode string nullable — Brazilian ZIP code (CEP) for locality-aware pricing and availability (examples: "01310100")
• product string required — Product SKU/id or a full product URL (examples: "ke2kf0a6kg", "238803400", "https://www.magazineluiza.com.br/apple-iphone-16-128gb/p/238803400/te/ip16/"; minLength: 1)
• seller_id string nullable — Select a specific marketplace seller offer by seller id
• include_description boolean — Include the full product description text (default: true)

Response

• @type string (default: "MagazineluizaProduct")
• id string required
• name string nullable
• reference string nullable
• brand object nullable
  • @type string (default: "MagazineluizaBrand")
  • name string nullable
  • alias string nullable
• image string nullable
• description string nullable
• is_available boolean nullable
• is_buy_box boolean nullable
• product_type string nullable
• variation_id string nullable
• price object nullable
  • @type string (default: "MagazineluizaPrice")
  • best_price number nullable
  • full_price number nullable
  • list_price number nullable
  • discount_percent number nullable
  • currency string nullable
  • payment_description string nullable
• installment object nullable
  • @type string (default: "MagazineluizaInstallment")
  • quantity integer nullable
  • amount number nullable
  • total_amount number nullable
  • payment_description string nullable
• rating object nullable
  • @type string (default: "MagazineluizaRating")
  • count integer nullable
  • score number nullable
• seller object nullable
  • @type string (default: "MagazineluizaSeller")
  • id string nullable
  • name string nullable
  • legal_name string nullable
  • document_number string nullable
  • seller_type string nullable
  • score number nullable
  • total_sales integer nullable
  • since_at integer nullable
  • city string nullable
  • state string nullable
  • delivery_description string nullable
  • delivery_rate string nullable
  • answer_rate string nullable
  • is_chat_enabled boolean nullable
• category object nullable
  • @type string (default: "MagazineluizaCategory")
  • id string nullable
  • name string nullable
• subcategory object nullable
  • @type string (default: "MagazineluizaCategory")
  • id string nullable
  • name string nullable
• attributes array (default: [])
  • @type string (default: "MagazineluizaProductAttribute")
  • attribute_type string nullable
  • label string nullable
  • value string nullable
  • current string nullable
  • values array (default: [])
• offer_tags array (default: [])
• minimum_order_quantity integer nullable
• path string 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 SKU/id) 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.