BETA

Unpublish from a portal

When you want the listing to stop being published at the portal, this takes it down.

It does not delete the property: it stays in your inventory and you can publish it again whenever you want.

DELETE /property-v1/properties/{paId}/publication/{portal}

Same scope as publishing ({portal}:publish), same paId, no body.

curl -X DELETE "https://property-api.mapaprop.com/property-v1/properties/01M3Z4MF6S817S9V8QADXFFXN3/publication/zonapropapi" \
  -H "Authorization: Bearer $TOKEN" \
  -H "x-client-ref: $CLIENT_REF"
{ "status": "unpublished",
  "portal": "zonapropapi",
  "paId": "01M3Z4MF6S817S9V8QADXFFXN3",
  "quota": { "remaining": 1479, "limit": 1500 } }

A takedown can come back incomplete, and that is a 200

{ "status": "partially_unpublished", "portal": "argenpropapi", "paId": "01M…",
  "detail": "La baja quedó incompleta por el presupuesto de la llamada…" }

It happens when the development has many units: taking it down requires detaching each one, and that does not always fit in one call. It is not an error —the portal rejected nothing— so it comes back as 200.

The listingstays published, on purpose
What to dorepeat the takedown. Each time it picks up where the last one left off
When it is donewhen status comes back as unpublished
How many roundsfew: a development with 50 units comes down in ~5, not dozens

🔴 The listing stays published because taking it down there would be worse. If we took it down with units still attached, the portal would delete those units. We prefer to leave it up and have you repeat.

If you take down a development, the response may bring the listing-by-listing count

A development is one call but several listings (the parent and its units). When the portal reports them one by one, we pass that count on to you in a development block, and the three numbers add up to the total: unpublished + withError + processing.

processing is not a failure: the portal accepted the takedown and is still working. It is separate from withError precisely so you do not read it as an error.

The full breakdown, with the example and the code lists, is in publishing a development.

It is idempotent: call it as many times as you want

If the listing was already down, you still get a 200. That is not an error: the outcome you asked for was already in place.

The response does not tell you whether this call took the listing down or it was already down, and that is deliberate: the portal does not distinguish the two — it answers the same in both cases. A field promising that difference would be a constant dressed up as information.

What you can look at is quota: if it went down, the call reached the portal.

This makes retrying always safe, even after a 502 where you do not know whether the takedown went through.

Errors

CodeWhat happenedWhat to do
404that property is not in your inventorycheck the paId
409the account is not connected to the portalwithout a connection we cannot name the listing on their side
409the portal no longer recognises your client's account as part of your integration (portal_account_unlinked)connect it again: request a link. Retrying the takedown does not recover it
409the portal has the account disabled or blocked (portal_account_blocked)write to us with the reference; retrying does not enable it, and the link with the portal is managed by us
502the portal rejected the takedown, or did not respondif it did not respond, it may have been taken down anyway: retry

Both 409s are about the state of the ACCOUNT, not of the ad, so we change nothing on your side: the ad stays as it was in our records. Once the account is unblocked, repeat the takedown.

Three things worth keeping in mind

  • It consumes quota. A takedown uses one of your client's portal calls, just like publishing does.
  • Unpublishing does not delete the property. It stays in your inventory and you can publish it again whenever you want with the same paId — the listing is recreated, not duplicated.
  • 🔴 A takedown while the portal is processing the previous publication does NOT cancel it. The 200 says the portal accepted the takedown, not that the listing ended up down: if it still had the publication pending —typical in developments with many units, which go deferred— it finishes it afterwards and the listing goes back online. It is the same window that produces the publish's 409 portal_processing. Measured on 2026-10-08 against Zonaprop: takedown 3 s after a deferred publish → online again ~2.5 min later. ⇒ Wait until processingState stops saying it is being processed (it comes in the status query) and only then unpublish.