/leroymerlin/stores/stock

POST /api/leroymerlin/stores/stock

Price: 20 credits

Get the in-store stock of a Leroy Merlin Italy or Spain product at the stores nearest to a point: quantity available, stock level, distance and opening status

How to use it

Pass coordinates of the place to search around, not a city name, and the product id with the country site it came from. Stores are ordered by distance from the coordinates.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• country string required — Leroy Merlin country site (one of: "it", "es")
• product string required — Leroy Merlin product id or product URL (examples: "89621591"; minLength: 1)
• latitude number required — Latitude of the place to search around (examples: 41.9028; min: -90; max: 90)
• longitude number required — Longitude of the place to search around (examples: 12.4964; min: -180; max: 180)
• count integer required — Max number of stores to return (min: 1; max: 10)

Response

• @type string (default: "LeroyMerlinStoreStock")
• store_product_id string required
• store_id string required
• product_id string required
• name string nullable
• city string nullable
• url string nullable
• distance_km number nullable
• opening_status string nullable
• opening_note string nullable
• stock_quantity integer nullable
• stock_level string nullable
• stock_text 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 — No product has this id on that country site. 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.