Zonaprop

Zonaprop is one of the portals PropertyAPI publishes to. It has no endpoints of its own: you publish with the same methods as for any other portal, passing zonapropapi where the route asks for {portal}.

PUT    /property-v1/properties/{paId}/publication/zonapropapi
GET    /property-v1/properties/{paId}/publication/zonapropapi
DELETE /property-v1/properties/{paId}/publication/zonapropapi

Where to start

1 · Declare the clientClients — the agency's record, once per client
2 · Connect their accountConnect with a link — Zonaprop is connected with a link your client opens, not with credentials you send
3 · Load the propertyCreating properties · Check it first
4 · PublishPublishing — and the status of what the portal says
5 · Choose the tier (decided in step 4)On Zonaprop position is paid with the listing's plan, and the plan travels inside the publication — there is no later step. The plans your client has are in Your client's plans; the mechanism, in Paying for position

What is specific to Zonaprop

WhatWhere
🔴 The monthly allowance — 1,500 calls per agency, what consumes it and how it renewsMonthly allowance and limits
Your client's publication plans and how many are leftYour client's plans
How the account gets connected (with a link, not a credential)Connect with a link
Developments — one call publishes the parent and its unitsPublish a development
The enquiries people leave on the listingsLeads
Your client's users on the portal — to choose the listing's agentYour client's users

🔴 Your client has ONE single connection on Zonaprop

It is the first thing worth knowing, because it changes how you offer the service: Zonaprop allows a single connected system per agency. Two do not coexist.

If your client already publishes from another systemconnecting them through the API disconnects them from that one. Agree on it with them beforehand, not afterwards
If your client also uses the Mapaprop app and connects Zonaprop from therethat becomes the valid connection and yours stops working

That last case is the one that surprises the most, because nothing fails in your code: your calls start coming back rejected from one moment to the next, without you having touched anything.

What it looks like when it happens

The portal rejects the calls saying that this agency does not belong to your integration:

{ "code": "error", "message": "La inmobiliaria [...] no pertenece a la integracion ..." }

It affects everything at once: publishing, taking down, checking the status and reading your client's plans. If you see it on one call, you will see it on all of them.

What to do

Connect the account through the API again — Connect with a link. Your client opens the link, authorizes, and their account goes back to being tied to your integration.

If your client uses both, it is worth deciding which one publishes. Alternating between them means the latest connection switches off the previous one every time. It is not an API problem: it is how the account works on the portal.

Zones are not mapped through the API. We maintain the Mapaprop zone → Zonaprop zone mappings ourselves; you send your zone and we resolve the rest. If one of your zones is not mapped, the checker tells you before you publish. The location catalogues are in Zones.

The listing's agent, and when it costs you a call

On Zonaprop every listing has a responsible agent, and you can choose them when publishing by sending their email address in branch.agentEmail (Publishing).

🔴 That address must belong to a user that exists in your client's portal account. If you send a different one, Zonaprop does not return an error: it replaces it with the account administrator's and the publication returns 200. That is why it is worth checking the user list first.

And checking it does not have to cost you anything:

What you requestWhat you getQuota
GET .../customers/zonapropapi/usersAll users with their email address and role — which is all you need for agentEmail0 calls
The same, with ?detail=truePlus the agents' names and phone numbers1 call

The first one is enough to publish. The second is useful if you also want to send the agent's name and phone number on the listing, because the portal does not derive them from the email address: if you choose an agent and do not send the other two, the listing goes out with the details from your client's record.

The free level brings more people than the one that costs: the detail only exists for users with an agent role, so the administrator appears in the first one only — and that is precisely the one the portal uses when it does not recognise the address you sent.

Users are created in the Zonaprop panel, not through this API, and to appear on the list they must have an agent role assigned. If your client adds an agent to their CRM and does not add them on the portal, their email address will not work as agentEmail.