Get Rightmove data with one API

It is a type prefix, a caret and an id: REGION^87490 for London, OUTCODE^2522 for SW9, POSTCODE^1327582 for E14 5AB and STATION^2156 for Clapham Junction Station. STREET is the odd one out because its id is an opaque token rather than a number, as in STREET^Po8SVH56WnaE_XwZ9vjFYIG4IU7qSz_I for Shakespeare Road in Lambeth. Resolve one with location_search, or skip the step and pass free text as location: the search response echoes meta.location_identifier "REGION^87490" and meta.resolved_from "London" so you can see what it picked.

Measured across 218 live listings on 2026-08-27, the vocabulary that actually appeared was an empty string (the common case), "Guide Price", "Offers in Excess of", "Offers in Region of", "Fixed Price" and "From". The mix varies sharply by channel: 26 of 75 London sale listings carried "Guide Price", while "Offers in Excess of" appeared on 20 of 58 London commercial listings and only once in the residential sample. Note that "POA" is not a price_qualifier value at all, despite what most people expect. It lives in price_display.

Detect them on price_display and then ignore price_amount, because price_amount is not a real asking price on those rows. Measured on 2026-08-27, 11 of 85 London commercial listings had price_display "POA": an office at Alfa Laval Tower came back with price_amount 1, a land listing at One Page Street with 65,000,000 and an industrial unit with 10,500,000. Those are placeholders of wildly different scale, so any average or price filter that includes them is wrong. Gate on price_display == "POA" and treat the price as unknown.

count is what you received, result_count is the true market total, and pages_total is what Rightmove will actually let you page through. A Manchester furnished rental search with max_pages 3 returned count 75 (three merged pages of about 24), result_count 3,342 with result_count_display "3,342", pages_total 42, duplicates_skipped 0 and stop_reason "max_pages". Note that 42 pages of 24 is roughly 1,000, which is Rightmove's result ceiling, not the 3,342 total. To reach deeper inventory you narrow the search with a smaller radius or a tighter price band rather than paging harder, and result_cap_hit tells you when you have hit the wall.

No, and this one bites. Residential rows returned ids like 92186892 and 148711631, but commercial rows returned 15-digit ids: 760770556763601, 733927782766401 and 758381082588465. Store property_id as a string. A 32-bit integer column overflows on commercial stock, and while JavaScript's Number handles 15 digits, you lose nothing by keeping them as text since that is what property_detail accepts anyway.

Beyond the price itself, three fields diverge. Rental rows carry price_frequency "monthly" (74 of 75 measured, with one "weekly") and a price_display formatted as "£1,850 pcm", tenure null, and fees_apply true with a fees_apply_text running to several kilobytes of the agent's tenancy fee schedule. Sale rows carry price_frequency "not specified", a real tenure value such as SHARE_OF_FREEHOLD or LEASEHOLD, and no fee text. The channel enum is buy, rent, new_homes, commercial_sale, commercial_rent and student, with aliases like for_sale, to_rent, lettings and new_build accepted. Unlike most parameters here, an unknown channel is rejected outright with the valid list rather than ignored.

A lot, though some of it is null more often than you would hope. Measured for property 148711631: living_costs with council_tax_band "H", sizings expressed in four units at once (0.21 ac, 836 sqm, 0.08 ha, 9,000 sqft), nearest_stations with types such as LONDON_UNDERGROUND and a distance in miles (Knightsbridge at 0.049), epc_graphs image URLs, floorplans, price_per_sqft, price_qualifier_message, tenure LEASEHOLD, street_view coordinates and agent{branch_id 271223, company_name REGENTS ESTATE HOLDINGS LTD}. On that same leasehold flat, years_remaining_on_lease, annual_service_charge and annual_ground_rent were all null: the fields exist, but agents frequently do not publish them, so treat them as optional rather than guaranteed.

Yes, through the agent action, which takes branch_id or branch_url and returns the branch profile plus that branch's live stock with max_pages paging. The branch id is discoverable from any listing: property_detail returned agent.branch_id 271223 with branch_display_name "Global 1, London" and company_name "REGENTS ESTATE HOLDINGS LTD", and search rows carry an agent block too. This is the usual route for agent-monitoring and competitor-stock tools, since it gives you one company's inventory without running a location search per area.

Rightmove API is a ReefAPI endpoint group for uk property listings for sale and to rent. It returns live JSON through POST requests under /rightmove/v1.

Yes. ReefAPI starts with 1,000 free credits, no card required. Rightmove calls use the same shared credit balance as every other ReefAPI engine.

No login to Rightmove is needed for the API response. You call ReefAPI with your x-api-key header, and the playground can run live examples before you create a production key.

The page example is captured from a live location_search call, and production requests fetch live data through ReefAPI rather than a static sample.

Rightmove actions currently cost 1-3 credits per successful call. Failed or blocked calls are free, and all APIs draw from one credit pool.

Yes. Connect ReefAPI once through MCP and your assistant can call rightmove actions with the same key, credit pool and JSON envelope used by normal REST requests.