BETA

Publish and unpublish a development

A real estate development is published through its own resource, not through the one for properties:

PUT    /property-v1/developments/{paId}/publication/{portal}
DELETE /property-v1/developments/{paId}/publication/{portal}

Same scope as publishing a property ({portal}:publish), same paId — the development's.

Portal{portal} valueStatus
Zonapropzonapropapiavailable
Argenpropargenpropapiavailable
MercadoLibre, Cabaprop—the portal has no developments

⚠️ The two available portals treat units differently, and that changes your flow:

ZonapropArgenprop
The unitstravel inside the development's publicationare associated one by one, afterwards
For them to countdeclaring them in units is enougheach unit must be published as a listing first
Accepted typesanyonly Apartment, Retail, Office and Garage

In both cases you declare the same thing: units with the codes. We handle the difference — what changes is that on Argenprop an unpublished unit cannot be associated.

And on takedown the two portals do not behave the same

ZonapropArgenprop
What happens to the unitsthey go down with the development: they live inside itthe portal would delete them, so we dissociate them first and they stay published — on their own: they are no longer units of the development
What we returnhow many listings the portal took downthe ones we dissociated and, if one could not be, which is at risk

And we return it in the same shape for both, in a development block:

{
  "status": "unpublished",
  "development": {
    "action": "dissociated",
    "total": 3, "succeeded": 3, "failed": 0
  }
}
FieldWhat it says
actionwhat was done to them: unpublished (they went down with the development) or dissociated (they were dissociated so they do not go down)
total · succeeded · failedand the three add up: if they do not, a state is missing
failuresonly if there were any: [{ "code": "…", "reason": "…" }] — the reason travels where the portal gives one

One reason that does not come from the portal: skipped_no_budget. It means we did not call the portal for that unit — a call has a time limit and adopting units one by one does not always fit in a single one. It is not a rejection and it spent no allowance: repeat the development publish and it picks up where it left off. See publishing a development.

🔴 action changes what a failure means, and it is the opposite on each portal. With action: "unpublished", a unit in failures is still published. With action: "dissociated", it will be deleted by the portal. Same number, opposite outcome: read action before interpreting failed.

On Argenprop a unit that could not be dissociated will be deleted by the portal, which is why we name it. And if we cannot read which units it has associated, we do not take the development down: a takedown can be retried, a deleted listing cannot be recovered.

⚠️ And the units are left on their own, not "as before": they stop being part of the development. If your client publishes it again, they have to be declared in units once more.

If you ask for a development on a portal that does not support it yet, we answer 501 naming it — not a generic error. A portal can be available for standalone listings and not yet for developments.

This does not change how a development is created: you still create it with POST /property-v1/properties and its development group inside. What has its own resource is publication.

1. One call to the development, and what happens to its units depends on the portal

The development is always published with this call. What changes is where its units come from:

ZonapropArgenprop
The unitstravel in this same call: the portal receives the parent with its units insidehave to be published already; this call takes them and groups them
Before calling herenothing elsepublish each unit like any other listing

The full flow, with the order and the quota cost of each case, is in publishing a development.

curl -X PUT "https://property-api.mapaprop.com/property-v1/developments/01M3Z4MF6S817S9V8QADXFFXN3/publication/zonapropapi" \
  -H "Authorization: Bearer $TOKEN" \
  -H "x-client-ref: $CLIENT_REF" \
  -H "Content-Type: application/json" \
  -d '{ "plan": "DESARROLLOS_HOME" }'

Two requirements worth checking before you call

1 · At least one unit. An empty development is not published. Zonaprop states it literally — "the development will only be published if it has at least one unit"— and we reject it ourselves, before calling the portal: the attempt does not use up anything from your client's monthly allowance. verify tells you the same thing, and the counter is in units.total of the developmentStats, which comes with any response.

2 · A DEVELOPMENT plan that account actually has. The code is not fixed: it comes from the plans your client has contracted, and the ones for standalone listings do not work for a development. DESARROLLOS_HOME is a real example, not the value to copy — if you send one the account does not have, the portal rejects it and in the error we tell you which ones it does have available.

Why it matters: the portal has a call limit

Zonaprop allows 1,500 calls per month per real estate agency, and that limit is shared between publishing, checking status and fetching enquiries. For a development with 48 units the difference is this:

Unit by unitThrough the development
Publish49 calls1
Take down491

That is why the resource exists: walking through the units spends your monthly budget on a single development.

2. What we answer: unit by unit

The portal answers us with one entry per listing —the parent and each unit— and we pass it on to you summarised. This is what is most worth looking at:

{
  "status": "published",
  "portal": "zonaprop",
  "development": {
    "total": 48,
    "published": 45,
    "withError": 3,
    "codesWithError": ["TORRE-4B", "TORRE-5A", "TORRE-PH"]
  },
  "quota": { "remaining": 1432, "limit": 1500 }
}

A partial publication is not reported to you as a success. If the portal accepts the parent and rejects three units, the status is partial, withError is 3 and we tell you which ones by their code. If none go out, the status is failed.

The codesWithError are your codes (the code you sent, or the paId), not portal ids.

The development block appears when the portal reports listing by listing, which is the normal case for a development with units. If it answers without a body we can read, or reports a single listing, the block does not come — we would rather not send it than send it with numbers we did not read. status and quota always come.

Argenprop works differently: units are ASSOCIATED, not published with the parent

And the difference is not vocabulary — it is order, and it changes what you have to do:

ZonapropArgenprop
The unitstravel inside the development and the portal publishes themare listings of their own that must already exist
What publishing the development doespublishes themassociates them to the parent
Before publishing the developmentnothing🔴 publish each unit with PUT /properties/{paId}/publication/argenpropapi

That is why the block carries action, just like on takedown:

{
  "status": "published",
  "portal": "argenprop",
  "development": {
    "action": "associated",
    "total": 21,
    "succeeded": 18,
    "failed": 3,
    "failures": [
      { "code": "UF-102", "reason": "ENT001" },
      { "code": "UF-103", "reason": "ENT001" }
    ]
  }
}
FieldWhat it says
actionassociated — the development is online and these units were associated to it. We did not publish them
succeededthe ones that ended up associated: the new ones plus those already there
failed + failuresthe ones that did not end up associated, with the portal's reason

reason: "ENT001" means that listing does not exist in Argenprop yet. It is the most common case and it is almost always the order: referencing the unit inside the development object does not create it. Publish the unit first and repeat the development PUT — associating is idempotent.

The development stays published even if units fail, and that is on purpose: it lets you fix one unit without republishing everything. But then status: "published" is not enough — always read development.failed.

Listings the portal accepts "with remarks"

The portal can accept a unit and still say something — for example that a value came in empty and it set it to 0. That is not an error: the unit was published. We pass it on to you anyway, because it is usually the clue that one of your values is missing. Below is where to read it.

Why the portal complained, listing by listing — and it is FREE

The development block gives you the numbers. The detail of why we store for you and hand back in the read that costs no quota:

GET /property-v1/properties/{paId}
{
  "published": {
    "zonapropapi": {
      "remoteStatus": "published",
      "url": "https://www.zonaprop.com.ar/propiedades/clasificado/-60350743.html",
      "lastPublish": {
        "at": "2026-10-07T15:33:31.301Z",
        "total": 4, "published": 3, "withError": 1,
        "parentItemId": 60350743,
        "ads": [
          { "code": "DOME-TORRE", "portalItemId": 60350743, "isParent": true,
            "state": "ONLINE", "ok": true, "failureReason": null,
            "errors": [],
            "warnings": [
              { "code": "WARN-0213", "type": "WARNING",
                "text": "La caracteristica principal SUPERFICIE_TOTAL no puede ser NULL y se asigno 0 como valor default" }
            ] },
          { "code": "TORRE-4B", "portalItemId": 60350744, "isParent": false,
            "state": "OFFLINE", "ok": false, "failureReason": "errors",
            "errors": [{ "code": "ERR-0502", "type": "ERROR", "text": "La empresa tiene utilizados todos sus disponibles" }],
            "warnings": [{ "code": "WARN-0201", "type": "WARNING", "text": "El aviso no tiene imagenes." }] }
        ]
      }
    }
  }
}

These are the portal's own words, untranslated. We keep them from the very call that published, so reading them costs you nothing from your client's monthly allowance on the portal.

FieldWhat it is
atWhen we published. It is a dated record, not today's state
ads[].codeYour code (the code you sent, or the paId) — that is how you find it in your inventory
ads[].portalItemIdThe portal's id for that listing. Two different things
ads[].isParenttrue for the development, false for each unit
ads[].ok · failureReasonWhether that particular listing went out, and if not, why
ads[].errors · warningsThe portal's messages, {code, text, type}
parentItemIdThe development's id on the portal — the public url is built from it

How many units you see here depends on the path, and it is a portal limit.

The portal's acknowledgement carriesSo ads has
Up to 15 units (synchronous)one entry per listingthe development and every unit
16 or more (asynchronous)a single entry: the developmentonly the development

With 16 or more, by the time we answer you the portal has not processed the units yet: their messages do not exist yet, it is not that we do not read them. For those, query the unit as a standalone listing (GET /property-v1/properties/{paId}/publication/{portal}) — that does spend one call per unit.

status already tells you whether there were rejections (partial or failed — see publishing), and here is the why of each one: codesWithError says which ones failed and lastPublish what the portal said about each.

3. With more than 15 units, the portal processes in deferred mode

If the development has 16 units or more, Zonaprop does not process it on the spot: it acknowledges receipt and keeps working. In that case we answer:

{ "status": "received", "processing": "async" }

received is not published. It means the portal took it, not that it is already live. Do not store it as published until you confirm it.

While it is processing, it does not accept a second write of the same development. If you publish and publish again right away —to correct a field, for example— the portal rejects the second one, and we answer you 409 portal_processing with a retryAfter. It is not a failure and you did not lose the development: the first one carries on.

It is the longest window in the whole integration, precisely because here the portal works in deferred mode: the retryAfter of the 409 is 600 seconds for a batch, against 60 for a standalone listing.

🔴 And checking the status does NOT tell you whether you can write yet. The portal finishes with the parent listing long before it finishes with the batch, so the check answers about the listing and not about the lock: measured, the status said processed and the write kept being rejected for more than 5 minutes. Here waiting and retrying is what works — and it is also free, while checking spends one call of your client's allowance. The full contract is in publish.

The parent listing warnings you cannot avoid

When you publish a development, Zonaprop warns that SUPERFICIE_TOTAL, SUPERFICIE_CUBIERTA, HABITACIONES, MEDIO_BANO and GARAGE on the parent listing are empty and assigns them 0.

It is on the portal's side and there is nothing to change on yours. Zonaprop validates the parent listing as if it were a regular listing, but its development catalogue does not expose those characteristics: for development types the only one of that family it accepts is the total number of units. And the request body has no surface area fields. There is no way to send them.

The data does travel in each unit, which is a regular listing: its total area, its covered area, its unit of measurement, rooms, bedrooms, bathrooms, toilets and garages. That is where the buyer looks for them.

⇒ The parent's WARN-0213 are noise: the listing publishes anyway. Do not change the fields in the development group — they are used for the characteristics the portal does accept (units, floors, lifts, garages, commercial units, offices).

And now we tell you before you publish

Keep sending every field. The object is Mapaprop's, not a portal's: we ask you for all the data because that is what lets us publish on every possible portal. Zonaprop not using one does not make it useless — the data is stored and travels to the ones that do accept it.

omitted is information, not an instruction to remove the field. If you remove it, you lose compatibility with the other portals.

Said that: If you send a field from the group that this portal does not use, it comes back in omitted in the verify, with the reason and with where the data does live. There are seven:

FieldWhy it does not travel
totalBuildingArea · totalLandAreaZonaprop has no area characteristic for a development. Each unit's does travel
minAmbiences · minRooms · minBathroomssame: they do not exist for a development. Each unit's do travel
totalTowersit has no characteristic for number of towers
commercialTaglineit has no field for the development's commercial tagline

totalGarages does travel (as number of garages), and only on the vertical type — on a horizontal development it comes back in omitted because of the type.

⇒ Verify before publishing and you will not find out afterwards: the verify is free.

Units that are not available do not travel to Zonaprop

Zonaprop has no field for per-unit availability: if we send it a sold unit, it shows it to the buyer just like one that is for sale. So we do not send it.

What excludes it todaysold
What does NOT exclude it (yet)rented · reserved · suspended — undecided, not overlooked
How you find outin adjusted: one entry per unit, with its field and the reason. You see it in the verify, before publishing
The total (CANTIDAD_TOTAL_DE_UNIDADES)counts the excluded ones: a 100-unit building with 3 sold still has 100

The unit is not removed from your development: it stays in units[], it still counts for the aggregates, and it gets published again on its own if it stops being sold.

If every unit is marked as unavailable, the development cannot be published — Zonaprop needs at least one. We tell you that as the reason, not "add a unit": you already added them.

Not sending it does NOT take down a listing that was already published. If the unit was sold after you published it, take down its publication with DELETE …/publication/{portal} on that unit. Marking it affects future updates, not the listing that is already up.

4. Taking it down

curl -X DELETE "https://property-api.mapaprop.com/property-v1/developments/01M3Z4MF6S817S9V8QADXFFXN3/publication/zonapropapi" \
  -H "Authorization: Bearer $TOKEN" \
  -H "x-client-ref: $CLIENT_REF"

A single call takes the development and its units down. Same as with a property:

  • It deletes nothing: the development stays in your inventory and you can publish it again.
  • You can retry without worry: if it was no longer published, we still answer 200.
  • The units come down with it. Verified against the portal: when the development is taken down, each of its units goes offline with the same timestamp. You do not need to walk through them.
  • The plan returns to your stock, so you can reuse it on another development.
{ "status": "unpublished",
  "portal": "zonapropapi",
  "paId": "01M3Z4MF6S817S9V8QADXFFXN3",
  "quota": { "remaining": 1462, "limit": 1500 } }

When the takedown comes with a listing-by-listing count

If the portal reports each listing, we pass that count on to you — and the three numbers add up to the total:

{ "status": "unpublished",
  "portal": "zonapropapi",
  "paId": "01M3Z4MF6S817S9V8QADXFFXN3",
  "development": {
    "total": 5,
    "unpublished": 2,
    "withError": 1,     "codesWithError":  ["TORRE-4B"],
    "processing": 2,    "codesProcessing": ["TORRE-5A", "TORRE-PH"]
  },
  "quota": { "remaining": 1462, "limit": 1500 } }
What it means
unpublishedthey went offline
withErrorthe portal rejected that listing's takedown. codesWithError says which ones
processingthe portal accepted and is still working. It is not an error

processing is not a failure, and that is why it is separate from withError. If you take a development down while the portal is still processing a publication, the listing did not get to be offline yet — the takedown was accepted all the same. The three numbers add up to total, so you can always tell what happened to each unit.

The development block only comes if the portal answers listing by listing and there is more than one. When the takedown is total and the portal confirms it in one go, you will not see it: no information is missing, there is simply nothing to break down.

The codes in both lists are your codes (the code you sent or the paId), not portal ids.

If the portal does not list the units your object declares, we do not unpublish

In Argenprop, units are dissociated before taking the parent down, because the portal deletes the ones still attached to it. To do that we read its unit listing. If that listing comes back empty and your object declares units, the two sides contradict each other and we do not take the development down:

{ "error": "portal_unit_listing_mismatch",
  "detail": "El objeto declara 27 unidades y el portal no lista ninguna. …",
  "youCanFixIt": true,
  "declaredUnits": 27,
  "portalUnits": 0 }

Why we stop: if the portal really has none, taking it down would be harmless; if what happened is that we could not read its listing, taking it down deletes your units' listings, and that cannot be recovered. From here both situations look the same, so we pick the one you can retry.

How to continue: if the development no longer has units, declare it in your object — set development.units to [] — and retry the takedown. Your object is the source of truth, so that is how you state it.

Where you see a development's status

GET /property-v1/developments/{paId}/publication/{portal}

It asks the portal how the development is doing. Same method as for a standalone ad, on the developments resource — and it is what answers the status: received from section 3.

{
  "paId": "01M4B6DBK8AZDNSY1XA1E07E1T",
  "portal": "zonapropapi",
  "remoteStatus": "published",
  "inSync": true,
  "remote": {
    "processingState": "PROCESADO",
    "estadoPortal": "PROCESADO",
    "plan": "DESARROLLOS_HOME",
    "publishedAt": "2026-10-07T12:04:00.000Z",
    "unpublishedAt": null,
    "procesando": false,
    "unidades": { "total": 21, "codigos": ["01M4B6…___mapaprop", "…"] },
    "exists": true,
    "url": null,
    "checkedAt": "2026-10-07T18:22:10.144Z"
  },
  "quota": { "remaining": 1431, "limit": 1500 }
}

It spends one call of your client's monthly quota, same as publishing. The free snapshot of the last known state is in GET /property-v1/properties/{paId} → published.{portal}, with its checkedAt — a development is read on the properties resource, which is where the object lives.

The example above is Zonaprop's. The remote of an Argenprop development carries something different, because it is whatever each portal answers:

ZonapropArgenprop
The stateprocessingState + publishedAt / unpublishedAtpublicationState, with its own dictionary (VIGENTE · SUSPENDIDO · HISTORICO)
The planplandoes not report it
Whether it is shown—visible
Metrics—points, the listing's
The unitsunidades: { total, codigos }🔴 do not come: you query them through each unit's listing
procesandoyesdoes not report it

What does not change: remoteStatus, inSync, portalItemId, url, exists and checkedAt. Those hold on both portals, and they are the ones worth reading if you support both.

The deciding field is remoteStatus, not processingState. Zonaprop leaves the development at PROCESADO before and after taking it down, so that state does not tell you whether it is online.

remoteStatus is the verdict, and it is the same field on every portal and for listings and developments alike: published, unpublished, or null if the portal gave us nothing to decide with. The when is carried by remote.unpublishedAt.

If you were reading another field for this, see API changes.

The processing stages, in processingState:

ValueWhat it means
ESPERANDO_PROCESARthe portal acknowledged it and has not started yet
EN_PROCESOit is being processed right now
PROCESADOit finished with that ad

procesando is a shortcut: it is true for anything that is not PROCESADO, and also for a value that is not in the table — when in doubt, "still working". If you care about which stage it is at, read processingState, which is what the portal says uninterpreted.

processingState and estadoPortal are the SAME field, with the same value. processingState is the good name —the one a standalone listing already uses, so a single reader works for both resources— and estadoPortal is kept so as not to break whatever you may already be reading. If you are writing new code, use processingState.

For the units we give you how many and which ones, not each one's state: the portal does not include it in the development's response. For a single unit's state, query it as a standalone ad (/properties/{paId}/publication/{portal}) — but that is one quota call per unit.

FieldWhat it is
remoteStatuspublished · unpublished · null if the portal reported no publication
inSyncfalse = it changed on the portal without you asking. We do not republish it: you decide
remote.urlToday always null for a development: the portal returns no id to build it with. A broken link is worse than no link
exists: falseThe development is not on the portal (never published, or deleted). It is a 200, not an error

And you still have what you already had: the response of the publish and takedown calls themselves —the development block— worth storing because it is that moment's ad-by-ad account.

5. If you use the wrong resource, we tell you

A development through the properties resource —or a property through the developments one— is a 400, and the message tells you the exact URL:

{
  "error": "wrong_resource",
  "detail": "Ese objeto es un DESARROLLO inmobiliario (tiene el grupo `development`). Usá `/property-v1/developments/{paId}/publication/{portal}`.",
  "expected": "developments",
  "received": "properties"
}

We do not spend one of the portal's calls to tell you this: the check happens before.

It applies to all three methods, including the status query — and there it is what protects you from a false answer: if you ask about a standalone property using the developments resource, the portal replies that it does not exist (because it is not a development), and without this check we would tell you that your ad —which is perfectly published— went down.

Why the two resources exist: the portal has them separated as well, with different formats. If we sent a development through the path of a standalone listing, it would be published without its units.

6. Before publishing on Zonaprop

A development also needs to know whether it is horizontal or vertical. If your fields already say so, we work it out; if not, we ask you for it.

The development object — it is explained in its §4, with both cases.

7. Response codes

CodeWhat happened
200Published or taken down. Check development.withError before considering it closed
400 wrong_resourceYou used the resource that does not apply. The message names the right one
400 portal_not_supportedThat portal does not publish developments through here yet
409 portal_not_connectedThat agency does not have the portal account connected
409 portal_processingThe portal is still processing an earlier write of this development. It carries retryAfter: wait and retry
409 portal_unit_listing_mismatchYour object declares units and the portal lists none. We did not take the development down, so as not to delete your units' listings
422A value is missing to publish. We tell you which one, and whether you can fix it yourself
501The portal is supported for listings but not yet for developments

The development object — how it is declared and the unit rules

Verify before creating — try it out without publishing anything

developmentStats — the calculated numbers of its units

Publish a property — the resource for standalone listings