Listing history for a property
listing_historyEvery marketing snapshot for a property: asking price over time, price reductions, days listed, status changes, agent, image count and whether it had a floor plan.
Same call over REST
Listing history/v1/listings/history/{uprn}Not connected yet? Connect your assistant. Sign in with your MarketCode account; no API key needed.
Reference
What listing_history answers
price_trajectory appears only when at least two snapshots carry a price. No listing at all is a real answer, not a failure — a property sold off-market or never advertised has none.
UK only.
Inputs
Before you call it
- uprn
- A UPRN is the Unique Property Reference Number every UK address carries. Narrow the address with address_autocomplete, which is free, then address_resolve returns the UPRN for 8 credits. property_summary and address_by_postcode return UPRNs too.
Example
An example call to listing_history
Use the MarketCode tool listing_history with {"uprn":"200003443835"} and show me the result.{
"uprn": "<string>",
"listings": [],
"count": 0,
"price_trajectory": null,
"note": "<string>",
"credits_charged": 0
}Shape only. This call returns licensed records, so the keys are real and every value is a placeholder of its type.
Inputs
Arguments listing_history takes
| Name | Type | Required | Description |
|---|---|---|---|
| uprn | integer | Yes |
Response
What comes back
| Field | Type |
|---|---|
| uprn | string |
| listings | array |
| count | integer |
| price_trajectory | null |
| note | string |
| credits_charged | integer |
Fields observed in the example response above; a field the example did not exercise is not listed.
Usage
How to run listing_history in your assistant
Ask your assistant in plain English, for example:
"Use the MarketCode tool listing_history for <address or area>.
Show the result and the credits charged."
The arguments the assistant will send, for the example on this page:
{"uprn":"200003443835"}The connect steps for Claude, ChatGPT, Codex, Cursor and Claude Code are on the MCP page.
Skills
Skills that use listing_history
- Valuation report: An indicative valuation for one address: the range, the comparables and adjustments, the index position, the EPC, flood and planning context, and the reasoning, with every figure cited to the tool it came from.
- Due diligence report: A property due diligence report: title and ownership, history, EPC and council tax, flood and designations, nearby activity, cross-source disagreements and the cross-reference findings that join them, with a traffic light.
Price and licence
What it costs, and where the data comes from
listing_history costs 3 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, from Property portals. A call that fails is not charged.
Credits are granted on sign-up and bought in packs; the pricing page lists every call.
Sources
- Property portals
Sale and lettings listings
Collected from publicly marketed listings · Great Britain
Related
Tools used with listing_history
- Resolve an address to a UPRN8 credits
address_resolveResolve free-text address to canonical record (UPRN for UK).Same product - Property summary4 credits
property_summaryOne-call summary of a property: what it is, what building it belongs to,Same product - Full valuation with back-seriesFree
valuation_fullFull valuation block for a property: the value and its range, a monthlySame product - Comparable properties6 credits
property_compsComparable properties in the same building or block, with missingSame product - Registered sales for a propertyFree
transactions_by_uprnAll HMLR Price Paid records joined to this UPRN, newest first.Same product - House price index seriesFree
market_index_seriesThe published house-price INDEX for one postcode district or local authority: the level per month (base period = 100), the forecast tail flagged, and provenance saying how the index was built.Same product
Glossary
Terms used here
- Asking price and asking-to-sold ratio: The price a property is marketed at, as against the price it sells for; asking leads sold by months and includes what never sells, and the ratio between them is a temperature gauge.
- Days on market: How long a listing has been marketed; MarketCode reports the age of live stock and the days to completion on matched sales, and is explicit that a true days-to-sale is not observable from portals.
FAQ
Questions about listing_history
How much does `listing_history` cost?
+
listing_history costs 3 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, from Property portals. A call that fails is not charged.
Do I need to resolve the address first?
+
Yes. listing_history takes a UPRN, not an address. Start with address_autocomplete (free) to narrow the address, then address_resolve (8 credits) to get the UPRN. An assistant with the MarketCode skills installed does both steps on its own.
Which assistants can run `listing_history`?
+
Any MCP client: Claude (claude.ai, Claude Desktop, Claude Code), ChatGPT in developer mode, Codex and Cursor, each documented on the MCP page. You sign in with your MarketCode account over OAuth; there is no key to paste, and the connection is read-only.
Where does the data come from?
+
Read from Property portals listings. Coverage is the UK.
Can I store or republish the results?
+
The response includes records we license from Property portals. 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 `listing_history` 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 listing_history in your assistant.
30-minute call. We'll connect your assistant live on a real address.