Skip to main content

Spatial search

The spatial search endpoints use PostGIS GIST indexes to return properties matching a geographic shape. Use these instead of area= filters when you have explicit map coordinates — they’re an order of magnitude faster on large queries. Required scope: spatial:read Cost: 1 request per call

Search within a viewport (bounding box)

Returns properties inside a rectangular bounding box. Designed for map-based UIs where users pan and zoom.

Request

Body parameters

Response

When clustered is true, the response includes cluster centroids instead of individual properties — zoom in to see them.

Search within a drawn polygon

Returns properties inside an arbitrary polygon. Use this for “draw on map” UIs.

Request

Body parameters

* Provide either polygon_coordinates or polygon_wkt, not both.
Coordinates are [longitude, latitude] (GeoJSON order), not [lat, lon]. This trips up most first-time users.

Search within a radius

Returns properties within radius_miles of a centre point. Equivalent to GET /api/v1/properties?lat=...&lon=...&radius_miles=... but slightly faster for large radii.

Request

Body parameters

Response

Same shape as viewport search, plus a distance_meters field on each property:
Properties are sorted by ascending distance from the centre point.

Common patterns

Find all properties around a London tube station

Search a custom catchment area