Search commercial properties to rent
View all Rightmove UK Property Search & Sold Prices endpoints →Search commercial rental listings with a required identifier obtained from auto-complete data[index].locationIdentifier. Optional query filters cover price bounds and price_type, size bounds and size_unit, comma-separated property_type values, search_radius, type_of_let, listing recency, parking and inclusion of let-agreed listings; page and sort_by are also accepted. Documented radius values are supplied without a distance unit, and no sort_by values or maximum page size are documented. An observed successful response was a JSON object with status=true, a string message, a data array of objects, and integer currentPage, resultsPerPage and totalResultCount fields. The partial, unverified documentation example additionally shows row fields including id, displayAddress, displaySize, heading, location.latitude/longitude, customer.branchDisplayName, and price.amount/currencyCode/displayPrices. Those row-level fields were not individually verified in the observed response metadata. Use returned pagination values for bounded traversal, retain the filters with any resume checkpoint, and allow inventory and totals to change between requests. A successful search does not certify current availability, legal use or comparable normalized rents.
API Features
Live API Demo
🔒 Sign in to try it live
Log in to call this API with your own API key. New accounts get 100 free credits — no card required.
Log in / Sign upNo active API key found. Create one in your Dashboard, then reload this page. Dashboard →
/api/project/rightmove/commercial-property-to-rent API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/rightmove/commercial-property-to-rent?key=<API_KEY>&identifier=REGION%5E274&search_radius=0.0'
Query Result
Use Cases
- Export commercial rental pages in bounded batches, saving the original filters and returned pagination metadata so a job can resume without claiming a fixed inventory snapshot.
- Build an occupier shortlist using location, price bounds, floor-area bounds and explicit size units, then review listing suitability separately.
- Run distinct office, retail and industrial research searches with documented property_type tokens while retaining each search's rent-basis and area-unit settings.
- Offer a leasing search form with optional parking, let-agreed inclusion and LongTerm or ShortTerm settings, without promising that returned premises remain available.
- Create a commercial map view from example location coordinates only when they are actually returned, keeping missing coordinate or size values visible as unknown.
Frequently asked questions
Where do I obtain the required commercial search identifier?
Call the auto-complete operation and use data[index].locationIdentifier as identifier. REGION^274 is the documented sample. A free-text address is not documented as a replacement for this token.
How do price_type and size_unit affect rental filters?
price_type accepts PricePerUnit or PricePerCalendarMonth. size_unit accepts SquareFeet, SquareMetres, Acres or Hectares. Preserve these selections with the numeric price and size bounds; the endpoint does not document a conversion or normalization guarantee.
Can one request include several commercial property types?
Yes. property_type is documented as a comma-separated string, for example Office,BusinessPark. Use the exact documented tokens, such as Warehouse, Shop or Restaurant, rather than sending display labels or a JSON array.
What response structure has been observed for commercial rental search?
The observed successful response contained status=true, a message string, a data array of objects and integer currentPage, resultsPerPage and totalResultCount fields. The additional row fields described in the partial documentation example, including id, displayAddress, location and price, were not individually confirmed by the saved response metadata.
How should a paginated rental export be resumed?
Use the numeric page parameter and inspect the returned pagination values. The observed request used page=1. Save the filters and traversal checkpoint, bound the amount of work, and account for changes to listings and totalResultCount rather than treating pages as a fixed snapshot.
Are radius units, sort values and recency durations defined?
The documentation lists search_radius values from 0.0 through 40.0 and added_to_site values 1, 3, 7 and 14, but does not define their units or durations in the supplied evidence. No accepted sort_by values are supplied. Do not invent units, sort tokens or time windows.