Leboncoin Scraper - Listings & Prices

Leboncoin Scraper collects public classified listings from Leboncoin search URLs, ad URLs, or keyword searches. It is built for French marketplace research, price tracking, and lead discovery. Each dataset record represents one public listing and includes the listing identity, title, price, location, seller information, images, attributes, source URL, and scrapedAt timestamp. The actor is available through Apify and can also be used through Apify MCP for structured marketplace workflows.

Best fit and connected workflows

This actor fits workflows where you want public Leboncoin inventory in a clean dataset for analysis, alerts, or enrichment. Common routes include:

• Search-based monitoring for a category, keyword, or saved Leboncoin query.
• Ad-URL collection when you already have specific public listings to process.
• Price tracking across repeated runs using the same search URL.
• Lead discovery from public seller and listing metadata.
• AI agent workflows through Apify MCP when an agent needs current Leboncoin records in a structured format.

Practical scenario

Sophie, a marketplace analyst, starts with a Leboncoin search URL for used phones in Electronics. She runs the actor with maxItems set to 50 and includeDetails set to false. The returned records include priceEur, city, sellerName, sellerType, firstImageUrl, and scrapedAt. Sophie uses those fields to compare asking prices by city, then opens the matching ad URLs for a closer manual review of the most relevant listings.

Input fields

Field	Type	Purpose
startUrls	array	Leboncoin search URLs, ad URLs, or legacy ad URLs
searchQueries	array of strings	Keyword searches used to build Leboncoin search URLs
categoryId	string	Category selector for keyword-based searches
priceMin	integer	Minimum price in EUR for keyword-based searches
priceMax	integer	Maximum price in EUR for keyword-based searches
ownerType	string	Seller type filter: all, private, or pro
sort	string	Sort mode: time or price
order	string	Sort order: desc or asc
maxItems	integer	Maximum number of listing records written to the dataset
maxPages	integer	Maximum result pages visited per search
includeDetails	boolean	Fetch detail pages for richer public descriptions and attributes
responseFormat	string	Record shape: concise or detailed
proxyCountry	string	Residential proxy country used by the actor-managed browser session

Focused input example

{
  "searchQueries": [
    "iphone"
  ],
  "categoryId": "17",
  "priceMin": 100,
  "priceMax": 500,
  "ownerType": "all",
  "sort": "time",
  "order": "desc",
  "maxItems": 25,
  "maxPages": 3,
  "includeDetails": false,
  "responseFormat": "concise",
  "proxyCountry": "FR"
}

Output fields

The default dataset contains one record per validated Leboncoin listing returned by the run.

Field	Type	Purpose
listingId	string	Stable Leboncoin listing identifier
listingUrl	string	Canonical public ad URL
title	string	Public listing title
categoryId	string or null	Leboncoin category identifier
categoryName	string or null	Human-readable category name
priceEur	number or null	Advertised price in euros
currency	string or null	ISO currency code
locationLabel	string or null	Combined public location label
city	string or null	City from the public payload
postalCode	string or null	Postal code from the public payload
department	string or null	Department when available
region	string or null	Region when available
latitude	number or null	Approximate latitude
longitude	number or null	Approximate longitude
sellerId	string or null	Public seller or store identifier
sellerName	string or null	Public seller display name
sellerType	string or null	Seller classification
sellerUrl	string or null	Public seller or store URL
description	string or null	Public ad body text when detail extraction is selected
attributes	array	Category-specific public attributes
imageUrls	array	Public listing image URLs
firstImageUrl	string or null	Primary image URL
listingCreatedAt	string or null	First publication timestamp
indexDate	string or null	Index or update timestamp
status	string or null	Listing status when available
urgent	boolean or null	Urgent flag when present
shippable	boolean or null	Shipping flag when present
hasPhone	boolean or null	Indicates whether a phone number exists as a public flag
detailFetched	boolean	Shows whether a detail page was fetched and merged
sourceSearchUrl	string	Source search or ad URL
scrapedAt	string	Extraction timestamp
parseWarnings	array of strings	Non-fatal parsing notes

Illustrative output record

{
  "listingId": "3055076563",
  "listingUrl": "https://www.leboncoin.fr/ad/arts_de_la_table/3055076563",
  "title": "Boite coffre",
  "categoryId": "45",
  "categoryName": "Arts de la table",
  "priceEur": 4,
  "currency": "EUR",
  "locationLabel": "Toulouse 31000 Capitole",
  "city": "Toulouse",
  "postalCode": "31000",
  "department": "Haute-Garonne",
  "region": "Occitanie",
  "sellerName": "eva2019",
  "sellerType": "private",
  "firstImageUrl": "https://img.leboncoin.fr/api/v1/lbcpb1/images/example.jpg?rule=ad-large",
  "detailFetched": false,
  "sourceSearchUrl": "https://www.leboncoin.fr/recherche?text=iphone&category=17",
  "scrapedAt": "2026-07-15T12:00:00.000Z",
  "parseWarnings": []
}

How it works

The actor accepts either direct Leboncoin URLs or keyword-based searches. When you provide startUrls, it uses those exact public Leboncoin search or ad URLs. When you provide searchQueries, it builds Leboncoin search URLs and can apply the selected category, price range, seller type, sort mode, and order.

It writes normalized public listing records to the default dataset. The output artifacts include:

• listings for the dataset items
• output for a compact run outcome
• runSummary for diagnostics and billing details

When includeDetails is enabled, the actor also fetches public ad detail pages and merges richer fields such as description and additional attributes into the listing record.

Pricing

This actor uses Pay per event pricing plus Apify platform usage.

The charged events are:

• Actor start: charged once per GB of configured actor memory at run start.
• Leboncoin listing returned: charged for each validated listing written to the default dataset.

The primary listing event is billed at $0.002 per listing, and Apify platform usage is charged separately. For example, a run that writes fifty listings creates fifty listing events, plus the actor start event and normal platform usage. For current details, open the live Pricing tab on the actor page.

Use with AI agents (MCP)

This actor is available as an Apify Actor usable through Apify MCP. It is designed for agent workflows that need public Leboncoin listings in a structured dataset and a compact machine-readable run outcome.

• Tool description: scrape public Leboncoin listings from search URLs or keywords and return normalized listing records with prices, locations, sellers, images, attributes, and timestamps.
• Exact Actor identity: khadinakbar/leboncoin-scraper

Find 20 public Leboncoin listings for iPhone searches in Electronics, keep the output concise, and return the dataset items with price, city, seller type, and source URL.

Output interpretation:

• Use listingUrl as the canonical record identifier for review and downstream linking.
• Use priceEur, city, sellerName, and sellerType for marketplace analysis.
• Use firstImageUrl for quick visual inspection.
• Use sourceSearchUrl and scrapedAt for provenance.
• Use detailFetched to distinguish search-result records from records enriched through detail pages.

Provenance and scope:

• The actor collects public Leboncoin data only.
• Each dataset item corresponds to one validated listing returned by the run.
• The output and runSummary records provide run-level counts and diagnostics.

Pagination and cost guidance:

• maxPages limits how many result pages are visited per search.
• maxItems limits how many listing records are written and charged.
• In keyword workflows, a higher page limit can still be bounded by a smaller item limit.

Apify API example

import { ApifyClient } from "apify-client";

const client = new ApifyClient({
  token: process.env.APIFY_TOKEN,
});

const run = await client.actor("khadinakbar/leboncoin-scraper").call({
  searchQueries: ["iphone"],
  categoryId: "17",
  maxItems: 5,
  includeDetails: false,
  responseFormat: "concise",
});

const dataset = client.dataset(run.defaultDatasetId);
const { items } = await dataset.listItems();

console.log(items);

Best results and outcome guidance

Use startUrls when you already have a Leboncoin search page with the exact filters you want preserved. Use searchQueries when a keyword-based workflow is enough and you want the actor to build the search URL.

For cleaner marketplace analysis:

• Keep responseFormat set to concise for search-result datasets.
• Set includeDetails to true when you want public descriptions and richer ad attributes.
• Use categoryId, priceMin, priceMax, ownerType, sort, and order together for keyword-driven searches.
• Use a full search URL for complex location filters such as city or radius settings.
• Review parseWarnings when a record needs a manual check.

Continue the workflow

• Then use 1688 Product Listings Scraper — Wholesale Prices & Suppliers to extend Leboncoin Scraper - Listings & Prices with a neighboring commerce research source when the brief calls for 1688 data.
• Then use Zara Product Scraper — Prices, Stock & Variants to extend Leboncoin Scraper - Listings & Prices with a neighboring commerce research source when the brief calls for Zara data.

Design note

I found that the dataset contract includes both detailFetched and parseWarnings, which makes it clear that the actor separates core listing extraction from optional detail-page enrichment and visible extraction notes.

FAQ

When should I use a search URL instead of keywords?

Use a search URL when you already have exact Leboncoin filters, especially for location-based or highly specific browsing states. Use keywords when you want the actor to construct the search query for you.

What workflow should I use for public seller review?

Start with searchQueries or a saved startUrls search, then review sellerName, sellerType, sellerUrl, and listingUrl in the dataset. That gives a practical path from marketplace search to seller-level review.

How should I route a price-tracking workflow?

Use a consistent startUrls search or the same keyword and filter combination over time, then compare priceEur, city, and scrapedAt across runs.

How does this fit AI agent workflows?

Use the actor through Apify MCP when an agent needs structured Leboncoin listings. The compact output and dataset schema support retrieval, filtering, and downstream analysis.

Responsible use

This actor is intended for public Leboncoin listing data and respectful collection. It is a good fit for research, monitoring, and analysis workflows that work with publicly available marketplace content. Keep your use aligned with applicable laws, platform terms, privacy rules, and internal data-handling policies.