Overview
The Properties API provides comprehensive endpoints for managing real estate listings. All property operations require authentication except for listing and retrieving individual properties. Base Path:/api/properties
List Properties
Query Parameters
Search text to match in property title or description
Filter by property types (casa, departamento, ph, terreno, local, galpon, oficina, campo, deposito, bodega, consultorio, fondo-comercio, hotel, cochera)
Filter by operation types (venta, alquiler, alquiler-temporal, permuta)
Filter by property status (activo, pendiente, vendido, alquilado, pausado)
Minimum price filter
Maximum price filter
Minimum number of bedrooms
Minimum number of bathrooms
Location search (city, province, neighborhood)
Page number for pagination
Number of items per page
Response
Indicates if the request was successful
Array of property objects
Pagination metadata
Usage Example
Fromsrc/pages/ListingsPage.tsx:112:
Get Property by ID
Path Parameters
The unique property ID
Response
Indicates if the request was successful
Complete property object with all fields, images, location, and metadata
Usage Example
Fromsrc/routes/propiedades.$propertyId.tsx:24:
Get Property by Slug
Path Parameters
The URL-friendly property slug
Response
Indicates if the request was successful
Complete property object
Usage Example
Fromsrc/routes/listings/p/$slug.tsx:23:
Create Property
Request Body
Multipart form data with the following fields:Property title (max 255 characters)
Detailed property description
Property price
Property type ID (from metadata)
Operation type ID (from metadata)
Number of bedrooms
Number of bathrooms
Covered surface area in m²
Property images (multiple files supported)
City name
Province/state name
Street name
Latitude coordinate
Longitude coordinate
Comma-separated feature IDs
Comma-separated tag IDs
Response
Indicates if the property was created successfully
Usage Example
Fromsrc/pages/PropertyFormPage.tsx:1154:
Update Property
Path Parameters
The property ID to update
Request Body
Multipart form data with fields to update (same structure as create endpoint, all fields optional).Response
Indicates if the update was successful
The updated property object
Usage Example
Fromsrc/pages/PropertyFormPage.tsx:1141:
Delete Property
Path Parameters
The property ID to delete
Response
Indicates if the deletion was successful
Confirmation message
Usage Example
Fromsrc/pages/AdminPage.tsx:113:
Add to Favorites
Path Parameters
The property ID to favorite
Response
Indicates if the property was added to favorites
Success message
Usage Example
Fromsrc/contexts/AuthContext.tsx:336:
Remove from Favorites
Path Parameters
The property ID to unfavorite
Response
Indicates if the property was removed from favorites
Success message
Usage Example
Fromsrc/contexts/AuthContext.tsx:349:
Error Responses
All endpoints may return the following error responses:Common Status Codes
200- Success400- Bad Request (invalid parameters)401- Unauthorized (authentication required)403- Forbidden (insufficient permissions)404- Not Found (property doesn’t exist)500- Internal Server Error
Related Documentation
- Users API - User profile and favorites management
- Metadata API - Property types, features, and tags
- Admin API - Administrative operations