Connect with a link
With some portals you cannot obtain your client's account credential on your own. The agency is the one who has to complete the step, and you should not have to handle their portal credentials.
For those cases you request a connection link, send it to your client, and they complete the step on a page of ours. When they finish, the connection is registered and you can publish on their behalf.
| Method | Path | Who calls it |
|---|---|---|
POST | /property-v1/connect-links | You, with your token |
GET | /property-v1/connect-links/{token} | The page your client sees |
POST | /property-v1/connect-links/{token}/confirm | The page your client sees |
The last two are public: they are used by the page, not by your application. They are documented so you understand the flow, not for you to call them.
These endpoints are under development. Write to dev@mapaprop.com if your integration needs them.
When to use this path and when not to
| Portal | How to connect |
|---|---|
Zonaprop (zonapropapi) | Here. Your client authorizes on the portal |
Argenprop (argenpropapi) | Here. Your client enters their integration credential on our page |
| Cabaprop, MercadoLibre | Portal connections — you obtain the token and store it |
Requesting a link for a portal that is not on this list returns 400.
The two modes, and what changes for you
The link response includes a connectMode field that states how that portal is connected:
authorize | credentials | |
|---|---|---|
| Portal | Zonaprop | Argenprop |
| What your client does | authorizes in a portal window | enters their portal username and password on our page |
| Who sees the credential | nobody: the portal asks for it on its own site | they enter it on our page; you never see it |
Nothing changes for your integration: you request the link the same way, send it the same way and check the status the same way. The page adapts to the portal on its own. The field is documented because it tells you what your client is going to see.
Before you start: declare your client
The link is issued for a client record that already exists. If you have not created it, you get 409.
That is because the link points to one agency, and its identity comes from the record — never from whatever your application sends.
How they end up identified to the portal depends on the portal: with Zonaprop the code is assigned by us when the record is created (MAPAPROP-PA-000123), and your client needs nothing in place beyond their account; with Argenprop the identifier is issued by the portal and we read it when connecting.
See Clients.
1. Request the link
| Field | Type | Required | Description |
|---|---|---|---|
portal | string | yes | zonapropapi or argenpropapi |
clientRef | string | yes* | Your client id. *It can be sent in the x-client-ref header |
curl -X POST https://property-api.mapaprop.com/property-v1/connect-links \
-H "Authorization: Bearer <TU_TOKEN>" \
-H "x-client-ref: cliente-42" \
-H "Content-Type: application/json" \
-d '{ "portal": "zonapropapi" }'
201 response:
{
"token": "x-_qM7tYl3TnjxIyxTCmX2Y6dfuD1uiSYO8VX3M3jZE",
"portal": "zonapropapi",
"expiresAt": "2026-10-08T17:51:44.000Z",
"url": "https://www.mapaprop.com/property-api/connect/zonapropapi/x-_qM7tYl3Tnjx..."
}
Use the url exactly as it comes. Do not build it yourself: if we move the page, the links you already sent would break.
The link is valid once and lasts 7 days. Once your client completes the connection, the link is consumed. To reconnect — for example if they disconnected — request a new one.
Requires the property-api-create scope.
2. Send it to your client
By email, through your panel, however you prefer. The page shows them the name of their agency so they can verify they are connecting the right account, and explains what they are about to do.
In both modes the connection is only considered done once the portal confirms it. With authorize we ask the portal whether the authorization was registered; with credentials we perform the login against the portal and read the account profile. It is not enough for the screen to say it went through.
3. Finding out that it finished
We do not notify you. Once your client completes the step, check the status:
curl https://property-api.mapaprop.com/connections/zonapropapi \
-H "Authorization: Bearer <TU_TOKEN>" \
-H "x-client-ref: cliente-42"
status: "active" means connected. That call does not consume portal quota: it reads our own record.
Your application's button
With this you can draw a single button that works both for connecting and for disconnecting:
| Step | Call | Does it consume portal quota? |
|---|---|---|
| Deciding which button to show | GET /connections/{portal} | no |
| Click on Connect | POST /property-v1/connect-links → open the url | no |
| Your client authorizes | — | yes, 1 |
| Click on Disconnect | DELETE /connections/{portal} | depends on the portal (see below) |
status: "active" → show Disconnect. revoked or 404 → show Connect.
What disconnecting does, exactly
Disconnecting is two things, and they happen in this order: the portal first, then us.
- We close the permission on the portal's side. The response tells you so in
remoteUnlink:"ok"it was closed ·"pending"we could not and it is worth retrying ·"skipped"that portal does not need the step. - We revoke the connection on our side, and this always happens — even if step 1 failed. A portal not responding does not leave you tied to an integration you asked to end.
| Portal | Does it consume your client's quota? |
|---|---|
| Zonaprop | yes, 1 — it is a per-agency route |
| Argenprop | no — its limit is per integration, not per account |
What it never does, in any case: take the listings down. The listings were published by your
client with their own portal account and stay published. The response says so explicitly in
externalListingsUntouched: true. If you want them down, unpublish them before disconnecting.
If you get remoteUnlink: "pending", call the DELETE again: it is idempotent and retries the
portal step. On Argenprop that retry will keep returning pending — once the connection is
revoked we no longer hold the credential needed to close the session — so what matters is the
result of the first call.
Look at status, not at whether the connection exists. GET /connections also returns revoked connections: we keep the record so reconnecting is possible. If your code does if (connections.length > 0) it will treat a client who disconnected as connected.
Request the link when your client clicks the button, not when you draw it. If you request it on every screen load, you generate links nobody uses.
For Zonaprop there is also: monthly quota and limits.
Error responses
| Code | When | What to do |
|---|---|---|
400 | The portal does not support this flow | Use zonapropapi or argenpropapi |
409 | You did not declare the client record | Create it with POST /property-v1/customers |
404 | The link does not exist | Check that it is complete |
410 | The link expired (7 days) | Request a new one |
409 not_authorized_yet | Your client has not completed the authorization yet | Have them finish the step on the portal |
409 portal_account_already_connected | That portal account is already connected through another integration | It has to be disconnected from wherever it is connected today. A portal account has a single owner |
The rest are resolved by your client on the page and never reach your application.
What your client sees
The page is ours, it carries neither your branding nor Mapaprop's beyond a footer, and it has no navigation: it does not invite them to go anywhere else. It shows the name of their agency and explains what they are about to do.
If it finishes correctly, it tells them they can close the window. If something fails, we tell them with the portal's own reason and let them try again.
Under no circumstances does the portal credential pass through your application. Depending on the portal:
- With Zonaprop your client enters it on the portal's site, in its own window: not even we see it.
- With Argenprop they enter it on our page, because the portal has no authorization screen: connecting means signing in. We use it once so the portal authorizes us, we store the permission it returns, and we do not store the password.
Argenprop issues integration credentials separate from the ones the agency uses to sign in to the site, in the xxxx@api.com format. If your client connects with the site ones, the connection is registered but publications fail due to permissions. The page warns them about it; if you see this reported, check which username they connected with.
That email also carries a number, which Argenprop calls IdAnunciante and also IdVendedor: they are the same thing. The page asks for it using both names, so your client will recognise it.
Argenprop may take down the listings your client had published through another channel. If they had been using the portal's panel or another CRM, the portal removes those listings when the account moves to being managed from a new system, so nothing ends up duplicated when things are republished. Argenprop does this, not us and not your integration.
Let them know before connecting, and plan on republishing their portfolio from your system. More detail: Argenprop.