notifications and
projects.
notifications and projects expose 20+ fields each in the live v1 schema. This page
documents the key identifying, join, and reshaped fields — see the API Reference tab
for the complete, auto-generated field list.notifications
GET /v1/operations/notifications — maintenance reports and damage notifications.
integer
required
Unique notification identifier.
integer
required
Unique property identifier.
integer
Technical object the report concerns. References
Property.technical_objects.to_id.integer
Reporting person. This is a
bigint sequence from a different subsystem — don’t treat it
as the same identifier space as person_id on Accounting.booking_header or
Stakeholder.tenants.string
Cost centre the notification is attributed to.
string
Type of report.
string
Priority level.
string
Current status of the notification.
date
Date the report was created.
boolean
Whether the notification is linked to an insurance claim.
projects
GET /v1/operations/projects — capital projects and larger multi-order initiatives.
integer
required
Unique project identifier.
string
Human-readable project number — distinct from
project_id above, which is the
identifier to use for lookups and joins.integer
required
Unique property identifier.
string
Cost centre the project is booked against.
integer
Primary creditor for the project. Currently doesn’t resolve against
Stakeholder.creditor.creditor_id — treat it as unreliable rather than a working foreign
key until the source data is fixed.integer
Related offer, if applicable.
integer
Related notification, if the project originated from one.
integer
Looks like a technical-object reference by name, but isn’t — only about 3.5% match
against
technical_objects.to_id, and no better match against orders/notifications.
The target entity is unconfirmed; don’t treat this as a working foreign key.string[]
Position in the cost-breakdown hierarchy, as an ordered array from the top level down.
Empty levels are omitted, so the array length varies per project.
string
Project type.
string
Current project status.
number
Total budgeted amount for the project.
number
Completion percentage.
date
Project start date.
date
Project end date.
string
Project-lead flag. Still a
'0'/'1' string, not yet a boolean — meaning of the two
values isn’t confirmed with the source system yet.