Mapaprop
BETA

DELETE /properties/{paId}

Deleting here does NOT take down your listings on the portals. The listings are yours, published with your own account on each portal. If you want to take them down, it is done on each portal.

Resource URL

DELETE https://property-api.mapaprop.com/property-v1/properties/{paId}

The paId is the one create returned. If you do not have it, list your properties.

Authentication

Authorization: Bearer <your token>.

curl -X DELETE https://property-api.mapaprop.com/property-v1/properties/01M3PTZ8YBMM5DSNW03WP8VD9E \
  -H "Authorization: Bearer $TOKEN"

The response

The response carries the clientRef, the same one you sent in the envelope. We return it on all six paths (verify, create, read, list, update and delete) so you can match it against your own database without having to remember which clientRef you asked with.

{
  "paId": "01M3PTZ8YBMM5DSNW03WP8VD9E",
  "status": "deleted",
  "deletedAt": "2026-09-29T15:20:11.482Z"
}

The property is left as status: "deleted". It stops appearing in the list, and looking it up returns it with that status.

It is idempotent

Deleting something already deleted responds 200 all the same, with yaEstabaBorrada: true:

{ "paId": "01M3PTZ8YBMM5DSNW03WP8VD9E", "status": "deleted", "yaEstabaBorrada": true }

You can retry without any risk of duplicating anything.

Errors

CodeWhen
401Token missing, expired or invalid
404That paId does not exist
409The property is processing its images

The 409

If create is still downloading the images, the property cannot be deleted:

{
  "status": 409,
  "error": "La propiedad está procesando sus imágenes",
  "detail": "Procesando 2 de 4 imágenes. No se puede modificar ni publicar hasta que terminen."
}

Check the GET and retry once images.status is no longer processing.