Otodom new-build developments and their units
New-build developments in Poland on Otodom. Without url: a search of developments with the site's filters (location, price, area, price per m², build year, keywords, days since listed, radius, sort); each result has the summary fields of /otodom/v1/search plus construction state, estimated delivery (year and quarter), number of units, unit area range, unit rooms range and price from per m². With url (or id): one development with its description, state, start and finish dates, units in the project and listed, area and ceiling-height ranges, price from per m², floors, extra spaces, unit counts by rooms, location with coordinates, photos, video, the developer (name, page, logo, phones, address) and a page of its units: id, link, title, category, price, currency, price per m², area, plot area, rooms, floor, build year, finishing state, availability date, special offer, photos, floor plans and every characteristic, with the price, area and room facets. Pass next_page back as page; null on the last page.
Every response includes credits_used: the credits this call cost.
Parameters
| name | type | description |
|---|---|---|
url | string | An otodom.pl/pl/inwestycja/... (or /pl/oferta/...) development link from the search results: returns that development and its units. |
id | string | The development slug ending in -ID..., instead of url. |
location | string | Search: location path as in otodom.pl search links (voivodeship/county/commune/city[/district]). Default: all of Poland. Example: mazowieckie/warszawa/warszawa/warszawa |
transaction | sale | rent | Search: sale (default) or rent. |
price_min | number | Search: minimum price (PLN). |
price_max | number | Search: maximum price (PLN). |
area_min | number | Search: minimum area (m²). |
area_max | number | Search: maximum area (m²). |
price_m2_min | number | Search: minimum price per m². |
price_m2_max | number | Search: maximum price per m². |
build_year_min | integer | Search: built from (year). |
build_year_max | integer | Search: built until (year). |
keywords | string | Search: words in the description. |
days_since_created | integer | Search: listed within this many days (1, 3, 7, 14, 30). |
radius_km | number | Search: extra radius around the location (km). |
rooms | string | With url: only units with these room counts, comma-separated (1-10), e.g. 2,3. |
sort | price_asc | price_desc | area_asc | area_desc | relevance | newest | price_m2_asc | price_m2_desc | Sort order. Units (with url): price_asc (default), price_desc, area_asc, area_desc. Search: any of the values (default relevance). Example: price_asc |
limit | integer | Per page: search 24, 36 (default), 48 or 72; units 1-50 (default 50). |
page | integer | Page number, starting at 1. Pass next_page back as page; it is null on the last page. Example: 1 |
Every endpoint also takes fresh, raw, fields (see lean responses and caching).
Example
curl "https://api.api.sh/otodom/v1/investments" \
-H "x-api-key: $APISH_KEY" import os, requests
res = requests.get(
"https://api.api.sh/otodom/v1/investments",
params={},
headers={"x-api-key": os.environ["APISH_KEY"]},
timeout=120,
)
res.raise_for_status()
data = res.json() const url = new URL("https://api.api.sh/otodom/v1/investments");
const res = await fetch(url, { headers: { "x-api-key": process.env.APISH_KEY } });
if (!res.ok) throw new Error(`${res.status} ${await res.text()}`);
const data = await res.json(); Response
A JSON object with the fields described above, plus raw (the source's own data), cached, fetched_at and credits_used. Errors return {"success": false, "error": "…"} with the HTTP status (see errors). A lookup that ran but found nothing (404) costs the price above; refused calls and errors on our side are free (what's charged).