/zara/products

POST /api/zara/products

Price: 10 credits

Get full Zara product details by product id (or product URL): name, reference, description, price, section/family, color variants with per-color images and sizes (with availability and sku) and material composition.

How to use it

Fetch a single Zara product by id (numeric, e.g. 02221014) or a product URL. Returns one item with name, alias, seo_product_id, reference/display_reference, description, price+currency, section/family/subfamily, kind, state, is_in_stock, first_visible_at, image+images, colors (each with name, hex_code, product_id, reference, price, is_in_stock, image+images and sizes that carry availability and sku) and materials (composition by area, material and percentage).

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• product string required — Zara product id or a product URL containing it (examples: "02221014", "https://www.zara.com/us/en/zw-collection-poplin-dress-p02221014.html"; minLength: 1)

Response

• @type string (default: "ZaraProduct")
• id string required
• url string required
• name string nullable
• alias string nullable
• seo_product_id string nullable
• reference string nullable
• display_reference string nullable
• description string nullable
• price number nullable
• currency string nullable
• section string nullable
• family string nullable
• subfamily string nullable
• kind string nullable
• state string nullable
• is_in_stock boolean nullable
• first_visible_at string nullable
• image string nullable
• images array (default: [])
• colors array (default: [])
  • @type string (default: "ZaraProductColor")
  • id string required
  • name string nullable
  • hex_code string nullable
  • product_id string nullable
  • reference string nullable
  • price number nullable
  • is_in_stock boolean nullable
  • description string nullable
  • image string nullable
  • images array (default: [])
  • sizes array (default: [])
    • @type string (default: "ZaraProductSize")
    • name string required
    • availability string nullable
    • sku string nullable
    • price number nullable
• materials array (default: [])
  • @type string (default: "ZaraProductMaterial")
  • area string nullable
  • material string nullable
  • percentage 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.