Registered Dubai property sales and rental contracts as Property Finder shows them (Dubai Land Department records), 10 per page up to 50 pages: date, price, price per sqft, bedrooms, property type, off-plan or ready, unit number, area, building and community, and for rentals the contract start and end dates. Also returns the market insights for the location (average sale price and price per sqft with their yearly change, average new and renewed rents, ROI, transaction volume) and its sub-areas with their transaction counts (pass a sub-area's location back to drill down). Pass next_page back as page; it is null on the last page.
Every response includes credits_used: the credits this call cost.
Parameters
name
type
description
location
string
Location path: dubai (default), a community or building under it (dubai/dubai-marina, as sub_locations[].location gives), or a property type page (dubai/villas, dubai/2-bedroom-apartments). Example: dubai/dubai-marina
url
string
A propertyfinder.ae transactions page (https://www.propertyfinder.ae/en/transactions/sold/dubai/...), instead of location and type.
type
sold | rented
sold (default) or rented.
sort
newest | oldest | price_desc | price_asc
newest (default), oldest, price_desc, price_asc.
page
integer
Page number (1-50). Pass next_page from the previous response.
import os, requests
res = requests.get(
"https://api.api.sh/propertyfinder/v1/transactions",
params={"location": "dubai/dubai-marina"},
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/propertyfinder/v1/transactions");
url.searchParams.set("location", "dubai/dubai-marina");
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).
The fastest way to see the full response is the playground: it runs this endpoint with your account and shows the exact JSON.