BETA

Connect with a credential you already have

Each of your clients needs to have their own portal account connected. This is the path for portals where you already have the credential: you logged in with the credentials your client gave you, or you completed their OAuth, and all that's left is to save it.

POST /connections

These endpoints are in development. Write to us at dev@mapaprop.com if your integration needs them.

Before you start

You obtain the portal account token. These endpoints do not perform the login against the portal: they save the credential your client already authorized you to use. Each portal has its own connection mechanism.

You need a scope for each portal. Scopes are granted when you register your application; write to us indicating which portals you'll be working with.

portal values

PortalValueRequired scopeHow you get the credential
ArgenpropArgenpropApiargenpropapi:connectlogin with your client's credentials
CabapropCabapropApicabapropapi:connectportal OAuth
MercadoLibreMercadolibreApimercadolibreapi:connectportal OAuth

It's case-insensitive: ArgenpropApi, argenpropapi, and ARGENPROPAPI are the same portal and the same connection. Responses always return the value in lowercase (argenpropapi), so don't be surprised if it comes back different from how you sent it.

The Api suffix matters: some portals also have an XML feed, and these endpoints are only for the API integration.

Zonaprop doesn't connect here. These endpoints save a credential you already have, and Zonaprop doesn't issue one: the real estate agency authorizes on the portal, and the authorization stays on their side.

To connect Zonaprop, request a link and send it to your client: Connect with a link. If you try it here, you'll get a 409.

Identifying your client: clientRef

clientRef is the identifier you choose for each of your end clients. It's 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 POST body).

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

One portal account = one owner

A single portal account can't be connected by two applications at the same time. If you try to register an account that's already connected by another application, you get a 409. This is what allows us to unambiguously route the queries that come in from the portal.

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).

FieldTypeRequiredDescription
portalstringyesSee portal values
portalAccountIdstring or numberyesAccount id on the portal. Case-sensitive
accountTokenstringyesAccount credential. Maximum 4096 bytes
clientRefstringyes*Your client id. *Can be sent via header
tokenExpiresAtnumber or nullnoExpiration in epoch, if the portal reports it
scopesGrantedarray of stringnoPermissions your client granted you. Up to 32
appMetaobjectnoYour own data. Maximum 8192 bytes serialized
curl -X POST https://property-api.mapaprop.com/connections \
  -H "Authorization: Bearer <YOUR_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{
    "portal": "ArgenpropApi",
    "portalAccountId": "310578",
    "accountToken": "<account credential>",
    "clientRef": "cliente-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,
    "appMeta": {}
  }
}

The accountToken never comes back out. It's stored encrypted and no endpoint returns it, not even encrypted. Save it yourself if you need it for something else.

After connecting

To check the status or disconnect, see Check and disconnect — it works the same for accounts connected through this path and for those connected with a link.

Errors

CodeerrorWhat happened
400portal is required / portal must be a non-empty stringThe portal is missing or isn't text
400Invalid JSON bodyThe body isn't valid JSON
400clientRef is required (header x-client-ref, query or body)The client isn't identified
400(several, with field)A field doesn't meet the format or exceeds a maximum
401UnauthorizedThe token is missing or invalid
403Missing required scope: argenpropapi:connectYour application doesn't have the scope for that portal
404Connection not foundThat client has no connection with that portal
409portal account already connectedThat portal account is already connected by another application
503Connection storage is temporarily unavailable (encryption backend)Temporary issue on our end. Retry

A 403 tells you exactly which scope is missing, and that text includes the portal as you sent it. If you see Missing required scope: argenprop:connect instead of argenpropapi:connect, the problem is the portal value, not your permissions.