Argenprop APIargenprop.com ↗
Search Argenprop property listings and locations via API. Filter by operation, type, bedrooms, price, amenities, and more. Returns up to 20 listings per page.
What is the Argenprop API?
The Argenprop API exposes 2 endpoints that cover Argentina's Argenprop real-estate portal. Use search_properties to query active listings with the full filter set the site offers — operation type, property type, location, rooms, price range, amenities, and more — and use search_locations to resolve free-text place names into the location_id values those property searches require.
curl -X GET 'https://api.parse.bot/scraper/afdbd229-5e16-49f0-84b6-5fb8d9b7bc2a/search_locations?query=Palermo' \ -H 'X-API-Key: $PARSE_API_KEY'
Looks up places (neighbourhoods, sub-neighbourhoods, cities, districts, provinces) that match a free-text name, in the same order the site's own location autocomplete shows them. One round trip. Each result carries a location_id of the form <level>:<code> (for example one shape is barrio:palermo) that search_properties accepts unchanged in its location parameter, plus the containing neighbourhood/city/district/province/country names and a bounding box. Returns an empty locations array when the site knows no matching place.
| Param | Type | Description |
|---|---|---|
| queryrequired | string | Free-text place name, partial names accepted (e.g. a neighbourhood or city name). |
{
"type": "object",
"fields": {
"query": "the query as sent",
"locations": "array of matching places, most relevant first",
"locations[].label": "display label as the site shows it",
"locations[].level": "hierarchy level of the place: subbarrio, barrio, localidad, partido, provincia or pais",
"locations[].bounds": "bounding box (north_lat, north_lng, south_lat, south_lng) in decimal degrees",
"locations[].location_id": "<level>:<code> identifier accepted by search_properties.location"
},
"sample": {
"data": {
"query": "Palermo",
"locations": [
{
"city": "CABA",
"name": "Palermo",
"label": "Palermo, CABA",
"level": "barrio",
"bounds": {
"north_lat": -34.549012,
"north_lng": -58.392987,
"south_lat": -34.597855,
"south_lng": -58.449044
},
"country": "Argentina",
"district": "Capital Federal",
"province": "Capital Federal",
"location_id": "barrio:palermo",
"neighborhood": "Palermo"
},
{
"city": "CABA",
"name": "Palermo Soho",
"label": "Palermo Soho, Palermo",
"level": "subbarrio",
"bounds": {
"north_lat": -34.549012,
"north_lng": -58.392987,
"south_lat": -34.597855,
"south_lng": -58.449044
},
"country": "Argentina",
"district": "Capital Federal",
"province": "Capital Federal",
"location_id": "subbarrio:palermo-soho",
"neighborhood": "Palermo"
}
]
},
"status": "success"
}
}About the Argenprop API
Endpoints and What They Return
search_locations accepts a free-text place name and returns an array of matching places ordered by relevance, mirroring the site's own autocomplete. Each result includes a label, a hierarchy level (one of subbarrio, barrio, localidad, partido, provincia, or pais), a bounding box with decimal-degree coordinates, and a location_id in <level>:<code> format. That location_id is what you pass to search_properties to scope a search geographically.
Property Search Filters
search_properties is the core endpoint. It accepts a wide range of optional filters: rooms (total ambientes, 1–5), bedrooms (1–5), garages (0–4+), bathrooms, price_min/price_max with a currency, street for address matching, age bracket, orientation, and more. Results are paginated at 20 listings per page via the page parameter. The response includes total (the site's match count), total_pages, has_more, and a results_url pointing to the corresponding public listing page.
Listing Fields
Each object in listings[] carries a price as an integer (null when the listing says "consult"), the currency it's quoted in, and an age text field such as 'A estrenar' or '2 años' when the listing publishes one. The response also returns resolved_locations (an array of {location_id, label} objects confirming which locations were matched) and an unresolved_location field that identifies any location the site did not recognise, so callers can detect and handle bad inputs cleanly.
The Argenprop API is a managed, monitored endpoint for argenprop.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when argenprop.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 argenprop.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 tracker for Buenos Aires neighbourhoods using
price,currency, andlocation_idfilters. - Feed a property-alert service by polling
search_propertieswith saved filters and comparingtotalacross runs. - Populate a location autocomplete widget in a third-party app using
search_locationswith partial neighbourhood names. - Analyse bedroom-to-price ratios across
partidoorprovincialevels by varying thebedroomsandlocationparameters. - Generate a map of listings by pairing listing coordinates with the bounding-box data returned by
search_locations. - Filter new-construction inventory by setting the
ageparameter to the site's 'A estrenar' bracket. - Compare asking prices on a specific street by passing a street name to the
streetfilter alongside a citylocation_id.
| 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 Argenprop have an official developer API?+
How do location IDs work, and do I need to look them up before searching?+
search_locations returns a location_id in <level>:<code> format for each matching place. You pass one or more of those IDs to search_properties via the location parameter to scope results. The level field tells you whether the place is a neighbourhood (barrio), sub-neighbourhood (subbarrio), city (localidad), district (partido), province (provincia), or country (pais), so you can pick the right granularity for your query.What happens when a location string is not recognised?+
search_properties response includes an unresolved_location field. When a supplied location is not recognised by the site, that field contains the offending item rather than returning a silent empty result. The results_url will be null in that case, making it straightforward to detect and handle the error in your code.Does the API return individual listing detail pages — floor plans, full photo galleries, contact info?+
search_properties returns listing summaries: price, age, rooms, and similar fields from the search results view. Full listing detail pages, photo galleries, agent contact information, and floor plan data are not exposed. You can fork this API on Parse and revise it to add a listing-detail endpoint that fetches those fields.Is coverage limited to Argentina, and does it include all property types the site lists?+
search_properties endpoint accepts a property_type filter that mirrors the site's own type list, but coverage of niche or newly added property categories depends on what the site indexes at query time.