I am a Mapaprop customer

The other flows are written for an integrator: an app that publishes the inventory of other agencies. If you subscribed to Property API to automate your own account, the only "client" is you — and there are five things that work differently.

1 · your token        Settings > API Token           one click, never expires
2 · your record       POST /customers                once
3 · your portal       you connect your account       YES, again. See below
4 · you publish       POST /properties               branchRef = your branchId
5 · your enquiries    GET  /leads?portal=mapapropapi  your inbox, no allowance spent

1 · The token is not requested, it is activated

You do not register an app or wait for credentials: you subscribe to Property API and activate your API Token with one click from Settings > API Token. It is the same token as all your other API services and it never expires. How to do it: Property API Token.

2 · The record: yes, you declare it too

POST /property-v1/customers      x-client-ref: my-agency
{ "name": "…", "email": "…", "phone1": "…" }

You choose the x-client-ref and it is the same in every call of yours. We return our id (MAPAPROP-PA-000001), which is worth storing.

Why, if Mapaprop already has your data? Because this is what gets published as the ad's contact, and the API does not assume: you declare it once and it is explicit. Changing it later is a PUT to the same route.

3 · 🔴 The portal account is connected again

Even if you already publish on that portal from Mapaprop. The Property API connection is its own and separate from the one the web uses: they are two different paths to the same portal, and connecting one does not connect the other.

It works like it does for any client, and the portal defines which form it takes: with a link or with the credential.

4 · Your branches: send the branchId, nothing else

This is what gets simplest for you. Your branches already exist in your account, with their id and their name, so you declare nothing:

POST /property-v1/properties
{ "canonical": { }, "branchRef": 777 }

That number is your branch's, and you read it with GET /branches. No declaring, no naming.

And you can also manage them, all optional:

You want…You do
your code to talk about "centro" instead of a numberdeclare the mapping in branches
to create a new branchdeclare it with its data in PUT /customers and we return its id
to edit onePUT /branches/{branchRef}
to delete oneDELETE /branches/{branchRef}

You can name it by your ref or directly by its branchId: both ways work.

The data of a branch in your account lives in Mapaprop, and that has not changed. What changed is that you now have one more door to write it: the PUT above writes in Mapaprop, not a copy next to it. That is why there are not two versions of the same phone number — there is one single value and two ways to edit it, the webapp and the API.

What the record declares about a branch that is already linked is not published: when publishing, the contact comes from Mapaprop. The record is the mapping, not the data.

Deleting a branch moves its properties. Its properties, contacts, signs and users pass to another branch, and that cannot be undone. With 3 or more branches you choose which one with ?targetBranchRef=; with 2 they go to the main branch. The detail is here.

5 · Your enquiries: the ones in your own inbox, with a single call

🟢 Here you get something an integrator does not have yet: the enquiries that come into your Mapaprop account — through your website, your chat, the Mapaprop portal, or a portal that drops them in your inbox — are read with a single call.

curl "https://property-api.mapaprop.com/property-v1/leads?portal=mapapropapi&fromDate=20260101" \
  -H "Authorization: Bearer $TOKEN"
Spends no portal's allowancethe source is your own account, so paging costs you no calls
They carry the threaddata.questionId groups the conversation: stitch the messages together instead of opening one record per message
One-year windowper request. More than that returns 400 window_too_wide
And they also reach you on their ownif you declared a webhook, the same enquiries arrive through it without being requested

It works because your token belongs to a Mapaprop account, and that is the difference with an integrator. This source resolves the account from the token, so it returns your enquiries and not somebody else's. An integrator trying ?portal=mapapropapi gets 400 no_mapaprop_account: what serves them is the webhook.

The details are in the enquiries of a whole account.

And from there on, everything is the same

Publishing, the statuses, the enquiries and the takedown work exactly as in the other flows:

Your properties enter your Mapaprop account. Unlike an integrator's —which live only in Property API— yours are registered in your account too, so you see them on the web like any other. That is what makes the add-on worth it.