Skip to content

SeLoger Listings, Rents, and Agent Data API

SeLoger is one of the main places French property data appears, and collecting it by hand across listings is slow and hard to scale.

OUTPUT FORMATSHTMLJSONMarkdown

This page explains how a managed scraping API turns a SeLoger URL into rendered HTML or structured JSON, which request options control cost and output, and how to choose between selector-based and AI-based extraction.

What teams collect from SeLoger

Most SeLoger projects fall into three groups. The first is listing collection: sale and rental properties with asking price, number of beds, square meters, arrondissement and agent information, which feeds French market analysis. The second is rental trend tracking across neighborhoods over time, used for relocation pricing, rental-yield models and market reports. The third is neighborhood context — amenities and walkability signals attached to each listing — used in buyer-search and location-scoring tools.

A single request can return the rendered page, and with extraction rules applied it can return the listing fields directly. That matters when the same pipeline needs to run across many arrondissements and property types without a separate parser for each page layout.

Field and control map

The table below pairs each commonly collected SeLoger field with the request option that produces it. Use it to decide which options a given job actually needs before you spend credits.

How a SeLoger request works

The workflow has four steps.

  1. Create an account. You get an API key and 1,000 free credits to start.
  2. Install a client for your stack. SDKs exist for Python, Node.js, Go, PHP, Ruby and Java, and plain cURL works too. Each scrape becomes a single function call, with no proxy rotation or headless browser to manage yourself.
  3. Send a GET request with your API key and a SeLoger URL. JavaScript renders, residential proxies rotate, and you receive rendered HTML ready to parse.
  4. Add advanced parameters when the page needs more: render_js for JavaScript, stealth_proxy for CAPTCHAs, country_code for geo-targeting, and ai_extract_rules for natural-language extraction.

Setup is quick because the dashboard includes a request builder you can use to test a URL before writing any code.

Choosing between HTML, extraction rules and AI extraction

There are three output shapes, and the right one depends on how stable your target pages are. A plain request returns rendered HTML; adding extract_rules or ai_extract_rules switches the response to parsed JSON.

  • Rendered HTML. Best when you already have a parser or want to inspect the page yourself. No extraction configuration is needed.
  • CSS or XPath extraction rules. Pass extract_rules with selectors mapped to field names. This is the most predictable option when SeLoger markup is consistent across the pages you collect, and it returns parsed JSON.
  • AI extraction rules. Pass ai_extract_rules with a natural-language specification and receive structured JSON without writing selectors. This suits pages whose layout varies, or teams that would rather describe the fields than maintain selector code.

A practical rule: start with selectors for a fixed set of listing pages, and move to AI extraction when the same field set has to survive layout changes or span several page types.

Worked example: tracking rents in one arrondissement

Suppose you want a monthly view of rental asking prices in a single Paris arrondissement. Your request needs the SeLoger search URL for that area, JavaScript rendering because listing content is dynamic, and an extraction rule that maps the rent, number of beds, square meters, arrondissement and agent name to your own field names. The response is parsed JSON you can append to a time-series table.

Run the same request on a fixed schedule, store the capture date alongside each record, and compare month over month. Because SeLoger listings expire and reappear, deduplicate on the listing identifier rather than on price or address. If a request returns an empty result set, check whether the selector matched anything before assuming the target is blocking you — an empty selector and a blocked request look similar in a JSON payload but need different fixes.

Telling failures apart

Three problems produce similar-looking empty or partial results, and each has a different remedy.

  • Blocked or challenged request. The page did not load as expected. Enable stealth_proxy, and keep JavaScript rendering on if the content is dynamic.
  • Selector mismatch. The page loaded but your extraction rule found nothing. Inspect the rendered HTML and update the selector, or switch to ai_extract_rules.
  • Target throttling. Requests succeed individually but fail in bursts. The API applies concurrency limits per plan rather than per-target rate limits, so space out requests or spread them across sessions when the target reacts to aggressive patterns.

Logging the HTTP status and a short excerpt of the response alongside each failure makes this diagnosis fast.

Credits, concurrency and plans

Credit cost per request depends on the options you enable: 5 credits for JavaScript rendering, 25 for premium proxies combined with JavaScript rendering, and 75 for stealth_proxy. API credits are valid for one month and do not roll over, and requests start at 1 credit each. Concurrency is the number of requests that can be sent at the same time, and it is set per plan.

Paid plans start at $19 per month. The plan comparison below lists every tier with its credit allowance and concurrency, so you can match a plan to your expected monthly request volume. All prices are exclusive of VAT. Cancellation terms are set by the account owner and confirmed at signup.

Compliance and data handling

Public-facing pages can usually be scraped, but review the target site's terms of service before deploying and avoid post-login content. The provider states that it does not collect or store personal data from scraped sites unless the user explicitly requests it. Proxy rotation and headless browser rendering are used to reduce IP-based blocking and mimic real browsing behavior.

Legal obligations vary by jurisdiction and by what you do with the collected data, so confirm your own position before running a production pipeline.

SeLoger field and request control map
FieldProduced byNotes
Asking price or rentRendered page or extraction ruleSale and rental listings both supported
BedsRendered page or extraction ruleNumeric field
Square metersRendered page or extraction ruleNumeric field
Arrondissement and cityRendered page or extraction ruleLocation fields
Agent nameRendered page or extraction ruleAgent details
Days on marketRendered page or extraction ruleDerived from listing dates
Image galleryRendered page or extraction ruleFull gallery returned
Neighborhood amenities and walkabilityRendered page or extraction ruleLocation-scoring signals
Structured JSONextract_rules or ai_extract_rulesParsed response, no HTML parsing on your side
Full-page screenshotScreenshot APIVisual record before a listing expires
Markdown outputMarkdown Scraper APISuitable for LLM input

Field availability depends on what the individual SeLoger page exposes; the list reflects the fields the captured page documents.

Plan comparison (captured reference)
PlanMonthly priceAPI creditsConcurrent requestsPriority supportAccount managerTeam management
Hobby$1975,00025Not includedNot includedNot included
Freelance$49250,00050Not includedNot includedNot included
Startup$991,000,000100Not includedNot includedNot included
Business$2493,000,000200IncludedIncludedIncluded
Business +$5998,000,000400IncludedIncludedIncluded
Enterprise 14$99914,000,000500IncludedIncludedIncluded
Enterprise 24$1,59924,000,000600IncludedIncludedIncluded
Enterprise 41$2,39941,000,000700IncludedIncludedIncluded
Enterprise 69$3,59969,000,000800IncludedIncludedIncluded
Enterprise 120$5,799120,000,000900IncludedIncludedIncluded

All prices are exclusive of VAT. This is a dated reference captured from the page and should be checked against current pricing before purchase.

Credit cost by request option
OptionCredit cost
Base request1 credit
JavaScript rendering5 credits
Premium proxies with JavaScript rendering25 credits
Premium proxies without JavaScript rendering10 credits
stealth_proxy75 credits

Credits are valid for one month and do not roll over.

Frequently asked questions

Do I need a SeLoger account to scrape it?

No external account is required. You sign up for an API key, which comes with 1,000 free credits and no card, then send the URL and the service handles the rest.

Is scraping SeLoger legal?

Public-facing pages can usually be scraped, but review the target site's terms of service before deploying and avoid post-login content. Your own legal obligations depend on jurisdiction and on how you use the data.

What rate limits apply to SeLoger scraping?

The API applies concurrency limits per plan rather than per-target rate limits. If the target throttles aggressive patterns, space out requests or use multiple sessions.

How do I get structured JSON from SeLoger?

Pass extract_rules with CSS selectors mapped to field names, or use ai_extract_rules with a natural-language specification. The response comes back as parsed JSON.

Which programming languages can I use?

Any. SDKs are published for Python, Node.js, Go, PHP, Ruby and Java, and plain cURL works too. Pick whatever your stack already uses.

How much does it cost to scrape SeLoger?

Signup includes 1,000 free credits with no card required. Paid plans start at $19 per month for higher volume and concurrency. Credit cost per request depends on options: 5 credits for JavaScript rendering, 25 for premium_proxy with JavaScript, and 75 for stealth_proxy.

What happens if a request returns an empty result?

Check whether the page actually loaded before assuming a block. A selector that matched nothing and a request that was challenged both produce thin output, but the first needs a selector update or AI extraction and the second needs stealth_proxy or JavaScript rendering enabled.