Inmuebles24 APIinmuebles24.com ↗
Search Mexican property listings from inmuebles24.com. Filter by location, property type, and operation. Returns price, size, bedrooms, and more.
What is the Inmuebles24 API?
The Inmuebles24 API provides access to Mexico's leading property portal through a single search_listings endpoint that returns up to 30 structured listing objects per page, covering 12 response fields including price, currency, size in square meters, bedrooms, bathrooms, and parking. You can filter searches by city slug, property type, and operation type (rent, sale, or temporary), then paginate across the full result set using the max_pages parameter.
curl -X GET 'https://api.parse.bot/scraper/1f9c00cd-0e91-4ffa-b270-798554cb52ac/search_listings?page=1&sort=relevance&query=ciudad-de-mexico&max_pages=1&operation=renta&property_type=departamentos' \ -H 'X-API-Key: $PARSE_API_KEY'
Search for real estate listings by location, property type, and operation type. Returns structured listing data including price, features, structured location with coordinates, images, agency info, and URLs. Each page contains 30 listings (fixed by the site). Paginates by page number; use max_pages to control how many pages to fetch, or all_pages=true to auto-paginate through all results. When all_pages is true, pagination stops when a page returns fewer than 30 results or after 100 pages.
| Param | Type | Description |
|---|---|---|
| page | integer | Starting page number (1-based) |
| sort | string | Sort order for results |
| query | string | Location slug for search (e.g., 'ciudad-de-mexico', 'guadalajara', 'monterrey', 'puebla') |
| all_pages | boolean | When true, automatically paginates through all available result pages until results are exhausted (fewer than 30 results on a page or 100 pages max). When false, page and max_pages control pagination. |
| max_pages | integer | Maximum number of pages to fetch (ignored when all_pages is true) |
| operation | string | Operation type for the listing search |
| property_type | string | Property type slug |
{
"type": "object",
"fields": {
"page": "integer - starting page number",
"count": "integer - total listings returned in this response",
"listings": "array of listing objects with id, title, price, currency, price_text, maintenance, location, country, state, city, neighborhood, latitude, longitude, bedrooms, bathrooms, size_m2, parking, land_size_m2, age, description, image_urls, agency_name, agency_url, for_sale_or_rent, url, posting_type",
"pages_fetched": "integer - number of pages fetched",
"search_params": "object with query, property_type, operation used for the search",
"total_available": "integer or null - total listings available on site for this search"
}
}About the Inmuebles24 API
What the API Returns
The search_listings endpoint returns an array of listing objects, each containing id, title, price, currency, price_text, maintenance, location, bedrooms, bathrooms, size_m2, and parking. The response also includes count (listings returned in this batch), total_available (total matching listings on the site, when available), pages_fetched, and a search_params object echoing the query, property_type, and operation values used.
Filtering and Pagination
The query parameter accepts location slugs such as ciudad-de-mexico, guadalajara, monterrey, and puebla. The operation parameter distinguishes between venta (sale), renta (rent), and temporal (short-term/temporary). The property_type parameter accepts slugs including departamentos, casas, terrenos, oficinas, locales-comerciales, and inmuebles. Results are paginated at approximately 30 listings per page; use page to set the starting page and max_pages to control how many pages are fetched in a single call.
Data Shape and Coverage
Prices are returned as both a numeric price value and a formatted price_text string, alongside currency to distinguish MXN from USD listings. The maintenance field carries monthly HOA or maintenance fee data where listed. Location is returned as a text field from the listing itself rather than structured coordinates. Not all fields are guaranteed to be populated on every listing — bedrooms, bathrooms, and size_m2 depend on what the original listing author provided.
The Inmuebles24 API is a managed, monitored endpoint for inmuebles24.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when inmuebles24.com changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official inmuebles24.com API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Build a rental price index for Mexican cities using
price,currency, andlocationacross multiple pages ofrentaresults. - Compare apartment availability in CDMX vs. Guadalajara by running parallel
departamentossearches with differentqueryslugs. - Track new
ventalistings for a specific city over time by storingidfields and diffing results on a schedule. - Aggregate
size_m2andpricedata to compute price-per-square-meter estimates forcasasin Monterrey. - Populate a property search tool with structured listing data including
bedrooms,bathrooms, andparkingfor user-facing filters. - Identify commercial real estate inventory by querying
locales-comercialesoroficinasacross major Mexican metros. - Monitor
total_availablecounts for specific location and property-type combinations to spot supply trends.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 200 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
| Team | $300/mo | 20,000 | 300 req/min |
| Company | $1,000/mo | 100,000 | 500 req/min |
Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does inmuebles24.com offer an official developer API?+
What does the `search_listings` endpoint return for each listing?+
id, title, price, currency, price_text, maintenance, location, bedrooms, bathrooms, size_m2, and parking. The outer response includes count, total_available, pages_fetched, and search_params reflecting the filters applied.Are listing photos or contact details included in the response?+
How does pagination work, and is there a limit on pages fetched per call?+
page to the starting page number (1-based) and max_pages to control how many consecutive pages are retrieved. Each page returns approximately 30 listings. The total_available field in the response tells you how many total listings match your search on the site, letting you calculate how many pages exist.Does the API cover property listings outside major Mexican cities?+
query parameter accepts city and region slugs, so coverage depends on what inmuebles24.com indexes for that location. Smaller municipalities may have few or no results. The API currently exposes only the slugs available in the search — it does not include a browse-by-state or region-hierarchy endpoint. You can fork this API on Parse and revise it to add an endpoint that enumerates available location slugs.