Postal address of the property. Required before an order can be placed — it is where the creative is sent. Include coordinates: nothing on our side geocodes the text, so without them the property is stored at (0, 0), which loses distance-based creative routing and rejects a KEYS_PICKUP order at placement. On PATCH this object is merged sub-field by sub-field rather than replaced, so omitting coordinates keeps the stored ones: send them with every address change, or a moved property keeps routing creatives to its old location.

Which floors exist and how they are labelled.

Asking price of the property. Listing data only — it has no bearing on what Backbone charges for the shoot.

Descriptive keywords for the property. They are used as input to the marketing-text generation this API offers, so keep them customer-safe — internal codes or agent notes placed here can surface in the generated listing copy. Nothing in this API filters on them.

Surface area with its unit, e.g. { "value": 120.5, "unit": "SQM" }. Both parts are required and value must be greater than zero — a zero or negative value is rejected with a 400. Prefer this over the loose area / areaUnit pair.

Energy certificate: type (CONSUMPTION or DEMAND), year, consumption and demand in kWh/m²·a, validUntil, energyClass (A_PLUS is the "A+" class), co2Emissions in kg/m²·a, primaryEnergySources, includesWarmWater. Merged field by field, not replaced: sending one field leaves the others as they were, and there is no way to clear a field once set — so switching type from CONSUMPTION to DEMAND leaves the old consumption value in place.

Per-language marketing texts, each { languageCode, title, description, furnishingDescription, locationDescription, excerpt, otherDescription }. Sending this list replaces the whole stored set, so include every language you want kept — it is not merged language by language, and an empty list clears it. Every entry needs a languageCode, and two entries sharing one are rejected with a 400, compared case-insensitively (de and DE collide).

The property owner: { name, email, phone, organization }, every part optional. This is the actual owner, unlike ownerId / ownerReferenceId, which identify the agent. A contact you send replaces the stored one outright, so a partial contact drops the fields you leave out; omitting the field or sending null leaves the stored contact alone, and {} erases it. This is a third party's personal data and nothing else on our side removes it, so that empty write is how an erasure request is honoured short of deleting the property.

Who to contact about the sale. Same shape as objectOwner, though organization is only meaningful there. Replaces the stored contact outright, and is erased by an empty object as objectOwner is.

Who accompanies viewings. Note this is property-level reference data: the person the creative actually meets for a shoot is the order's organizationMethod contact, which is not taken from here.

Property categories, main category first (e.g. APARTMENT, LOFT, DETACHED_HOUSE, OFFICE, PARKING_SPACE). Replaces the stored list when sent.

Condition of the property, main condition first (e.g. NEW_BUILDING, FIRST_OCCUPANCY, LIKE_NEW, MODERNIZED, REFURBISHED, IN_NEED_OF_RENOVATION). Replaces the stored list when sent.

Flooring types present, as free-form values. Replaces the stored list when sent.

Prices under one shared currency: { currency, buy: { price, perSquareMeter, referring }, rent: { net, gross, extra, interval }, deposit }. Merged field by field on PATCH. currency (ISO 4217) is required when you add or change an amount and none is stored yet (400 otherwise), and it also re-stamps the currency of price. buy.price is the same stored value as price, and the other amounts share storage with the deprecated flat price fields.

Amenity and situation flags, most as APPLIES, DOES_NOT_APPLY or UNKNOWN (e.g. hasElevator, hasBalcony, isWheelchairAccessible), plus numberOfGarages and numberOfCarPorts. Merged field by field on PATCH: a flag you leave out keeps its stored value.

Ids of the departments handling the property in your system.

Portal / publisher configurations, each { id, options: [{ key, value }], promotions }. Replaces the stored list when sent.

Swiss register references: egid, ewid, egrid and minergieCertification (e.g. MINERGIE, MINERGIE_P, MINERGIE_A_ECO). Merged field by field on PATCH.

Land-register parcel numbers. Replaces the stored list when sent.

Parking offered with the property, each { type, count, price, listingType }; type is free-form (e.g. GARAGE). Replaces the stored list when sent.

Virtual tour links, at most 20 (400 otherwise). Entries that are not absolute http(s) URLs of at most 2000 characters are dropped rather than rejected. Replaces the stored list when sent.

Video links, at most 20 (400 otherwise). Entries that are not absolute http(s) URLs of at most 2000 characters are dropped rather than rejected. Replaces the stored list when sent.

Your own custom fields as a flat string-to-string map: at most 100 keys, keys up to 200 and values up to 2000 characters (400 otherwise). Stored and returned as given, never interpreted. Replaces the whole stored map when sent.