Taking things down
These are five different operations and they get confused often. The difference matters because only one of them removes the listing from the portal: the other four do not touch it.
| You want to… | You call | Does the listing leave the portal? |
|---|---|---|
| take a listing down from a portal | DELETE …/publication/{portal} | yes |
| take it down from your client's Mapaprop account | DELETE …/publication/mapapropapi | no — it leaves their site and their networks |
| disconnect your client's account | disconnect | no |
| delete your client's record | DELETE /customers | no |
| delete a property from your inventory | DELETE /properties/{paId} | no |
⚠️ Deleting a property from your inventory does not take its listings down either: it is the same rule as the others. If you want them down, take them down before deleting it.
📌 The second row only applies if your token came from a Mapaprop account — Mapaprop.
🔴 The rule, and it is a decision of ours, not a limitation
We never take a listing of your client's down on our own initiative. Not when disconnecting their account, not when deleting their record, not if they stop using the service.
That listing is published with your client's account on the portal, and the decision to take it down is theirs. We disconnect what is ours; their listing remains their listing.
What we do do when disconnecting is cut off our own access: we stop being able to publish or update on their behalf.
⚠️ This matters for your design. If your app offers "unlink from Mapaprop" and you assume that cleans up the portals, your client's listing will stay up — with the data frozen as of the last day you updated it. If you want it taken down, take it down explicitly first.
The order, if you want to leave everything clean
1 · take the listings down DELETE …/publication/{portal} ← one per property and portal
2 · disconnect the account
3 · delete the record (if applicable)
Skipping step 1 does not fail: it disconnects all the same and the listings stay published. That is why the order is a recommendation, not a requirement the system enforces.
🔴 Taking down a large development may also need more than one round
On portals where each unit is a listing of its own, taking the development down requires detaching each one before touching it — and that does not always fit in one call. When it does not, we tell you and the listing stays published: repeat the takedown and each round picks up where it left off.
And it stays published on purpose, not because of a failure: 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.
| Repeating is safe | the ones already detached are not touched again |
| Nothing is ever lost | while the takedown is incomplete, everything stays as it was |
| When it is done | when the response stops saying it came back incomplete |
Taking a listing down
DELETE …/publication/{portal} takes that listing
down from that portal.
- It is idempotent: if it was already gone, it answers fine all the same. You do not have to keep track.
- It is per portal: if you published on three, that is three calls. Taking it down from one does not touch the others.
- It spends one call from your client's allowance, like publishing.
- The property still exists on our side: unpublishing is not deleting. You can publish it again whenever you want, with the same identifier.
Do not unpublish a listing while the portal is still processing its publication. If you published and unpublished right away, the takedown will answer fine and the listing may come back online: the portal keeps working on what it had pending and finishes it after the takedown.
This happens mostly with large developments, where the portal works in deferred mode and the window is minutes long. The symptom is disconcerting: you take it down, you see it down for a while, and it comes back on its own.
Wait until the status stops saying it is being processed, and only then unpublish. If you try to publish again in the meantime, we will reject it as temporary — it is the same window.
Disconnecting the account
Disconnecting cuts off our access to the portal account. After that, publishing and updating are not possible until your client connects it again.
What we keep on purpose, and it is what makes reconnecting cheap:
- Which properties were published on which portal. On reconnecting, the state is recovered and corrected against what the portal actually says.
- The zone mapping. That data belongs to the system, not to the account: it is never deleted.
Deleting the client's record
DELETE /customers deletes what we hold about that client.
Their listings on the portals stay published — same rule as above.
It is the least reversible of them all: after deleting, setting that client up again means starting from scratch, portal connection included.
How each one answers if you get ahead of yourself
| If you… | |
|---|---|
| take down a listing that was already down | 200, no drama. It is idempotent |
| take down a listing on a portal you never published to | we tell you, and nothing is broken |
| disconnect an account that was not connected | we tell you, naming the portal |
| publish after disconnecting | the error says that account needs connecting, not "you lack permission" |
Related
- Unpublishing from a portal — the endpoint and its contract
- Checking and disconnecting · Deleting a client
- Setting up a client — the reverse path