Classifieds price research
Use Leboncoin endpoints to turn classifieds price research into repeatable API requests with documented inputs and JSON responses.
Turn Leboncoin's classifieds listings into structured JSON — normalized public listing cards from a location search, and full public detail for one listing, from France's largest online classifieds marketplace.
Search Leboncoin listings by location and get normalized public listing detail as structured JSON, for France's largest classifieds marketplace.
Endpoint families
2
Documented params
4
Examples
2
Live catalog snapshot
Active endpoints
2
Methods
GET
Required params
4
Schema refs
2
{
"platform": "Leboncoin",
"endpoint": "leboncoin-search",
"method": "GET",
"path": "/leboncoin/search",
"auth": "apiKey"
}Use cases
Search Leboncoin listings by location and get normalized public listing detail as structured JSON, for France's largest classifieds marketplace.
Use Leboncoin endpoints to turn classifieds price research into repeatable API requests with documented inputs and JSON responses.
Use Leboncoin endpoints to turn listing monitoring into repeatable API requests with documented inputs and JSON responses.
Use Leboncoin endpoints to turn marketplace catalog analysis into repeatable API requests with documented inputs and JSON responses.
Managed execution
Every figure below is read from the live Leboncoin endpoint catalog — 2 endpoints, 4 documented request parameters, and 2 published response schemas — the same catalog Docs and Playground run against.
2 documented Leboncoin endpoints, grouped into 2 request families — Listing and Search.
4 request parameters are documented across those Leboncoin endpoints, 4 of them required — the full input contract is public before you write any integration code.
2 of the 2 Leboncoin endpoints ship a recorded example response, and 2 carry a documented response schema — you can code against the real JSON before the first request.
Leboncoin endpoints document their error responses (400, 404, 429 and 503) alongside the success schema, so a block, a rate limit, or a missing record comes back as a typed error rather than silently empty data.
2 hosted MCP tools back the Leboncoin endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Coverage map
/leboncoin/listing
/leboncoin/search
Endpoint catalog
/leboncoin/searchReturns public listing cards from one Leboncoin location page. This endpoint excludes contacts, seller profiles, accounts, and transaction data.
MCP tool leboncoin_search
/leboncoin/listingReturns public metadata for one supplied Leboncoin ad URL. It excludes seller identity and contacts, precise location, payment, delivery, and account data.
MCP tool leboncoin_listing
Related APIs
Marketplaces & Retail
Separate an auction that is still open from a completed sale, and use BaT's own make and model directory to carry valid IDs into search and price-history requests.
Marketplaces & Retail
Treat Glovo as a local marketplace: discover the supported city first, then follow that city's category, store, menu, and collection identifiers through the catalog.
Marketplaces & Retail
Use PetSmart's hierarchical paths to scope product searches, then keep product SKU, price range, online availability, pickup eligibility, and store inventory as separate fields.
How to scrape Leboncoin
Crawlora's Leboncoin endpoints return normalized public listing data as JSON with one API key — no account or session cookie required.
/leboncoin/search takes a required location and returns that location page's normalized public listing cards — around 18 ads, each with id, url, title, category, price_eur and image_url. There is no keyword parameter: the search is geographic, and you filter by category from the returned cards.
price_eur is named for its unit — Leboncoin is a French marketplace and every price is in euros, not the caller's local currency. No conversion is applied, so convert downstream if you are comparing against non-euro sources.
Pass a Leboncoin ad URL — the full public URL, not a bare id — to /leboncoin/listing for that ad's normalized public metadata.
Both endpoints exclude seller identity, contact details, precise location, payment and delivery data by design. That is a scoping decision rather than a gap: the endpoints return only what Leboncoin shows an anonymous visitor, which keeps the data on the right side of France's privacy expectations for classifieds.
On 2026-10-30 /leboncoin/search for the Paris 16e postcode area returned 14 listings with price_eur, while /leboncoin/listing for a listing URL answered 503 Leboncoin request failed.
Agent Skills
安装 Crawlora agent skill，你的智能体即可通过文档化的 API 以 JSON 形式获取 Leboncoin 数据，无需编写爬虫。以下 skill 覆盖 Leboncoin：
Researches secondhand, resale, handmade, and musical-instrument marketplaces via the Crawlora API. Use to compare live listings and sellers, check…
npx skills add github.com/Crawlora-org/crawlora-skills --skill resale-secondhand-researchFAQ
Call /leboncoin/search with a location for that page's normalized listing cards — id, url, title, category, price_eur and image — or /leboncoin/listing with a full ad URL for one ad's public detail. Both return structured JSON with no session cookie or account needed.
Not through this API. /leboncoin/search is anchored on a location and takes no keyword or query parameter, so the practical pattern is to pull a location page and filter by the category field on the returned cards. Each card also carries price_eur, so price filtering happens in your own code rather than in the request.
No — both Leboncoin endpoints exclude seller identity and contact details, precise location, payment, delivery, and account data. They return only the normalized public listing metadata Leboncoin shows to anonymous visitors.
Collecting publicly accessible listing data is generally permissible if you respect Leboncoin's terms of use, robots directives, rate limits, and applicable law. This is for public data you are authorized to collect.