Booli APIbooli.se ↗
Search active and sold Swedish property listings, get listing details, photos, area statistics, and price trends from Booli.se via 6 structured endpoints.
What is the Booli API?
The Booli.se API provides access to Swedish real estate data across 6 endpoints, covering active listings, historical sold properties, listing photos, and area-level market statistics. The search_listings_for_sale endpoint accepts location queries and filters for price range, room count, rent, and property type, returning paginated results with coordinates, addresses, and list prices. Sold transaction history and 12-month price trend series are also available.
curl -X GET 'https://api.parse.bot/scraper/62c0a0dc-f695-46ab-be29-04b903ed21c7/search_listings_for_sale?page=1&query=Stockholm&max_rent=5000&max_price=5000000&max_rooms=5&min_price=1000000&min_rooms=2&object_types=L%C3%A4genhet&max_living_area=150&min_living_area=40' \ -H 'X-API-Key: $PARSE_API_KEY'
Search for active property listings for sale across Sweden. Accepts a free-text location query (municipality, area, or street name). Returns paginated results ordered by most recently published. Each result includes address, price, object type, coordinates, and basic property attributes. Cloudflare-protected; transient blocks trigger proxy rotation.
| Param | Type | Description |
|---|---|---|
| page | integer | Page number for pagination. |
| queryrequired | string | Location search query (municipality, area, or street name, e.g. 'Stockholm', 'Göteborg', 'Nacka'). |
| max_rent | integer | Maximum monthly rent/fee in SEK. |
| max_price | integer | Maximum list price in SEK. |
| max_rooms | integer | Maximum number of rooms. |
| min_price | integer | Minimum list price in SEK. |
| min_rooms | integer | Minimum number of rooms. |
| object_types | string | Property type filter. Accepted values: Lägenhet, Villa, Kedjehus-Parhus-Radhus, Fritidshus, Gård, Tomt/Mark. |
| max_living_area | integer | Maximum living area in m². |
| min_living_area | integer | Minimum living area in m². |
{
"type": "object",
"fields": {
"page": "integer, current page number",
"listings": "array of listing summary objects with booliId, streetAddress, objectType, listPrice, latitude, longitude, tenureForm, published, descriptiveAreaName, daysActive, url"
},
"sample": {
"data": {
"page": 1,
"listings": [
{
"id": "6121470",
"url": "/bostad/453126",
"booliId": "6121470",
"latitude": 58.5809718,
"listPrice": {
"raw": 1050000,
"unit": "kr",
"value": "1 050 000",
"formatted": "1 050 000 kr"
},
"longitude": 16.1869314,
"published": "2026-06-11 09:30:07",
"daysActive": 0,
"objectType": "Lägenhet",
"tenureForm": "Bostadsrätt",
"streetAddress": "Nelinsgatan 26",
"descriptiveAreaName": "Söder"
}
]
},
"status": "success"
}
}About the Booli API
Listing Search and Filtering
The search_listings_for_sale endpoint takes a required query parameter (a Swedish location name such as 'Stockholm' or 'Nacka') and optional filters including min_price, max_price, min_rooms, max_rooms, max_rent, and object_types (e.g. 'Lägenhet', 'Villa', 'Radhus'). Results are paginated via the page parameter and return an array of listing objects that include booliId, streetAddress, objectType, listPrice, and geographic coordinates (latitude, longitude). The search_sold_listings endpoint mirrors this interface for historical transactions, accepting the same query and page inputs.
Listing Detail and Photos
Once you have a booliId from search results, get_listing_detail returns the full property record: structured objects for rooms, listPrice, and livingArea (each with raw, formatted, value, and unit fields), plus objectType, tenureForm, streetAddress, constructionYear, and geographic coordinates. get_listing_photos takes the same listing_id and returns an array of image objects with id, primaryLabel, width, height, and alt text — useful for building property cards or detail views.
Area Statistics and Price Trends
get_area_statistics accepts a Booli area ID (e.g. '11' for Stockholm) and returns an areaInfo object containing a title, description, and an HTML-formatted market summary string. get_price_trends takes a property_id (the residenceId from a listing detail or a booliId) and returns an areaTrend object with periods (month ranges), a series array of named value sequences, type, and unit — representing how sold prices in the property's local area have moved over the past 12 months. A pricePercentageDiff object with a description field is also returned, though it may be null for some properties.
The Booli API is a managed, monitored endpoint for booli.se — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when booli.se changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official booli.se API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Build a Swedish property search tool filtered by price range, room count, and property type using
search_listings_for_sale. - Analyse historical transaction prices in a specific Swedish city or neighbourhood via
search_sold_listings. - Display a property detail page with structured room, area, price, and tenure data from
get_listing_detail. - Populate a photo gallery for a listing using image dimensions and alt text from
get_listing_photos. - Show 12-month local price trend charts for a specific property using the
seriesandperiodsarrays fromget_price_trends. - Generate area-level market summaries for Swedish locations using
get_area_statisticswith known Booli area IDs. - Track asking vs. sold price relationships by combining
search_sold_listingsresults withget_listing_detaildata.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 200 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
| Team | $300/mo | 20,000 | 300 req/min |
| Company | $1,000/mo | 100,000 | 500 req/min |
Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Booli have an official developer API?+
What does `get_listing_detail` return beyond what's in search results?+
get_listing_detail returns structured sub-objects for rooms, listPrice, and livingArea — each with raw, formatted, value, and unit fields — plus tenureForm, constructionYear, and precise coordinates. Search results return a flatter subset of these fields sufficient for list views but without the structured value objects.Can I filter sold listings by price range or property type the way I can with active listings?+
search_sold_listings currently accepts only query and page parameters — it does not support min_price, max_price, object_types, or room-count filters. Active listing search via search_listings_for_sale supports those filters. You can fork this API on Parse and revise it to add filter parameters to the sold listings endpoint.Does the API cover rental listings or new-development projects?+
How fresh is the listing data, and are all Swedish regions covered?+
query parameter. Rural areas with low listing volumes will return fewer results, not an error.