Rightmove and Zoopla data from one API
The UK market is split between two portals and agents do not list on both consistently, so a single-portal feed is a partial market by construction. Both are here under one key, including the sold-price surfaces that make a valuation defensible.
Rightmove and Zoopla both run partner APIs for agents publishing INTO the portal, not for reading the market out of it. If you are not an agent feeding stock in, those programmes do not apply. This reads the public listing pages, no account needed.
What the two engines give you
- Rightmove
- location_search, search, property_detail, agent, similar, sold_prices
- Zoopla
- location_search, search, property_detail, sold_prices, property_history, agent, agent_search
- Both
- for-sale and to-rent, agent records, sold prices
- Zoopla only
- property_history — the listing's own past on the portal
Build a street-level view of one postcode
Resolve the location on each portal first; their location ids are not interchangeable.
- 1
POST /rightmove/v1/location_searchpostcode to Rightmove's own location id
- 2
POST /rightmove/v1/searchlive listings for that id
- 3
POST /zoopla/v1/location_searchthe same postcode, Zoopla's id
- 4
POST /zoopla/v1/sold_priceswhat actually transacted, for the asking-price gap
Live asking prices from both portals against real sold prices, for one postcode, in four calls.
Where the two sources genuinely differ
| rightmove | zoopla | |
|---|---|---|
| Location ids | Rightmove uses its own region identifiers | Zoopla's are different and not convertible — resolve on each side |
| History | sold_prices only | sold_prices plus property_history for the listing's own past |
| Agents | agent lookup | agent plus agent_search |