Publication
Once the property is loaded and the portal account connected, this is where it gets published — and taken down.
All three operations go to the same route, and what changes is the method:
/property-v1/properties/{paId}/publication/{portal}
The three methods
| What it does | Scope | |
|---|---|---|
PUT | Publishes the property. Calling it again updates, it does not duplicate | {portal}:publish |
DELETE | Takes the listing down. Idempotent: if it was already gone, it still answers 200 | {portal}:publish |
GET | Asks the portal how the listing is doing: its URL, whether it is still online, the views. ⚠️ spends allowance | {portal}:publish |
GET/PUT …/positioning | Paying for position: the balance, the ceiling, where the listing stands and a simulation of the position you would get. ⚠️ spends quota, and the simulation costs one call per value | {portal}:publish |
All three use the same scope: whoever can publish can take down and look up.
And all three answer the same when the rejection is about the state of the ACCOUNT. If the
portal says it no longer recognises your client's account (409 portal_account_unlinked) or
that it has it blocked (409 portal_account_blocked), you receive it with the same
code on the PUT, the DELETE and the GET — so you do not have to write three readings of the
same fact.
⚠️ And in all three we leave your records as they were. A rejection of that kind says nothing about the ad: the portal did not even look at it. What changes is the answer, not what we claim about the ad.
📌 There is no fourth method for the property's STATE (reserved, sold, rented): it travels inside
the object and is applied within the PUT —
the property's state on the portal.
The GET on this route is not the one on /properties/{paId}.
That one reads what we already have stored and is free; this one asks the portal and spends a call
from the client's allowance. They are two different operations.
The portals
This table is the reference: the rest of the documentation is generic on purpose and sends you here instead of repeating one portal's figure as if it applied to all of them.
| Portal | {portal} in the route | Key in publication | Publishing |
|---|---|---|---|
| Zonaprop | zonapropapi | zonaprop | ✅ available |
| Argenprop | argenpropapi | argenprop | ✅ available — standalone listings and developments |
| Cabaprop | cabapropapi | cabaprop | ⏳ not yet |
| MercadoLibre | mercadolibreapi | mercadolibre | ⏳ not yet |
| Mapaprop | mapapropapi | — | ✅ available — see below: it is not an external portal |
Mapaprop is in the table but it is not an external portal, and that difference changes three
things: there is no account to connect (it is your client's account, the same one as the app), it
does not consume anyone's quota, and it has no key in publication because there is nothing to
configure. What it does have of its own: publishing there also publishes to the networks your
client belongs to, and unpublishing does not take down the listings on the external portals. The
details are in Mapaprop.
A portal has two names and they are not interchangeable. The route takes the API name
(zonapropapi); inside the publication key it
is the short name (zonaprop). If you cross them we tell you by name: inside publication you get
portal desconocido. Válidos: argenprop, zonaprop, cabaprop, mercadolibre, and in the route you get
portal_not_supported.
Today PropertyAPI publishes in Argentina. All four portals are Argentine or enabled only there: Argenprop and Cabaprop do not exist in other countries, and on Zonaprop and MercadoLibre the per-country enablement is a step we have not taken yet. If your client is not from Argentina you can still load and verify their inventory — what they do not have is a portal to publish to. Write to dev@mapaprop.com if you need another country: it helps us prioritise it.
"Not yet" applies only to publishing. Everything else already works on all four: you can connect the account, load the property and check it — the checker tells you, portal by portal, whether that listing would go out. That way you can have your integration ready before the portal is enabled.
What changes on each portal
| Zonaprop | Argenprop | Cabaprop | MercadoLibre | |
|---|---|---|---|---|
| How it connects | a link your client opens | a link or a credential — the link is the recommended path | credential (OAuth) | credential (OAuth) |
| The credential | there is none: the authorisation stays on the portal's side | you obtain it and we store it encrypted | same | same |
| Call allowance | 1,500 per month per agency | the portal defines it | the portal defines it | the portal defines it |
| Publication plans | named and queryable | does not use plans: subscription points, which the portal does not publish through its API | — | — |
Its own fields in publication | plan · branch · developmentCategory | advertiserId · visible | branchOfficeId | listingTypeId · condition · sellerContact |
| Developments | ✅ the units travel inside the development's publication: a single call | ✅ but each unit is published first and the development then takes them: the flow explains it | ⏳ not yet | ⏳ not yet |
| What a re-publish can change | not measured | everything but type — including the zone. The property type cannot be changed on a listing that already exists: you have to unpublish and publish again | — | — |
The allowance is the client's, not yours and not ours. They contract it with the portal, your integration spends it, and each portal defines it its own way — Zonaprop's figure is not the API's norm. Details of that case: Monthly allowance and limits.
Of those own fields, publication checks the type, not the presence: if you send advertiserId
as text it flags it, but it does not require you to send it. What each portal actually needs is what
the PUT tells you when it is missing — in its 409, with the field name. What each one means:
the publication key.
Each portal with a section of its own has its specifics there: Zonaprop · Argenprop · Cabaprop does not have a section of its own yet.
And the configuration
The publication key — the plan and the portal data that travel inside the object, so you do not have to send them on every call.
Before publishing
Three things, in this order:
- Your client's record — Clients
- Their portal account connected — Connect with a link or with the credential
- The property loaded, with its
paId— Creating properties