Sourcing live listings
POST /v1/sourcing/live-listingsWhat is on the market RIGHT NOW in these postcode districts, each listing enriched against our own record of the property: asking price against our valuation (`asking_vs_avm_pct`, `discount_to_avm_gbp`), £/m², gross yield on both the asking and valuation bases, unexpired lease years, EPC with its retrofit gap, the designation flags, days listed, the agent, and a plain-language `signals` list.
Same call over MCP
Live listings enriched against our valuationsourcing_live_listingsAuthenticate with an API key from the API & MCP Hub. The same call is available as an MCP tool at the same price.
Reference
What POST /v1/sourcing/live-listings returns
There is NO total — a district holds far more archived listings than live ones, so counting them costs seconds while the page costs milliseconds. Read has_more and page with offset; never tell a user how many listings exist, only how many you fetched.
A listing enriches only where the portal's own UPRN match landed on a unit we hold; enrichment.n_with_valuation says how many of the rows that was, and the rest carry the listing's fields with null comparisons. UK only.
Request
Calling POST /v1/sourcing/live-listings
curl -X POST "https://api.marketcode.ai/v1/sourcing/live-listings" \
-H "Authorization: Bearer $MARKETCODE_API_KEY"
-H "Content-Type: application/json" \
-d '{"postcode_districts":"<postcode_districts>"}'Send your API key as a Bearer token. Every response carries credits_charged and credits_remaining.
Inputs
Parameters
This endpoint takes no path or query parameters.
Request body
| Name | In | Type | Required | Description |
|---|---|---|---|---|
| postcode_districts | Body | string[] | Yes | Postcode districts, e.g. ["SW11"] |
| channel | Body | string | No | One of: residential_sale, residential_rent, commercial_sale, commercial_rent, anyDefault: residential_sale |
| min_price | Body | integer | No | |
| max_price | Body | integer | No | |
| min_beds | Body | integer | No | |
| max_beds | Body | integer | No | |
| auction_only | Body | boolean | No | Default: false |
| new_homes | Body | boolean | No | |
| limit | Body | integer | No | Default: 50 |
| offset | Body | integer | No | Default: 0 |
Price and licence
What it costs, and where the data comes from
Sourcing live listings costs 2 credits per successful call over MCP and over REST, and the two surfaces share one credit balance.
The price covers licensed records in the response. A call that fails is not charged.
Credits are granted on sign-up and bought in packs; the pricing page lists every call.
Related
Endpoints used with Sourcing live listings
- Build cost: index, regional factor, estimateFree
build_costBuild cost for a scheme: the sector's cost index with its 1- and 5-year movement, the regional location factor (`region`: NATIONAL, LONDON, SOUTH_EAST — an error lists what is loaded), the editorial on-cost percentages (prelims, contingency, overheads & profit, professional fees) and, given `gia_m2` and `rate_gbp_m2` (your BCIS or in-house base rate, with `rate_period` in the series' own format, e.g. 2024Q1), an estimate: the rate carried through the index to the latest period, localised, multiplied out, with totals at low / mid / high on-costs. The £/m² benchmark leg says `not_available` until a tender benchmark is loaded — no rate is invented, and nothing here is a modelled number. UK only.Same category - Construction cost index seriesFree
cost_indexConstruction cost index series for a development appraisal's cost side: `basis` is tender (tender price indices), output (output price indices), deflator (the construction deflator) or labour. Optional `sector` (residential, commercial, industrial, infrastructure, all, …), `freq` (monthly | quarterly | annual) and an inclusive period window in the series' own format (2014Q1, 2014M01, 2014). Each series carries its base period and method. UK-wide; regional factors come with the site appraisal. UK only.Same category - Adjacent parcels, owners and the combined site2 credits
land_assemblyThe parcels adjacent to one parcel and who owns each — the first question of a site assembly. Returns each neighbour with its area, land use, constraints and registered proprietor, plus a `combined` block: total area in m² and hectares, the number of distinct owners, how many neighbours already share the subject's proprietor (the parcels needing no second negotiation), how many have no linked owner, and every constraint present across the whole assembly.Same category - Site appraisal dossier5 credits
site_appraisalEverything known about ONE site, assembled and judged — the site dossier.Same category - Owners in an area, ranked as an approach list2 credits
sourcing_offmarket_ownersWho owns the stock in an area, ranked as an approach list: units held here, total value and equity, average and longest years held, how many of their units are on a short lease or already on the market, company status, and the signals behind the rank. Pass a `strategy` to rank the owners of only the units that preset points at — the owners of short-lease flats in a borough, say.Same category - Owners of sourced parcels5 credits
sourcing_ownersResolve registered owners for parcels returned by `sourcing_search`.Same category
FAQ
Questions about Sourcing live listings
How much does `sourcing_live_listings` cost?
+
Sourcing live listings costs 2 credits per successful call over MCP and over REST, and the two surfaces share one credit balance. The price covers licensed records in the response. A call that fails is not charged.
How do I authenticate?
+
Send your API key as a Bearer token in the Authorization header. Keys are created in the API & MCP Hub, shown once and revocable. Every response carries the credits charged and your remaining balance.
Is there an MCP version?
+
Yes. The sourcing_live_listings tool on the MarketCode MCP server is the same call at the same price, signed in with OAuth rather than a key, so Claude, ChatGPT, Codex and Cursor can run it in a conversation.
Where does the data come from?
+
The answer is computed by MarketCode. Coverage is the UK.
Can I store or republish the results?
+
The response includes records we license. Use them in your own analysis, reports and products; bulk redistribution of the raw records or building a competing dataset from them is not covered. Ask us if you need a redistribution licence.
Does `sourcing_live_listings` change anything?
+
No. The tool is annotated read-only on the server, so it never writes to your data or ours and an assistant can call it without a confirmation step.
Try Sourcing live listings on a real address.
30-minute call. We'll provision a key and walk through the endpoint on your use case.