BETA

PUT /properties/{paId}

It is a FULL REPLACEMENT: you send the whole object, just like on create. Whatever you do not send gets cleared.

That is why the response carries a diff, and the fields that were cleared are listed separately in cleared.

Resource URL

PUT https://property-api.mapaprop.com/property-v1/properties/{paId}

Authentication

Authorization: Bearer <your token>. Requires the property-api-update scope.

curl -X PUT https://property-api.mapaprop.com/property-v1/properties/01M3PTZ8YBMM5DSNW03WP8VD9E \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d @propiedad.json

The body

The same object as create, complete, in canonical:

{
  "canonical": { "…the property object, whole…" }
}

The fields are in The property JSON object.

This is not a PATCH. Sending {"canonical": {"price": 230000}} does not change only the price: it deletes everything else. To change one field, take the object the GET returns, change that field, and send the whole object.

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.

200 OK. It is the create response — object, portals, summary — plus the acknowledgement and the diff:

{
  "paId": "01M3PTZ8YBMM5DSNW03WP8VD9E",
  "updated": true,
  "updatedAt": "2026-09-29T23:41:02.118Z",
  "status": "active",
  "diff": {
    "property": {
      "price":       { "from": 245000, "to": 230000 },
      "description": { "from": "Departamento de 2 ambientes en el corazón…(1240 ch)", "to": "…(1310 ch)" },
      "toilettes":   { "from": 2, "to": null }
    },
    "assets":  { "added": 2, "removed": 1, "unchanged": 7, "reordered": false },
    "cleared": ["toilettes"],
    "changed": 6
  },
  "images": { "status": "processing", "total": 9, "processed": 7 }
}

diff.property — which fields changed

One per field, with its previous value and the new one. Long text is summarised with its real length (…(1240 ch)) so the response stays readable.

images and blueprint do not appear here: they have their own block.

🔑 diff.cleared — what got cleared

The list of fields that had a value and no longer do. It is the consequence of the full replacement, listed separately so you see it at a glance.

If cleared mentions something you did not mean to clear, send the PUT again with that field included. Nothing has been published yet.

diff.assets — the photos

"assets": { "added": 2, "removed": 1, "unchanged": 7, "reordered": false }

They are compared by URL, not by position. Reordering your photos without changing them gives unchanged and reordered: true — it does not count as new photos.

FieldWhat it is
addedURLs that were not there before: these are the ones we download
removedURLs no longer in the object
unchangedThe ones that remain. They are not downloaded again
reorderedThe same photos in a different order. It matters: the first one is the main one

New images go through the same cycle

If the PUT brings new URLs, images.status goes back to processing and the property is locked while we download them — same as on create. The ones already hosted are not downloaded again.

What the PUT changes in your Mapaprop account

If the property is already registered in your Mapaprop account, the PUT propagates the change there: the title, the description, the area, the price and its history, the alternative prices, the videos, the floor plan and the photos. It is a single call: there are no separate endpoints for the price or for the photos.

Your object is the property's complete reality. What you send replaces what is in the account — including anything someone edited by hand from Mapaprop. If they corrected the price in the web app and you then send a PUT, the price from your object is what stays.

The same goes for the commercial state: if your object says the property is not sold, it stays not sold, even if the account had it marked as sold. Your system is the source.

Two things the PUT does not touch:

  • Publication. If the property was published, it stays published; if it was not, it stays unpublished. Publishing is a separate action.
  • What we resolve ourselves: the zone, and the URLs of the photos we already host.

How long until it shows in your account

The PUT answers as soon as the property is saved; the change travels to the Mapaprop account afterwards. Measured in production: about 8 seconds for a change that carries no new photos.

If the PUT carries new photos, we download them first — images.status tells you how that is going — and the change reaches the account once that processing finishes.

Those seconds are a reference, not a guarantee: they depend on how many photos you send. The signal that rules is the GET, not a clock — if the mapaprop block carries update with status: "pending", the change is still on its way; if it carries status: "failed", it did not arrive and it tells you why.

Developments: the units are replaced too

If the object is a development, the development.units list rules like everything else:

units in your objectWhat happens
not sentthe linked units stay as they are
[] (empty list)all of them are unlinked
[A, B]exactly those two stay linked

Unlinking a unit does not delete it: it is still a property of yours, it just stops belonging to the development.

Photos: absent is not the same as empty

images in your objectWhat happens
not sentthe photos stay as they are
[] (empty list)all of them are deleted
[a, b]exactly those two remain, in that order

New photos are downloaded before they reach the account, so the change shows up once that processing finishes. The ones already hosted are not downloaded again.

You just registered the property: wait for the registration

A PUT fired within seconds of the POST collides with the registration, which is still writing the prices and the photos into the account. In that case we return 409 registration_in_progress with retryAfterSeconds: retry the PUT once those seconds have passed.

{
  "error": "registration_in_progress",
  "detail": "La propiedad se está dando de alta en Mapaprop en este momento…",
  "retryAfterSeconds": 8
}

To avoid the retry, wait until the GET returns the mapaprop block with state: "synced" and accessories before sending the PUT.

Errors

CodeWhen
400 canonical_missingcanonical is missing from the body
401Token missing, expired or invalid
403 missing_scopeThe property-api-update scope is missing
404That paId does not exist, or it is deleted
409Another property of yours already uses that code — the code is unique per account. We return the paId of the one that has it
409images_processing — the property is processing its images
409registration_in_progress — the Mapaprop registration is still writing. Retry once the retryAfterSeconds have passed

A PUT on a deleted property returns 404: it does not bring it back. To have it again, create it anew — you will get a new paId.

What the PUT does NOT do yet

It does not republish on the portals. It stores the property and tells you what changed, but a listing already published on a portal is not updated on its own. That comes with the publishing step.