technical_objects.
technical_objects exposes 20+ fields in the live v1 schema (warranty, inspection, and
maintenance dates and flags). This page documents the key identifying, join, and reshaped
fields — see the API Reference tab for the complete, auto-generated field list.technical_objects
GET /v1/property/technical_objects — technical/metered installations at a property
(elevators, heating systems, meters, and similar equipment).
integer
required
Technical object identifier.
integer
required
Unique property identifier.
integer
Floor area the technical object is installed in, if applicable.
integer
Maintenance creditor responsible for the object. References
Stakeholder.creditor.string
Technical object number.
string
Object name.
string
Object type.
date
Installation/build date.
boolean
Whether this object represents a meter.
string
Foreign key into
Property.property_structure. New in v1, and populated conditionally:
only set for rows without a floor_area_id (currently a small minority); everywhere else
it’s null and floor_area_id remains the join key.There is no separate meter-reading endpoint. A
technical_objects row can represent a
meter, but this endpoint only returns the object’s master data (type, location,
responsible creditor) — not consumption readings.