/leboncoin/sellers

POST /api/leboncoin/sellers

Price: 20 credits

Get a leboncoin professional store by store ID, seller UUID or URL: name, SIREN/SIRET, activity sector, description, opening hours, website, address and coordinates, rating with review count, offered services and team.

How to use it

Fetch a single leboncoin professional store by store ID, seller UUID or store URL. Returns one seller with id, name, user_id, siren, siret, activity_sector, category_id, active_since_date, description, slogan, website_url, opening_hours, image, cover, pictures (store gallery), address/city/zipcode/department/region/lat/lng, activity_zone (pro service area with radius and center), rating, review_count, rating_url (public reviews profile), prestations (offered services), team (name/position/image) and media (the store's promoted link card: name, link_url, image).

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• seller string required — leboncoin professional store ID, seller UUID or a store/profile URL (examples: "51895", "https://www.leboncoin.fr/boutique/51895"; minLength: 1)

Response

• @type string (default: "LeboncoinSeller")
• id string required
• url string required
• name string nullable
• user_id string nullable
• siren string nullable
• siret string nullable
• activity_sector string nullable
• category_id string nullable
• active_since_date string nullable
• description string nullable
• slogan string nullable
• website_url string nullable
• opening_hours string nullable
• image string nullable
• cover string nullable
• pictures array (default: [])
• address string nullable
• city string nullable
• zipcode string nullable
• department string nullable
• region string nullable
• lat number nullable
• lng number nullable
• activity_zone object nullable
  • @type string (default: "LeboncoinSellerActivityZone")
  • radius integer nullable
  • city string nullable
  • label string nullable
  • zipcode string nullable
  • department string nullable
  • region string nullable
  • lat number nullable
  • lng number nullable
• rating number nullable
• review_count integer nullable
• rating_url string nullable
• prestations array (default: [])
• team array (default: [])
  • @type string (default: "LeboncoinSellerTeamMember")
  • name string nullable
  • position string nullable
  • image string nullable
• media object nullable
  • @type string (default: "LeboncoinSellerMedia")
  • name string nullable
  • link_url string nullable
  • image 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 — Seller not found (well-formed but nonexistent store/seller reference) 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.