GET
List my matches

Overview

Returns the authenticated user’s mutual-match feed — every matches row where the caller is a participant and has not dismissed the match. Each entry surfaces the other user’s listing (the property the caller could swap into) plus the caller’s own saved state. A row exists only when both users pass each other’s hard filters (the matching engine persists mutual handshakes only), so every result here is a genuine two-way match. There is no public listing-browse endpoint by design — properties are only ever visible through match context, which prevents scraping. Results are sorted by score descending, then computedAt descending, and paginated with an opaque cursor.

Authentication

Bearer <accessToken> required. Scope: user. The caller must have completed onboarding and have an approved tenancy (requireOnboarded) — otherwise 403.

Path parameters

None.

Query parameters

Area scoping

The filters are chosen from the size of the box the caller sends: radiusMiles applies only on that last row when the point resolves to no borough.
Why a neighbourhood search must ignore the borough. Areas routinely straddle council boundaries. Kilburn is mostly Brent, not Camden — so scoping a “Kilburn” search to the borough its centre lands in filtered to a council with no listings and returned nothing, while searching “Camden” returned the whole borough, Kilburn included. Users search by area, not by council.Checked against a 75-area sample across Camden, Islington, Hackney and Tower Hamlets, 7 areas resolve to a different borough than the one they are commonly listed under — Highgate (Haringey), Kilburn (Brent), Tufnell Park (Islington), De Beauvoir Town (Hackney), Nag’s Head (Westminster), Newington Green (Hackney) and Millwall (Lewisham). Every one of them returned zero results under borough scoping.Why borough scoping is still kept for borough-scale picks. A borough’s bounding box is not the borough. Camden is a wedge, so its box clips Islington and Westminster at the corners — the bleed that made “Camden” show Islington results. Keeping the borough equality for boxes >= 3 miles preserves that fix.Why 3 miles separates them. Google returns neighbourhoods as sublocality with viewports of ~0.2–2.1mi, and boroughs as administrative_area_level_3 at ~4mi+ (Tower Hamlets is 4.06mi). Of the 75 areas sampled, all 75 fell below 3 miles.

Request body

None.

Response — 200 OK

Match summary object

Match tiers

matchTier buckets score into the label the app renders on the match card. The raw percentage read badly — a genuine mutual match with no overlapping optional features scores 0 and showed as “0% match”, which looks like a rejection even though every mandatory requirement was met on both sides. There is no “no match” tier: a matches row only exists when every hard filter passed on both sides, so GOOD is the floor. A browse/search listing that is not a match carries match: null (see the nearby endpoint) and the app labels that “No Match” itself.

Property object

Example response

Error responses

Side effects

None — this is a pure read.

See also

curl