Retry the creation in Mapaprop
POST /property-v1/properties/{paId}/mapaprop
On the normal path you do not call it. If you are a Mapaprop customer and generated your token
from the app, the property is created in your account by itself: as soon as the image ingestion
finishes, without you asking for anything — see Mapaprop.
The result shows up in the mapaprop block of the
property GET.
This endpoint exists to retry when the creation was stopped and you already fixed the cause.
The mapaprop block
{
"mapaprop": {
"state": "synced",
"propertyId": 2619527,
"branchId": 1,
"message": "La propiedad existe en tu cuenta de Mapaprop con el id 2619527 (sucursal 1)…"
}
}
state | what happened | retry? |
|---|---|---|
pending | it has not run yet | no: wait |
synced | the property exists in the account | not needed |
rejected | the object has something Mapaprop cannot store | yes, after fixing it |
blocked | the account is not in a fit state | no: write to us |
unauthorized | a problem on our side | no: we are already on it |
exhausted | the automatic retries ran out | yes |
synced means the property exists, not that it is published. To publish it use
PUT /properties/{paId}/publication/mapaprop.
When it helps
When the state is rejected. The block tells you which field and why:
{
"state": "rejected",
"fields": ["currency"],
"message": "Mapaprop rechazó la propiedad: currency llegó como 1 (number) y Mapaprop guarda un código ISO. Mandá uno de: USD, ARS. Corregila con PUT …"
}
Fix the object with PUT /properties/{paId} and only then
retry.
When the property ended up synced but without its images. If the creation went through and the
accessories —photos, floor plan, videos— failed, the block says so in accessoriesMessage. In that
case the retry sends only the accessories: it does not create the property again.
The response
202 Accepted
{
"paId": "01M6Q16SAKDDD12YZ5RQKSN03G",
"reintentada": true,
"detail": "El alta en Mapaprop se está reintentando. El resultado aparece en GET /property-v1/properties/{paId}."
}
It is asynchronous: it answers right away and the result shows up in the GET. Do not wait for
the creation in this call.
The 409s
error | what it means |
|---|---|
already_synced | the property is already created and so are its accessories |
no_customer_id | your token did not come from a Mapaprop account: your properties live only in PropertyAPI |
not_consolidated | the images are still being processed. The creation fires by itself when they finish |
If you are not a Mapaprop customer —or generated the token some other way— this endpoint is of no use to you and the creation never fires. That is the normal case for an integrator that only publishes to portals.