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",
"alreadyUnpublished": false,
"quota": { "remaining": 1479, "limit": 1500 } }
It is idempotent: call it as many times as you want
If the listing was already down, you still get a 200 — with alreadyUnpublished: true. That is not an error: the outcome you asked for was already in place.
This makes retrying always safe, even after a 502 where you do not know whether the takedown went through.
Errors
| Code | What happened | What to do |
|---|---|---|
404 | that property is not in your inventory | check the paId |
409 | the account is not connected to the portal | without a connection we cannot name the listing on their side |
502 | the portal rejected the takedown, or did not respond | if it did not respond, it may have been taken down anyway: retry |
Two 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.
Related
- Publish to a portal — the
PUT, and what happens when you call it again - The
publicationkey — what to configure inside the object