Leboncoin Messages Reader

Yes — it is your own inbox. You sync your own account and read conversations you are already a party to, which is about as lawful as data gets. More in our guide to the legality of web scraping.

Yes — a private inbox has no public side. You sync your own account once through the Chrome extension, with session cookies and never your password. Here is how the sync works.

29 data points, one row per message. The text, who sent it, the date and time, whether it was read on either side, how many files are attached — plus the listing it hangs off (title, id, status, photo) and the other party's name.

About 20 messages a minute. An inbox of a few hundred messages is done while you make coffee, and the crawler paces itself between conversations so your account never reads like a robot in a hurry.

No — your unread badges stay exactly where you left them. The crawler reads and nothing else; it never tells Leboncoin you opened a thread. The other party sees no change either, so you can run it every hour.

Yes — switch on Received Messages Only. You get the other party's messages alone, without your own outreach in between. Leave it off and your sent messages come along too, which is handy for reading a reply in context.

Yes — Newer than takes 24h, 7d, 2w or a plain date. Anything older is left alone, so a daily run brings back only what arrived since yesterday. Absolute dates are read in the timezone you pick, Europe/Paris by default.

Yes — paste the conversation link rather than the inbox one. One task, one thread. Turn on Unread Conversations Only to sweep just the ones waiting on you, and use Max Results Per Task to cap how much comes back.

Yes — every row carries the listing id. It is the same id the Leboncoin Auto Message Sender stores, so a reply lines up with the campaign that earned it. Schedule the reader daily and your follow-up list writes itself.

Just about anywhere you already work. Google Sheets, Make, n8n, Amazon S3, email, webhooks — plus our MCP server, so Claude or ChatGPT can launch a run and read the replies itself. CSV, Excel and JSON too. See all integrations.

URL, such as https://www.leboncoin.fr/messages/id/20493b69-f428-4add-899e-17ceb7447ad7. Paste thousands at once or upload a CSV; duplicate inputs are skipped. 6 settings shape the run: see them in the playground.

29 data attributes per message, each with its description and an example: see the full list.

No. Duplicates are removed, and you only pay for unique results.

As fresh as your run: each run collects the data from the site at the moment it runs, nothing comes from a stored database.

CSV, Excel or JSON from the dashboard, through the API, or sent after every run to Google Sheets, Amazon S3, an SFTP server, a webhook or by email.

7 days on the free plan, 45 days on Starter and Pro, 90 days on Team and Business. Then they can no longer be downloaded. Download or deliver what you want to keep.

Around 20 messages a minute for one squid. Your plan's slots run several squids at the same time.

100.00% of its runs had no incident over the last 90 days (0 incidents, 100% fixed). Every day is on this page.

Our team fixes the scraper: every scraper on lobstr.io is built and maintained by us. How we measure.

Yes, on paid plans: every hour, every day, every weekday or on a custom schedule, in your time zone.

Yes: set the most results per task and per run in the settings. The run stops there and so does the bill.

1 credit per result. The playground shows the price as you pick them.

Yes. The free plan gives 100 credits every month, 100 results with this scraper, exported in full.

Every month a plan gives credits, which pay for results, and slots, which set how many squids run at the same time. Starter: $20 for 10,000 credits; Pro: $100 for 100,000 credits; Team: $500 for 1,000,000 credits. Upgrades start right away and are prorated; downgrades and cancellations take effect at the end of the cycle.

No. Your credits refresh every month with your plan.

You choose, per squid: pause and pick up where it stopped, or end the run. To keep going, upgrade or reset your billing cycle: your plan renews right away and your credits come back. Auto Billing Reset does it for you when your usage crosses a threshold you set.

Yes: paying yearly takes 20% off every plan.

A monthly plan: within 10 days of the charge, if no credit was used in that period. A yearly plan: within 30 days, in full if no credit was used, otherwise minus one month. Cancel from your billing page, then write to contact@lobstr.io. The details are in the terms of use.

Collecting publicly available data is generally allowed, but you choose what you collect and you are responsible for how you use it. Our terms of use (article 6) ask every user to respect the rights of the sites, not to extract substantial parts of a database, not to access confidential data and to follow personal data law such as the GDPR. This is not legal advice.

When results contain personal data, you are the data controller and lobstr.io, a French company, processes them on your behalf, under our personal data agreement. You need a lawful basis for what you collect, must inform the people concerned and honor their requests.

Results: 7 days on the free plan, 45 days on Starter and Pro, 90 days on Team and Business, then they can no longer be downloaded; you can delete them sooner. Your account data: see the privacy notice.

Yes, through the REST API at https://api.lobstr.io/v1, with your key from the dashboard. The playground’s Code tab writes the calls for your settings, in cURL and Python. The documentation has the full reference.

Yes. Add our MCP server, https://mcp.lobstr.io/mcp, to Claude, ChatGPT, Cursor or any MCP client and sign in with lobstr.io. Your agent shows the cost and asks you before a run spends credits. The playground’s Agent tab gives you a prompt.

No. Credits pay for results, not for requests.

Yes. Point a webhook at your server and lobstr.io calls it when a run succeeds or fails.

Yes, per endpoint: 120 requests a minute on squids and runs, 90 on tasks, 2 a second on results. Above that the API answers 429 with a Retry-After header.