/leboncoin/listings/similar

POST /api/leboncoin/listings/similar

Price: 20 credits

Get ads similar to a given leboncoin ad (the 'annonces similaires' recommendations): each with title, price, category attributes, images, location and seller.

How to use it

Fetch listings similar to a given leboncoin ad by ID or URL. Returns listing cards (the same shape as a single leboncoin ad) with name, price (EUR), attributes, images, location and seller.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• listing string required — leboncoin ad ID or a listing URL to find similar ads for (examples: "3223387909", "https://www.leboncoin.fr/ad/telephones_objets_connectes/3223387909"; minLength: 1)
• count integer required — Max number of similar ads to return (min: 1; max: 100)

Response

• @type string (default: "LeboncoinListing")
• id string required
• url string required
• name string nullable
• description string nullable
• price number nullable
• currency string (default: "EUR")
• category_id string nullable
• category string nullable
• ad_type string nullable
• status string nullable
• created_at integer nullable
• updated_at integer nullable
• expires_at integer nullable
• image string nullable
• images array (default: [])
• image_count integer nullable
• attributes object (default: {})
  • * string
• region string nullable
• department string nullable
• city string nullable
• zipcode string nullable
• lat number nullable
• lng number nullable
• is_urgent boolean (default: false)
• is_boosted boolean (default: false)
• has_phone boolean (default: false)
• favorite_count integer nullable
• seller object nullable
  • @type string (default: "LeboncoinListingSeller")
  • id string nullable
  • user_id string nullable
  • name string nullable
  • is_pro boolean (default: false)
  • siren string nullable
  • activity_sector_id 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 — Ad not found (well-formed but nonexistent/removed ad 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.