Skip to main content
The Operations domain covers the maintenance and procurement workflow: a tenant or technician reports an issue (notifications), a creditor submits a price (offers), work is commissioned (orders), and larger initiatives are tracked as projects.
orders and projects each expose 60+ fields in the live schema (invoicing amounts, hierarchy levels, contact details, and more). This page documents the key identifying and join fields only — see the API Reference tab for the complete, auto-generated field list.

​
notifications

GET /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.
​
string
Type of report.
​
string
Current status of the notification.
​
string
Priority level.
​
date
Date the report was created.

​
offers

GET /operations/offers — price offers submitted by creditors for a piece of work.
​
integer
required
Unique offer identifier. orders references this as offer_hdr_id.
​
integer
required
Unique property identifier.
​
integer
required
Creditor submitting the offer. References Stakeholder.creditor.
​
string
Unit the offer applies to, if applicable.
​
number
Total offer value.
​
string
Type of offer.
​
string
Current status of the offer.
​
boolean
Whether the offer was accepted.

​
orders

GET /operations/orders — commissioned work orders.
​
integer
required
Unique order identifier.
​
integer
required
Unique property identifier.
​
integer
Offer this order was created from. References offers.offer_hdr_id.
​
integer
Creditor performing the work.
​
integer
Technical object the order concerns, if applicable.
​
integer
Originating notification, if the order was created from one.
​
string
Order type.
​
number
Total net order value.
​
number
Total gross order value.
​
string
Cost centre the order is booked against.
​
string
Invoicing status of the order.

​
projects

GET /operations/projects — capital projects and larger multi-order initiatives.
​
integer
required
Unique project identifier.
​
integer
required
Unique property identifier.
​
integer
Primary creditor for the project.
​
integer
Related offer, if applicable.
​
integer
Related technical object, if applicable.
​
string
Project number.
​
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.
hierarchy_1 through hierarchy_20 describe the project’s position in a cost-breakdown hierarchy — most integrations only need hierarchy_1/hierarchy_2 for top-level grouping.