/rightmove/properties

POST /api/rightmove/properties

Price: 10 credits

Get full Rightmove property details by property ID (or property URL): address, price, transaction type, property sub-type, bedroom/bathroom counts, description, key features, images, floorplans, EPC graphs, coordinates, nearest stations, tenure, council tax band, size and the marketing agent.

How to use it

Fetch a single Rightmove property by numeric ID or a property URL. Returns one item with id, url, display_address, outcode/incode, country, latitude/longitude, transaction_type (sale/rent), channel, property_sub_type, property_phrase, bedroom_count, bathroom_count, price (numeric) and display_price with price_qualifier/secondary_price/price_per_sqft, let_available_date/deposit/let_type/furnish_type/minimum_term_months (rentals), description, key_features, image+images, floorplans, virtual_tours, brochures, epc_graphs, size (sqft/sqm min/max), tenure_type, years_remaining_on_lease, council_tax_band, annual_ground_rent/service_charge, nearest_stations, listed_at, is_published/is_archived/is_premium, contact_phone and agent (branch profile with phone and logo).

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• property string required — Rightmove property ID or a property URL containing it (examples: "174838280", "https://www.rightmove.co.uk/properties/174838280"; minLength: 1)

Response

• @type string (default: "RightmoveProperty")
• id string required
• url string nullable
• display_address string nullable
• outcode string nullable
• incode string nullable
• country string nullable
• latitude number nullable
• longitude number nullable
• transaction_type string nullable
• channel string nullable
• property_sub_type string nullable
• property_phrase string nullable
• bedroom_count integer nullable
• bathroom_count integer nullable
• price integer nullable
• display_price string nullable
• price_qualifier string nullable
• secondary_price string nullable
• price_per_sqft string nullable
• let_available_date string nullable
• deposit integer nullable
• let_type string nullable
• furnish_type string nullable
• minimum_term_months integer nullable
• description string nullable
• key_features array (default: [])
• image string nullable
• images array (default: [])
• floorplans array (default: [])
• virtual_tours array (default: [])
• brochures array (default: [])
• epc_graphs array (default: [])
• size_min_sqft number nullable
• size_max_sqft number nullable
• size_min_sqm number nullable
• size_max_sqm number nullable
• tenure_type string nullable
• years_remaining_on_lease integer nullable
• council_tax_band string nullable
• annual_ground_rent number nullable
• annual_service_charge number nullable
• nearest_stations array (default: [])
  • @type string (default: "RightmoveStation")
  • name string required
  • types array (default: [])
  • distance number nullable
  • unit string nullable
• listed_at string nullable
• is_published boolean nullable
• is_archived boolean nullable
• is_premium boolean nullable
• contact_phone string nullable
• agent object nullable
  • @type string (default: "RightmovePropertyAgent")
  • branch_id integer nullable
  • branch_name string nullable
  • branch_display_name string nullable
  • company_name string nullable
  • company_trading_name string nullable
  • display_address string nullable
  • phone string nullable
  • image string nullable
  • description string nullable
  • profile_url string nullable
  • properties_url string nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — Property not found (well-formed but nonexistent or removed listing) Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.