v1 Field Glossary

This glossary defines field names that appear on more than one /v1/ table documented in the v1 Data Model. Use it as a quick reference when joining across the /v1/ tables — several of these fields carry different meanings on different tables, which is exactly why they’re worth checking here first.

Field	Type	Description
`property_id`	integer or string	Unique property identifier; primary join key across every `/v1/` table. Type varies by table — integer on `booking_header`, `booking_positions`, `budgets`, `notifications`, `projects`, and `technical_objects`; string on `tenants`.
`person_id`	integer or string	Identifies a tenant or contact person. Not one identifier space — `booking_header.person_id`, `booking_positions.person_id`, `notifications.person_id`, and `tenants.person_id` come from different subsystems. Don’t join across tables on this field alone.
`creditor_id`	integer	Identifies a creditor (vendor or service provider). References the unversioned `Stakeholder.creditor` — there is no `/v1/` creditor endpoint yet. Unreliable on `projects`; see the Operations field reference.
`floor_area_id`	integer	References the unversioned `Property.property_structure` — there is no `/v1/` property_structure endpoint yet. Appears on `technical_objects` and `tenants`.
`account_id`	integer	Ambiguous across tables — not one join key. On `booking_positions`, the account the line item is posted to (FK into the unversioned `Accounting.accounts.account_hdr_id`). On `budgets`, renamed from the unversioned `account_hdr_id` and unrelated to `booking_positions.account_id`.
`property_structure_account_id`	string	Conditional fallback foreign key into the unversioned `Property.property_structure`, new in v1. Appears on `booking_header`, `booking_positions`, and `technical_objects` — populated only where the table’s primary join key doesn’t cover the row.
`cost_center_id`	string	Cost centre reference. Appears on `notifications` and `projects`; no `/v1/` cost-centre endpoint exists yet to resolve it against.
`booking_date`	date	ISO-8601 date of the ledger booking. Appears on `booking_header` and `booking_positions`.
`dms_link`	string	Link to the related document in the document management system, if attached. Appears on `booking_header` and `tenants`.

Fields prefixed with sk_ are internal surrogate keys used for joins in the underlying data warehouse. None of the tables documented under /v1/ currently expose one, but if you encounter one via the API Reference tab, don’t rely on it as a stable identifier.

Get Started

Core Concepts

Guides

Data Model

v1 Field Glossary