Portal connections

If your application publishes properties on portals through PropertyAPI, each of your clients needs to have their own account on the portal connected. These endpoints manage those connections.

Before you start

You are the one who obtains the portal account token. These endpoints do not log in against the portal: they store the credential your client already authorized you to use. Each portal has its own connection mechanism.

You need one scope per portal. Scopes are granted when you register your application; write to us stating which portals you are going to work with.

portal values

It is case-insensitive: ArgenpropApi, argenpropapi and ARGENPROPAPI are the same portal and the same connection. Responses always return the value in lowercase (argenpropapi), so do not be surprised if it comes back different from the way you sent it.

On Zonaprop the Api suffix matters: the portal also has an XML feed, and these endpoints are only for the API integration.

Identifying your client: clientRef

clientRef is the identifier that you choose for each of your end clients. It is opaque to us: it can be your internal id, a UUID or whatever you use. You send it in the x-client-ref header (or in the query, or in the body of the POST).

Your connections live in a space of their own: no other application can read them or touch them, and you cannot reach another application's either. That is determined by your token, not by what you send in the request.

One portal account = one owner

The same portal account cannot be connected by two applications at the same time. If you try to register an account that is already connected by another one, you get a 409. This is what makes it possible to route the inquiries coming from the portal without ambiguity.

POST /connections

Registers the connection. If you call it again for the same client and portal, it updates the existing connection (this is how you rotate the token).

curl -X POST https://property-api.mapaprop.com/connections \
  -H "Authorization: Bearer <TU_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{
    "portal": "ArgenpropApi",
    "portalAccountId": "310578",
    "accountToken": "<credencial de la cuenta>",
    "clientRef": "inmobiliaria-42"
  }'

201 response:

{
  "connection": {
    "portal": "argenpropapi",
    "portalAccountId": "310578",
    "status": "active",
    "scopesGranted": [],
    "createdAt": "2026-09-04T13:40:00.000Z",
    "lastActivityAt": "2026-09-04T13:40:00.000Z",
    "tokenExpiresAt": null,
    "providerMeta": {}
  }
}

GET /connections

Lists the client's connections. It only returns the portals you have scope for: if you work with Argenprop and your client also has a connection to another portal, that one does not appear.

curl https://property-api.mapaprop.com/connections \
  -H "Authorization: Bearer <TU_TOKEN>" \
  -H "x-client-ref: inmobiliaria-42"

200 response: { "connections": [ ... ] }, with the same fields as the POST.

GET /connections/{portal}

Returns one connection. 404 if that client does not have it.

DELETE /connections/{portal}

Disconnects the connection: we delete the stored credential and the account stops receiving inquiries from the portal through us.

It is idempotent: disconnecting something already disconnected responds 200 all the same.

{ "status": "revoked", "alreadyRevoked": false, "externalListingsUntouched": true }

Errors