Read straight from the database — the search index holds only what searching needs, so
nothing here comes from it. Use the id exactly as search returned it.
The id carries the track, in the form s_42 for a sales listing or l_42
for a lettings one. The two are separate tables with independent numbering, so id 42
exists in both and a bare number would resolve to whichever was guessed.
Visibility matches search. A listing is served only while it is live on the website
channel, so a listing that has been withdrawn stops resolving here at the same moment it
leaves the search results — an old URL cannot be used to reach it. Withdrawn, never
published, belonging to another agency and never having existed all return 404 and are
indistinguishable, so nothing can be inferred from the response.
Units carry their own status and price. One unit can be available while its
neighbour is under offer, so render per-unit rather than applying the listing's status
to the whole building. Statuses are numbers whose meaning depends on
transactionType; each carries a resolved label alongside it.
price is the headline range, aggregated the same way as the search result the
caller arrived from and annualised for rents, so the card and the page agree. For the
figures as the agent entered them, read buildingPrice and each unit's own price
with its rentFrequency.
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
