Leboncoin Scraper at a glance
Leboncoin Scraper is a ready-to-run Apify actor from abotapi for collecting real estate data. Its documented output includes id, title, change type (incremental mode), price (eur) and category, which you can export as JSON, CSV or Excel or read through the Apify API. It costs $1.50 per 1,000 results on the Apify Free plan and from $0.80 on paid plans, with smaller per-run or optional feature charges listed on Apify.
- Runs on
- Apify cloud: console, API, schedules and integrations
- Data type
- Real Estate, Jobs, Ecommerce
- Region
- Europe
- Pricing
- $1.50 per 1,000 results (Free plan), from $0.80 on paid plans
- Output
- Documented below · JSON, CSV, Excel
- Inputs
- 33 options
Scrape Leboncoin.fr classifieds across cars, property, jobs, electronics, furniture and 35+ categories. Extract 60–78 fields including prices, GPS coordinates, seller details, attributes and images. Supports filtered searches, URLs, pagination and listing deduplication.
What Leboncoin Scraper can do
- Two ways to search. Build a search from filters (category, location, price, and more), or paste one or more Leboncoin search URLs and let the actor walk them forward.
- 60 to 80 flat fields per listing. Price, location down to GPS coordinates, full seller info, and every category-specific attribute the site returns (mileage, fuel, rooms, surface area, and more), not a hard-coded subset.
- Multi-location and multi-category in one run. Search several cities or paste several search URLs, and get a fair share of listings from each.
- Optional detail-page enrichment. Turn on a single input to also fetch the full description text and the complete image gallery for each listing.
- Optional seller enrichment. Pull a seller's star rating and written reviews, or their other active listings, useful for mapping professional sellers' catalogues.
- Per-search budget. Max listings is shared fairly across every location or URL in the run, so a multi-city search returns a sample from every city instead of exhausting the budget on the first one.
Choose what to collect
These inputs let you configure Leboncoin Scraper - Classifieds, Prices, Sellers & Listings. Open the actor on Apify to enter your values and review the current options.
| Input | What it controls |
|---|---|
modestring · required | Search mode builds the URL from your filters. URL mode takes one or more Leboncoin search URLs and walks them forward. |
textstring | Optional keyword query (e.g. 'iphone 14', 'aston martin'). Search mode only: in URL mode the keywords come from the URL's own ?text= segment. Relevance is decided by leboncoin's own search engine, so accented and inflected matches are returned as the site returns them. |
categorystring | Top-level category. Search mode only: in URL mode the category comes from the URL's own ?category= segment. Category ids were re-derived from the live site on 2026-09-04, so each option now returns the category it names. "Workwear" no longer exists on leboncoin and is kept only so older saved tasks still run: it behaves like "All categories". |
locationsarray | Cities, regions, or department codes. Search mode only: in URL mode locations come from the URL's own ?locations= segment. Use a city name (['Paris', 'Lyon', 'Marseille']), a postcode (['75001']), or a metropolitan department code with or without the _d suffix (['75', '69_d']). Corsica (2A, 2B) and the overseas departments (971 to 976) are not accepted as department codes by the site and return nothing, so use a city name there instead ('Ajaccio', 'Bastia', 'Fort-de-France'). Leave empty for all of France. Multi-location is supported. |
minSquareinteger | Minimum surface area in m² (property categories). Search mode only: in URL mode this comes from the URL's own ?square= segment. |
maxSquareinteger | Maximum surface area in m² (property categories). Search mode only: in URL mode this comes from the URL's own ?square= segment. |
minMileageinteger | Minimum mileage in km (vehicle categories). Search mode only: in URL mode this comes from the URL's own ?mileage= segment. |
Show 26 more inputs
| Input | What it controls |
|---|---|
maxMileageinteger | Maximum mileage in km (vehicle categories). Search mode only: in URL mode this comes from the URL's own ?mileage= segment. |
urlsarray | Leboncoin URLs to scrape (URL mode only): search pages (/recherche?...), category pages (/c/), single ads (/ad//), pro shops (/boutique/) and seller profiles (/profile/). Multi-URL supported. A pasted search URL carrying page=N starts at page N, otherwise at the first page. Price, seller type and sort inside a pasted search URL are applied; the Sort order input overrides the URL's sort when set. Search-mode-only fields (keywords, category, locations, surface area, mileage) are ignored here because the URL already carries them. |
ownerTypestring | Filter by seller type. Applies in both modes: it is enforced on every listing after it is fetched, including listings reached from a pasted URL. |
minPriceinteger | Minimum price in euros. Leave empty for no minimum. Applies in both modes: it is enforced on every listing after it is fetched, including listings reached from a pasted URL. |
maxPriceinteger | Maximum price in euros. Leave empty for no maximum. Applies in both modes: it is enforced on every listing after it is fetched, including listings reached from a pasted URL. |
roomsarray | Filter by number of rooms (property categories). Multi-select supported, e.g. [2, 3, 4]. Applies in both modes: it is enforced on every listing after it is fetched, including listings reached from a pasted URL. |
fuelstring | Filter by fuel type (cars / motorcycles). Applies in both modes: it is enforced on every listing after it is fetched, matched against the listing's own fuel label. A ?fuel= segment inside a pasted URL is ignored, so set this input instead. |
sortBystring | How to sort results. Applies in both modes: in URL mode it overrides any ?sort= / ?order= segment in the pasted URL. |
maxPagesinteger | How many pages to walk per search URL (~100 listings per page). Leave at 0 to walk until 'maxListings' is reached or the search runs out of results. A built-in hard cap of 1000 pages per search always applies. |
maxListingsinteger | Maximum total listings to return across all searches. Set 0 for unlimited. |
fetchDetailsboolean | Visit each listing's detail page to pull the full description body, full image gallery, owner phone availability, similar listings, and any extra category attributes. Adds about 1 second per listing. Each delivered enriched listing is charged as one detail-page event on top of the per-result charge; listings the site refuses, listings skipped with the toggle off, and listings incremental mode suppresses as unchanged are not charged. |
fetchSellerReviewsboolean | For each listing, fetch the seller's textual reviews (star rating + customer feedback). Adds about 0.5 seconds per item. Sellers with no reviews get an empty array. |
maxReviewsinteger | How many of the seller's textual reviews to return per listing when seller reviews are enabled (most recent first, fetched page by page). Any value from 1 to 200 is honoured; the default is 20. |
fetchSellerOtherListingsboolean | For each listing, fetch the seller's other active ads (subject, price, URL, image). Adds about 0.5 seconds per item. Useful for mapping professional-seller catalogues. |
resumeFromRunIdstring | Paste a previous run ID or dataset ID to continue a large crawl without returning or charging for listings already collected there. Use this after an interrupted run, or when continuing a big pull across another run. For recurring monitoring of the same search, use Incremental mode below instead. |
incrementalModeboolean | Turn this on for daily or recurring monitoring. Flipping Fetch detail pages (or any compared scope) starts a fresh baseline for this search, by design. The first run returns all matching listings as NEW. Later runs normally return only NEW, UPDATED, and REAPPEARED listings. What is compared: every output field of a listing (price, title, description, location, seller, images, attributes) against the copy saved by the previous run; any difference in a compared field makes the listing UPDATED and changedFields names it. What is excluded: view and favourite counters, the site's re-index timestamp and the seller's rating, reviews and other-listings fields never count as a change (they are still returned), plus any field you list in "Ignore fields when detecting changes"; "Compare scope" can narrow the comparison to price and status only. Turn on "Emit unchanged" or "Emit expired" only when you also want those listings returned (and billed). State is kept separately for each search/URL, detail-mode and comparison setup; use State key when you want to name or deliberately share a monitoring campaign. To continue one specific interrupted run instead, use Resume from a previous run above. |
stateKeystring | Optional. Name this monitoring campaign to keep its state stable, or to deliberately share state across differently-configured runs. Leave empty to let the actor derive a key automatically from the search/URL and filter settings, different searches then never mix state with each other. Flipping Fetch detail pages (or any compared scope) starts a fresh baseline for this search, by design: the first run after the flip classifies every listing NEW again. |
emitUnchangedboolean | Off by default. Turn on to also return listings that have not changed since the last run, marked UNCHANGED. This returns, and bills, extra rows you already have, so leave it off unless you specifically want the full snapshot every run. |
emitExpiredboolean | Off by default. Turn on to also return listings that were present in a previous run but are no longer found, marked EXPIRED. Only produced once a run has fully scanned the tracked search from its first page to its natural end, not when Max listings or Max pages capped it, when a pasted URL starts at a page after the first, or when Resume was used. A listing missing from a search is not proof that it was sold or deleted. This returns, and bills, extra synthetic rows, so leave it off unless you need expiry tracking. |
expireAfterMissedScansinteger | Only used with "Emit expired". A listing is marked EXPIRED only after it was missing from this many complete scans in a row (default 1 = the first complete scan that no longer finds it). Raise it to ignore listings that briefly drop out of the search. EXPIRED means no longer found in the search, not confirmed sold or removed. |
changeScopestring | All fields (default): any change to a compared field makes a listing UPDATED. Price and status only: only price, price range and ad status decide UPDATED; description, photos, location and seller changes never create a row. |
compactUpdatesboolean | Off by default. When on, UPDATED and EXPIRED rows are slim: identifiers, current price and status, and priceChanges with the old and new value. NEW rows stay full. One row is still returned per listing. |
ignoreFieldsForChangesarray | Field names that never make a listing UPDATED, for a field that changes on its own on your searches. Use a top-level name (for example image_urls) or a dotted path into a nested field (for example owner_raw.name). Ignored fields are still returned and the change is not reported in changedFields. Changing this list starts a separate baseline unless you set State key. |
mcpConnectorsarray | Optionally send the scraped results into the apps you already use, via Model Context Protocol (MCP) connectors. Authorize a connector once under Apify → Settings → Integrations, then select it here. The connector receives a condensed, human-readable summary per item (title + key fields), not the full JSON, the complete record stays in the dataset. Leave empty to skip. Supported: Notion (https://mcp.notion.com/mcp), Linear (https://mcp.linear.app/sse), Airtable (https://mcp.airtable.com/mcp), Apify (https://mcp.apify.com). |
notionParentPageUrlstring | URL (or id) of the Notion page under which item pages are created. Required to enable the Notion export; ignored by other connectors. |
maxNotifyListingsinteger | Cap on items written to each connector per run. Does not affect the dataset. |
Fields in the output
The documented dataset includes the fields below. Availability can depend on the source page and selected mode.
idID (text)subjectTitle (text)changeTypeChange type (incremental mode) (text)pricePrice (EUR) (number)category_nameCategory (text)cityCity (text)zipcodeZip (text)departmentDept (text)owner_typeSeller (text)owner_nameSeller name (text)publication_datePosted (text)urlURL (link)Show 28 more fields
changedFieldsChanged fields (incremental mode) (array)firstSeenAtFirst seen (incremental mode) (date)lastSeenAtLast seen (incremental mode) (date)detailFetcheddetailFetchedowner_store_idStore ID (text)owner_user_idUser ID (text)has_phoneHas phone (boolean)seller_rating_avgSeller avg rating (text)seller_review_countSeller reviews (text)seller_reviewsseller_reviews (text)ratingReview stars (number)textReview text (text)dateReview date (date)author_nameReviewer (text)pricing.amount_eurPrice (EUR) (number)pricing.price_per_square_meterPrice per m2 (number)pricing.feesFees (text)pricing.annual_chargesAnnual charges (text)property.typeProperty type (text)property.surface_m2Surface m2 (number)property.roomsRooms (number)property.bedroomsBedrooms (number)property.building_yearBuilt (number)property.energy.ratingEnergy rating (text)property.energy.gesGES (text)attr_regdateRegistration year (number)attr_mileageMileage (number)attr_fuelFuel (text)Example output
An example from this actor’s documentation. Values are illustrative; this is not a fresh live result.
{
"id": "1234567890",
"list_id": 1234567890,
"subject": "Sample Listing Title",
"body": "Full seller description text appears here when fetchDetails=true.",
"url": "https://www.leboncoin.fr/ad/voitures/1234567890",
"category_id": "2",
"category_name": "Voitures",
"ad_type": "offer",
"status": "active",
"price": 0,
"publication_date": "2026-01-01 00:00:00",
"has_phone": true,
"is_boosted": false,
"city": "Paris",
"zipcode": "75001",
"department": "Paris",
"region": "Ile-de-France",
"latitude": 48.8566,
"longitude": 2.3522,
"owner_type": "private",
"owner_name": "Sample Seller",
"image_count": 5,
"image_urls": [
"https://img.leboncoin.fr/api/v1/lbcpb1/images/00/00/00/000000.jpg?rule=ad-image"
],
"attr_regdate": "2020",
"attr_mileage": "50000",
"attr_fuel": "Diesel",
"raw_attributes": [],
"seller_rating_avg": 4.8,
"seller_review_count": 42,
"seller_reviews": [
{
"rating": 5,
"text": "Vendeur serieux, transaction rapide.",
"author_name": "Sample Buyer",
"date": "2026-03-15T12:00:00Z"
}
]
}Ways to use this data
- Car and vehicle market research: track prices, mileage and listing volume for specific makes, models or regions.
- Property market monitoring: collect listings by city, price band, surface area and room count for rental or sale market analysis.
- Lead generation for pro sellers: filter by seller type and category to find active listings worth reaching out about.
- Price tracking and alerts: run the same search on a schedule with Incremental mode to catch new listings and price changes as they happen.
- Marketplace and competitor analysis: map a professional seller's full catalogue with the seller-other-listings enrichment.
Before you run
Start with a small input and check the resulting records against your expected fields. Source content and actor options can change; the current Apify listing is the reference for availability and pricing.
Questions about this actor
What data does Leboncoin Scraper return?
The documented output for Leboncoin Scraper includes id, title, change type (incremental mode), price (eur), category, city, zip and dept. Availability of each field depends on the source page and the selected mode.
How much does Leboncoin Scraper cost?
It costs $1.50 per 1,000 results on the Apify Free plan and from $0.80 on paid plans, with smaller per-run or optional feature charges listed on Apify. The Apify listing shows the current rate for every plan.
Can I get only new or changed listings on a schedule?
Yes. Schedule the actor from the Schedules tab and turn on Incremental mode. Each run then returns only new and updated listings, and unchanged ones are not billed. EXPIRED and REAPPEARED rows require also turning on emitExpired, and only appear once a run has fully scanned the tracked search.
Why did my run fail instead of returning an empty dataset?
If every connection attempt is refused during startup, the run stops with a clear message so "no listings match this search" is never confused with "the site could not be reached at all." Run it again in a few minutes. A search that genuinely has no matches still returns a normal empty result rather than failing.
Can I use it with AI agents or MCP?
Yes. Call it from any Apify integration or MCP client, and use the connector field to push results into Notion, Linear or Airtable.
