Enquiries for a single property
GET /property-v1/properties/{paId}/leads?portal={portal}
Returns the enquiries for one listing, the one belonging to the property you specify.
To pull everything, use the whole-account method. Walking through your properties one by one spends one call from the allowance for each one, and with the other method they all come in a single call. This method is for when you want to look at just one — the detail view of a listing in your panel.
curl "https://property-api.mapaprop.com/property-v1/properties/01M41AQNXYG4W4SEEEEPHEDNX4/leads?portal=zonapropapi&fromDate=20260101" \
-H "Authorization: Bearer $TOKEN" \
-H "x-client-ref: cliente-42"
The parameters
portal | required | zonapropapi |
fromDate | from which date. YYYYMMDD, or optionally YYYYMMDD HH:mm:ss | if you omit it, the last 7 days |
toDate | up to which date, same format | no upper bound |
size | how many leads per page | 100 |
maxPages | how many pages we fetch at most | 20 |
Always send fromDate whenever you want more than the very recent. Without an explicit window the
portal uses one of its own, a very narrow one: the same listing that returns 8 enquiries with a fromDate
nine months back returns 1 without the parameter. If you omit it, the listing looks as though it had
almost no enquiries.
The response
{
"portal": "zonaprop",
"paId": "2605257",
"from": "20260101",
"to": "20260601",
"leads": [
{
"eventId": "evt_src_322337250",
"event": "lead.created",
"occurredAt": "2026-11-15T03:07:08Z",
"clientRef": "cliente-42",
"source": {
"source": "mapaprop",
"case": "zonaprop",
"subcase": "api",
"ids": { "messageId": null, "adId": "56801168", "contactId": "49474924", "actionId": "10" }
},
"data": {
"questionId": null,
"messageId": "322337250",
"direction": "incoming",
"message": "Hola, quería coordinar una visita",
"contact": { "name": "Lucía", "email": "lucia@ejemplo.com", "phone": "1156781234" },
"customer": null,
"property": { "propertyId": null, "paId": null, "code": "2605257___mapaprop" },
"raw": null
}
}
],
"total": 8,
"quota": { "remaining": 1346, "limit": 1500 }
}
It is the same shape as the whole-account method, plus the paId you requested.
This method does not exist for mapapropapi. That source is requested only
by account, because not every enquiry that arrives in a
Mapaprop account is about an ad — 16.9 % are not — and requesting them per property would leave
out precisely the ones that cannot be requested any other way.
Capabilities says so with byProperty: false.
The lead object, field by field, is in the introduction.
to only appears if you sent toDate, and it carries the value that was actually applied.
A toDate with no time is the end of that day. If you send 20261013, we take it as
20261013 23:59:59 so that the 13th is included, and we tell you so in warnings. The portal reads a
date with no time as 00:00:00, so a bare one would have left out the whole day. If you want a
different cut-off, send the time (20261013 18:00:00) and we honour it as is.
If the listing is not on the portal
This is not an error: it is 200, with an empty list and the reason.
{
"portal": "zonaprop",
"paId": "01M41AQNXYG4W4SEEEEPHEDNX4",
"from": "20260929",
"leads": [],
"total": 0,
"notPublishedOnPortal": true,
"detail": "Ese aviso no figura en esa inmobiliaria del portal, así que no tiene consultas. Puede que todavía no se haya publicado, que el portal lo haya dado de baja, o que esté publicado bajo otra cuenta.",
"quota": { "remaining": 1346, "limit": 1500 }
}
The portal tells us "that listing does not appear under this agency" and nothing more, so we cannot tell you which of the three reasons it is. We would rather name all three than pick one and risk sending you to look where it is not.
The property does exist in your inventory — if it did not, the response would be a 404.
The errors
| When | What to do | |
|---|---|---|
400 portal_required | ?portal= is missing | send it |
| 403 | you are missing the {portal}:leads scope | ask us to grant it |
404 property_not_found | that paId is not in your inventory | check the id. It does not spend allowance: we stop before asking the portal |
409 portal_not_connected | that account is not connected to that portal | connect it |
409 portal_account_unlinked | it was unlinked on the portal's side | it has to be connected again |
429 portal_quota_exhausted | the agency used up its monthly allowance | wait for the following month. The allowance is shared with publishing — see Zonaprop's allowance |
501 leads_not_supported | that portal does not offer this service yet | — |
502 portal_rejected | the portal did not answer or rejected the request | retrying is safe |
Before building the call, check which mode that portal supports.
Not all of them offer this service, and this way you find out as data instead of through a 501.