The property JSON object

This is the reference for what you send: which fields the property object has, which ones are required, what values each one accepts, and how to say "I don't have this data".

It is a reference for the object, not for an endpoint. To understand how a property is identified —why type and operation are stable keys and where their values come from— read The property model first.

The object you send

This is the complete object. Below is what is required, what is optional and what values each field accepts.

{
  "code": "DEV-V3-909181",
  "type": 6,
  "operation": 2,
  "title": "Hermoso departamento luminoso con excelente ubicación y amenities completos",
  "address": "Av. Santa Fe 4271",
  "mapLatitude": -34.5828,
  "mapLongitude": -58.4206,
  "zone0": 1,
  "zone1": 2,
  "zone2": 189,
  "description": "Excelente propiedad ubicada en zona premium con fácil acceso a transporte público, comercios y servicios. Ideal para vivir o invertir.\n\nCuenta con todos los servicios y amenities modernos. Perfecta para familias o inversión.\n\nUbicación estratégica con fácil acceso a centros comerciales, escuelas y transporte público.",
  "descriptionFormatted": "Excelente propiedad ubicada en zona premium con fácil acceso a transporte público, comercios y servicios. Ideal para vivir o invertir.\n\nCuenta con todos los servicios y amenities modernos. Perfecta para familias o inversión.\n\nUbicación estratégica con fácil acceso a centros comerciales, escuelas y transporte público.",
  "zipcode": "1684",
  "betweenStreets": "Entre Av. Pueyrredón y Av. Coronel Díaz",
  "urlWebExternal": "https://ejemplo-inmobiliaria.com/propiedad-dev",
  "conditions": "Contado",
  "yearsOld": 16,
  "totalFloors": 16,
  "apartmentsPerFloor": 3,
  "floors": 2,
  "buildingArea": 126,
  "landArea": 189,
  "ambiences": 2,
  "rooms": 3,
  "dependencies": 1,
  "bathrooms": 1,
  "toilettes": 2,
  "garage": 2,
  "currency": "USD",
  "price": 142410,
  "zone3": 973,
  "rented": false,
  "sold": false,
  "reserved": false,
  "suspended": false,
  "occupancy": null,
  "images": [
    {
      "url": "https://cdn.ejemplo.com/propiedades/909181/foto-1.jpg",
      "description": "Imagen principal",
      "main": true
    },
    {
      "url": "https://cdn.ejemplo.com/propiedades/909181/foto-2.jpg",
      "description": "Imagen 2",
      "main": false
    },
    {
      "url": "https://cdn.ejemplo.com/propiedades/909181/foto-3.jpg",
      "description": "Imagen 3",
      "main": false
    }
  ],
  "blueprint": {
    "url": "https://cdn.ejemplo.com/propiedades/909181/plano.pdf"
  },
  "videos": [
    {
      "source": "https://www.youtube.com/watch?v=dQw4w9WgXcQ",
      "description": "Recorrido"
    }
  ],
  "prices": {
    "expensesCurrency": "ARS",
    "expensesPrice": 500,
    "taxCurrency": "ARS",
    "taxPrice": 200,
    "paymentPeriod": 1
  },
  "altPrices": [
    {
      "description": "Alquiler por semana",
      "currency": "ARS",
      "price": 100000
    }
  ],
  "attributes": [
    {
      "locale": "es_AR",
      "country": "ar",
      "id": "accessible",
      "label": "Accesible",
      "group": "propertyAttribute",
      "group_sub": "label",
      "group_subtype": "ammenities",
      "type": "bool",
      "key_legacy": "accessible",
      "selected": true,
      "status": true
    },
    {
      "locale": "es_AR",
      "country": "ar",
      "id": "statusAverage",
      "label": "Estado Regular",
      "group": "propertyStatus",
      "group_sub": "status",
      "type": "list",
      "key_legacy": "8",
      "value": 8
    },
    // … and 42 more entries, one per property attribute
  ],
  "publication": { … }  // per-portal publishing configuration — see its own page
}

Photos, floor plan, videos and additional prices

They travel in the same JSON: you send a single object.

⚠️ The property's price and currency do not go here: they are fields of the property itself and are already listed above.

The attributes array

Each entry describes one piece of data. There are two families: the property's status (propertyStatus) and the attributes — amenities, orientation, heating type and so on (propertyAttribute).

[
  {
    "locale": "es_AR",
    "country": "ar",
    "id": "accessible",
    "label": "Accesible",
    "group": "propertyAttribute",
    "group_sub": "label",
    "group_subtype": "ammenities",
    "type": "bool",
    "key_legacy": "accessible",
    "selected": true,
    "status": true
  },
  {
    "locale": "es_AR",
    "country": "ar",
    "id": "statusAverage",
    "label": "Estado Regular",
    "group": "propertyStatus",
    "group_sub": "status",
    "type": "list",
    "key_legacy": "8",
    "value": 8
  }
]

The value you send is key_legacy: it is the same in every country. The id, the label and the value come from your country's catalog — where to get them is explained further down.

customerSource — where the client came from

Every response that carries the customer block also carries, at the root, where it came from:

The client is NOT part of this object

Until 2026-09-30 the customer block travelled in here. Not any more: the client is declared once per client and the properties inherit it.

👉 Clients — the POST /property-v1/customers, its fields, the customerId we return and the branch.

⚠️ If you send customer inside this object it is ignored — like propertyId, customerId and branchId. And with no client declared, the upload responds 400 with rule: account_required.

publication — how it gets published

Inside the same object travels a publication key with what each portal needs from your account and from your publishing choices. It is not a field of the property: it is how you publish it.

{
  "publication": {
    "api": {
      "argenprop": {
        "advertiserId": 99999,
        "visible": true,
        "token": "<tu-token-de-argenprop>"
      },
      "zonaprop": {
        "plan": {
          "plan": "SUPERDESTACADO"
        },
        "token": "<tu-token-de-zonaprop>"
      },
      "cabaprop": {
        "branchOfficeId": 42,
        "token": "<tu-token-de-cabaprop>"
      },
      "mercadolibre": {
        "listingTypeId": "gold_special",
        "condition": "used",
        "token": "<tu-token-de-mercadolibre>"
      }
    }
  }
}

The full reference is on The publication key.

Required fields

There are 26, plus the attributes array. Everything else is optional.

Most of them are individual fields:

Optional fields

How to say "I don't have this data"

An optional field you don't have is sent as null or not sent at all: for us it is the same thing.

What is not the same is sending 0. A 0 in an area, in the age, in the number of occupants or in a coordinate is stored as the number zero — that is, as data.

Where the values come from

The enumerated fields —type, operation, status, orientations, amenities— deliberately have no fixed list on this page: they depend on the country and change whenever a new one is added.

You request them here:

GET /property-attributes?country=AR

See the full endpoint reference

It returns, for that country, everything it accepts: the text key (pa_key), the value you send (pa_key_legacy), the translated label (pa_label) and the family (pa_group_subtype).

Verify before publishing

You can send your object and see what it produces, without creating anything:

POST /property-v1/properties/verify

It tells you whether the object is valid, which rules it breaks field by field, and what would happen on each portal. It is the same body as the creation call, without the write.

See also

• The property model — stable keys, per-country catalog, what you send and what we set
• GET /property-attributes — the value catalog
• POST /properties — the creation endpoint