GET /properties
Two ways: one property by its paId, or the list of yours.
One property
GET https://property-api.mapaprop.com/property-v1/properties/{paId}
The list
GET https://property-api.mapaprop.com/property-v1/properties
{ "total": 12, "items": [ { "…" } ] }
The list is for ONE clientRef, not for your whole inventory. It returns the properties of the
client you send in x-client-ref. For another clincy's inventory, ask with its clientRef. See
clientRef.
Authentication
Authorization: Bearer <your token>.
curl https://property-api.mapaprop.com/property-v1/properties/01M3PTZ8YBMM5DSNW03WP8VD9E \
-H "Authorization: Bearer $TOKEN"
The response
The response carries the clientRef, the same one you sent in the envelope. We return it on all six
paths (verify, create, read, list, update and delete) so you can match it against your own database
without having to remember which clientRef you asked with.
The same thing create returned — object,
portals, summary — plus the image detail.
The portals are recalculated on every request. It is not a snapshot of the day you created the property: if we improve a portal's mapping, you see it here without posting anything again.
verdictAtCreation — the verdict from the day you created it
Besides portals — which is recalculated — the GET returns the verdict as it was the day you
created the property, with its date:
"verdictAtCreation": {
"at": "2026-09-29T21:52:43.549Z",
"argenprop": { "status": "fields_complete", "blockers": [] },
"zonaprop": { "status": "fields_complete", "blockers": [] }
}
To decide whether to publish, look at portals, not at this. The two coexist on purpose and say
different things:
portals | what the system would say today |
verdictAtCreation | what it said the day you created it, with its date |
verdictAtCreation is a historical record: it explains why a property created a month ago did or did
not pass, with the mapping that existed back then.
published — what is published on each portal
What publishing wrote on the other side. Until you publish, it comes back as null:
"published": {
"cabaprop": { "itemId": null, "remoteStatus": null },
"argenprop": { "itemId": "01M41AQNXYG4W4SEEEEPHEDNX4", "portalItemId": 20685478, "remoteStatus": "published" },
"zonaprop": { "itemId": "01M41AQNXYG4W4SEEEEPHEDNX4", "remoteStatus": "published" }
}
| Field | What it is |
|---|---|
itemId | The code we use to name the listing on that portal |
portalItemId | The id the portal gave the listing — see below |
remoteStatus | Its status: published, unpublished or error |
portalItemId — the portal's id, without spending quota
Some portals return the listing's id in the very response that publishes it. When they do, we store it and hand it to you here: it is the number the listing exists under in the portal's own panel, and the one their support recognises if your client writes to them.
| Portal | Does it come? | |
|---|---|---|
| Argenprop | ✅ | returns it on publishing |
| Zonaprop | — | its publication is identified by the code we send: it returns no id of its own |
You do not need to check the status to have it. It shows up as soon as you publish, and reading
it here is free. If your portal is not in the table, the field is omitted — it does not come back
as null.
⚠️ It can change during the property's life. On Argenprop, taking a listing down frees its code,
so publishing again creates a new listing with a different portalItemId. If you store the number
on your side, read it again after each publication.
And if you checked the status, url and remote too
When you use GET …/publication/{portal}, whatever the
portal answered is stored here. That way you can read it again without spending another quota
call:
"published": {
"zonaprop": {
"itemId": "01M41AQNXYG4W4SEEEEPHEDNX4",
"remoteStatus": "published",
"url": "https://www.zonaprop.com.ar/propiedades/clasificado/-60321762.html",
"remote": {
"portalItemId": 60321762,
"publicationState": "ONLINE",
"visits": 37,
"checkedAt": "2026-10-03T18:42:57.716Z"
}
}
}
| Field | What it is |
|---|---|
url | Where the published listing can be seen |
remote | Everything the portal said the last time we asked — the full detail here |
remote.checkedAt | How old this data is. If that is good enough, there is no need to check again |
url and remote do not appear until you check the status at least once. They do not come
back as null on purpose: a null would say "there is no status on the portal", and the truth is
"we have not asked yet".
There are THREE fields and they name the same listing in three ways. Worth keeping straight:
| Field | Whose it is | Where it comes from | Does it cost? |
|---|---|---|---|
itemId | ours — the code we published with | we build it | free |
portalItemId | the portal's | it answered on publishing | free |
remote.portalItemId | the portal's | it answered on checking the status | 1 quota call |
The last two name the same thing and should match. If they differ, the one in remote is older: it
says what the portal reported at its checkedAt.
⚠️ The url still needs the status — but for another reason: the id alone is not enough, we also
have to know how to build that portal's public address. Today we build it for Zonaprop; for Argenprop
not yet, so its url stays null rather than giving you a broken link.
mapaprop — the creation in your account
Only if you are a Mapaprop customer and generated your token from the app. The property is created in your account by itself when the image ingestion finishes, and this block says how it went:
{
"mapaprop": {
"state": "synced",
"propertyId": 2619527,
"branchId": 1,
"message": "La propiedad existe en tu cuenta de Mapaprop con el id 2619527 (sucursal 1)…"
}
}
The propertyId is the Mapaprop id, different from this API's paId: it is the one you use to
find the property in the app. The states (pending, synced, rejected, blocked, exhausted),
what each one means and when to retry are in
Retry the creation; the full picture, in
Mapaprop.
This is how you find out if something failed. The creation runs by itself and deferred, so the state is looked up here — we do not notify you through any other channel.
synced means the property exists in your account, not that it is published.
images and assets — the status of your images
images gives you the summary and assets the detail, one entry per image:
"images": { "status": "partial", "total": 4, "processed": 3 },
"assets": [
{ "n": 1, "slot": "image", "source": "https://tu-cdn.com/frente.jpg",
"url": "https://…/image-1.jpg", "ok": true },
{ "n": 2, "slot": "image", "source": "https://tu-cdn.com/living.jpg",
"error": "el host del origen no existe (DNS no resuelve) [ENOTFOUND]", "ok": false }
]
| Field | What it is |
|---|---|
slot | image or blueprint |
source | The URL you sent us |
url | Where it ended up. Only if ok |
error | Why it could not be downloaded. Only if not ok |
The images.status values and what to do with each one are in
POST /properties.
Errors
| Code | When |
|---|---|
401 | Token missing, expired or invalid |
404 | That paId does not exist |
The GET never returns 409: you can always look a property up, even while its images are being
downloaded. That is in fact how you follow the progress.
Related
- POST /properties — create
- DELETE /properties/{paId} — delete