BETA

DELETE /properties/{paId}

Deleting here deletes the property in the Mapaprop account. It is the same deletion the webapp's Delete button performs: the record and everything attached to it are gone. It is not reversible.

But it does NOT take down your listings on the portals. The listings are yours, published with your own account on each portal, and we do not touch them. To take them down you have DELETE /publication/{portal} — and if you try to delete a property that is still published, we warn you first with a 409 that names the portals.

Resource URL

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

The paId is the one the creation 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 in status: "deleted". It stops appearing in the listing, and reading it returns it with that status.

If it is still published, we tell you first

Deleting a property that still has live listings leaves you in a split state: deleted here, published there. So the first attempt bounces and names the portals:

{
  "error": "published_on_portals",
  "portals": ["zonapropapi"],
  "detail": "Esa propiedad sigue publicada en zonapropapi. Despublicala primero con DELETE /property-v1/properties/{paId}/publication/{portal}, o repetí este borrado con ?force=true si querés borrarla acá y dejar los avisos como están."
}

You have two paths, and both are valid:

1 · Unpublish first (the usual way): DELETE /publication/{portal} for each portal on the list, and then the deletion.

2 · Force it, if what you want is to remove it from your inventory and leave the listings as they are:

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

The response tells you what is still published, so you can record it:

{
  "paId": "01M3PTZ8YBMM5DSNW03WP8VD9E",
  "status": "deleted",
  "forced": true,
  "portalsStillPublished": ["zonapropapi"],
  "detail": "Se borró de Mapaprop. Los avisos de zonapropapi siguen publicados: no los dimos de baja. Podés despublicarlos con DELETE /property-v1/properties/{paId}/publication/{portal} usando este mismo paId."
}

Forcing does not leave you without a way out: the deletion is reversible on the status side, so you can unpublish afterwards using the same paId. What we never do is take down a listing of yours unless you ask for it.

?force=true has to be exactly that. A force=1 or force=false does not force it: when in doubt we prefer to ask you to confirm rather than leave live listings behind without your having decided it.

And a portal left in error, or one you had already unpublished, does not count: only listings that are actually up will block you.

If the property has something live in Mapaprop, we also tell you first

Mapaprop does not allow deleting a property that has a live deal, an active rental, or is published on MercadoLibre. These are the same three conditions the webapp asks you to confirm before deleting, and here they arrive as a 409 that names them:

{
  "status": 409,
  "error": "blocked_in_mapaprop",
  "blockers": ["deal"],
  "precheck": { "hasDeal": true, "activeDealCount": 1, "activeDealStates": ["reservada"] },
  "detail": "Tiene una operación viva en Mapaprop. Si aún así querés borrarla, repetí el pedido con `?confirmed=deal` — es la misma confirmación que te pide la webapp antes de borrar."
}
blockerWhat is going onHow you proceed
dealit has a live deal?confirmed=deal
rentit has an active rental?confirmed=rent
mlit is published on MercadoLibre from Mapaprop?confirmed=ml
development_unitsit is a development with linked unitscannot be confirmed — unlink them first

To confirm several at once, separate them with a comma: ?confirmed=deal,rent,ml.

Confirming does not undo anything: it deletes all the same, with the deal or the rental inside. Only confirm if you know what is going away.

A development with units is different

That one cannot be confirmed, because there is nothing to accept: the units have to be unlinked first. You do it with a PUT sending an empty development.units, and then the deletion goes through normally:

PUT  /property-v1/properties/{paId}     → canonical.development.units: []
DELETE /property-v1/properties/{paId}   → 200

The units are not deleted: they remain as standalone properties in your inventory.

It is idempotent

Deleting something already deleted still responds 200, with yaEstabaBorrada: true:

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

You can retry without fear of duplicating anything.

Errors

CodeWhen
401Token missing, expired or invalid
404That paId does not exist
409images_processing (processing images), published_on_portals (still published on some portal) or blocked_in_mapaprop (something live in your account)
502We could not delete it in Mapaprop, so we did not delete it here either — retry

The three 409s

They are told apart by the error, which is a code: published_on_portals (live listings on portals), blocked_in_mapaprop (something live in your account) and the images one — if the creation is still downloading them, it cannot be deleted:

{
  "status": 409,
  "error": "images_processing",
  "detail": "La propiedad está procesando sus imágenes. Procesando 2 de 4 imágenes. No se puede modificar ni publicar hasta que terminen. El estado está en GET /property-v1/properties/{paId}."
}

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

And a 502 that is a guarantee, not a failure

If we could not delete the property in Mapaprop, we did not delete it here either:

{ "status": 502, "error": "mapaprop_delete_failed",
  "detail": "No pudimos borrar la propiedad en Mapaprop, así que tampoco la borramos acá: dejarte una mitad borrada sería peor. Reintentá en unos minutos; si sigue, escribinos." }

Retrying is safe: if by then it was already gone, the deletion completes all the same.