These 4 endpoints (get-zone/get-operation/get-type/get-attribute) belong to Cabaprop v1, the version currently in production. Cabaprop v2 (still in test, cutover pending) resolves zone/type/operation differently: its own static crosswalk plus GET /api/v2/catalogs — it does not use these 4 endpoints. If you are integrating against v2, this page does not apply.
These 4 endpoints query an existing mapping between a Mapaprop identifier of your own and its Cabaprop equivalent (zone, operation, type/sub-type and attribute).
Unlike Zonaprop API > Mapping zone, there is no method to create new mappings. Zone mappings are pre-loaded with Mapaprop's own schema (zone0-zone1-zone2-0, where zone2 = CABA neighborhood), so these 4 endpoints are only useful if your application already knows those ids. For most integrations we recommend using the Cabaprop API > Location catalogs directly (neighborhoods, operation types, types/sub-types, attributes) to resolve the ids of the Property Object without depending on this mapping. If you need us to create a new mapping, write to us at dev@mapaprop.com.
Headers (for all 4 endpoints)
| Header | Required | Description |
|---|---|---|
Authorization | yes | Bearer <token> — Mapaprop token |
| Resource information | |
|---|---|
| Authentication | Required (Mapaprop token) |
| HTTP Method | GET |
| Response | JSON |
| Version | 1 |
Zone mapping (GET)
Resource URL
https://property-api.mapaprop.com/cabaprop/get-zone
Parameters - URL
| Key | Type | Required | Description |
|---|---|---|---|
brandZoneId | string | yes | Zone id, following the zone0-zone1-zone2-0 schema (zone3 is always "0"). |
Response
If there is no stored mapping, it responds 200 with {}. If there is:
{
"cz_brand_zone_id": "1-2-2-0",
"cz_brand": "mapaprop",
"cz_cabaprop_zone_id": "1234",
"cz_cabaprop_zone_name": "Palermo"
}
cz_cabaprop_zone_id may come as a single id ("1234") or as a comma-separated list ("1234,5678") when the zone corresponds to several adjacent Cabaprop neighborhoods.
Operation mapping (GET)
Resource URL
https://property-api.mapaprop.com/cabaprop/get-operation
Parameters - URL
| Key | Type | Required | Description |
|---|---|---|---|
brandOperationId | string | yes | Id of the operation in your application. |
Response
If there is no stored mapping, it responds 200 with {}. If there is:
{
"cz_brand_operation_id": "1",
"cz_brand": "mapaprop",
"cz_cabaprop_operation_id": "1"
}
Type / sub-type mapping (GET)
Resource URL
https://property-api.mapaprop.com/cabaprop/get-type
Parameters - URL
| Key | Type | Required | Description |
|---|---|---|---|
brandTypeId | string | yes | Id of the property type in your application. |
Response
If there is no stored mapping, it responds 200 with {}. If there is:
{
"cz_brand_type_id": "2",
"cz_brand": "mapaprop",
"cz_cabaprop_type_id": "3",
"cz_cabaprop_sub_type_id": "12"
}
Attribute mapping (GET)
Resource URL
https://property-api.mapaprop.com/cabaprop/get-attribute
Parameters - URL
| Key | Type | Required | Description |
|---|---|---|---|
attributeId | string | yes | Id of the attribute in your application. |
Response
If there is no stored mapping, it responds 200 with {}. If there is:
{
"cz_brand_attribute_id": "5",
"cz_brand": "mapaprop",
"cz_cabaprop_attribute_id": "9",
"cz_cabaprop_attribute_name": "Parrilla"
}
Errors (for all 4 endpoints)
| Status | Body | Cause |
|---|---|---|
| 400 | {"error":"brandZoneId is required"} (or brandOperationId/brandTypeId/attributeId depending on the endpoint) | The required parameter is missing. |
| 500 | {"error":"Error querying Cabaprop <mapping>","detail":"..."} | Unexpected error in the query. |