Skip to content
Demiton

Leave request

Leave request is one of Demiton's published registers for Australian civil construction. Leave requests and their approval status. Demiton keeps it current from the systems a contractor already runs and publishes the record's shape as a versioned JSON Schema, so the same question works whichever system produced the record.

Part of Workforce in the register catalog.

Register ID
leave_requestUse this name to ask for the register. The API calls it a shelf ID.
Each record is
An eventSomething that happened at a point in time.
Status
AvailableFilled today from connected systems, uploads or public data.
Data
OrganisationPrivate to each organisation's own workspace.
Version
v1 (1.0.2)Current version.

Standards

This register's contract was designed against these standards and laws. Holding these records does not by itself certify compliance.

  • Fair Work Act 2009Fair Work Act 2009 - employee records and National Employment StandardsAustralia · compilation 2026-07-07 · clause ss.87(1), 96(1), 535 ; s.106A · verified against full text
  • Fair Work Act 2009Fair Work Regulations 2009 - employee record contentAustralia · compilation 2026-06-20 · clause regs 3.32-3.34, 3.36 · verified against full text
  • Privacy Act 1988Privacy Act 1988 - Australian Privacy Principles; employee-records exemption; health information s.6FAAustralia · current · public summary
  • ISO 30414Human resource management - Requirements and recommendations for human capital reporting and disclosureInternational · 2nd ed. 2025 (supersedes ISO 30414:2018) · paywalled, from a secondary description
  • Employment Leave Act 2026 (NZ)Employment Leave Act 2026 (2026 No 48)New Zealand · assent 6 Aug 2026; not yet in force · clause ss.24(1), 73(1), 75(1), 127-130 · verified against full text
  • Holidays Act 2003 (NZ)Holidays Act 2003 (2003 No 129) - holiday and leave recordNew Zealand · version as at 20 Dec 2023 (repealed on commencement of Employment Leave Act 2026) · clause ss.16(1), 65(2), 66, 81 · verified against full text
  • Privacy Act 2020 (NZ)Privacy Act 2020 and Health Information Privacy Code 2020New Zealand · Act 2020; HIPC version as at 1 May 2026 · public summary
  • SI 1998/1833Working Time Regulations 1998United Kingdom · as amended by SI 2023/1426 from 1 Jan 2024 · clause regs 4-6, 9, 13, 13A, 15B · verified against full text
  • Statutory Sick Pay (Social Security Contributions and Benefits Act 1992)Statutory Sick Pay - weekly statutory payment, no day entitlementUnited Kingdom · rate read 2026-09-11 · public summary
  • UK GDPRUK GDPR and Data Protection Act 2018United Kingdom · current · public summary

Connectors

Connected today

Demiton keeps this register current from these systems now.

On the roadmap

Systems in the planned connector rollout that can fill this register. Partial means the system holds only some of its fields.

  • MYOB AcumaticaPartial
  • Xero AccountingPartial
  • Xero Payroll AU

Fields

14 fields: 7 required, 6 optional, 1 defined by each organisation.

Required

Every record carries these fields.

hoursDecimal numberUnit: hours

Paid hours of leave, summed from the per-day intervals.

Example: 38

workerText

The employee the leave belongs to.

Example: 1003

to_dateDateYYYY-MM-DD

Last day of the leave.

Example: 2026-07-24

from_dateDateYYYY-MM-DD

First day of the leave.

Example: 2026-07-20

leave_typeText

Category of leave (annual, personal/carer's, …)

Example: Annual Leave

is_approvedTrue or false

Whether the request is approved.

Example: true

source_record_idText

The source record's identity, for idempotent upsert.

Example: LR-55231

Optional

Present when the source system records them.

daysWhole numberUnit: leave-day rows

Number of per-day leave rows behind the request.

Example: 5

reasonText

The employee's stated reason.

statusText

The source status label (e.g. pending)

Example: approved

leave_datesListUnit: datetime (local)

The per-day leave intervals the request comprises.

financial_periodText

The pay period the leave falls in.

Example: 2026-07

leave_type_labelText

The vendor's display name for the leave type.

Defined by each organisation

Their contents come from the organisation's own forms or systems, so they differ between organisations.

leave_type_idWhole number

The bound system's numeric leave-type id.

Filed against

Records are indexed along these dimensions, so they can be asked for by any of them.

  • Financial periodcontext for the record, from When known
  • Workerwhat the record is about, from Always set

Example record

A sample from Bridgeworks Group, Demiton's demonstration company. The values are illustrative; the shape is exactly what the contract describes.

leave_request.example.json
{
"days": 5,
"financial_period": "2026-07",
"from_date": "2026-07-20",
"hours": 38,
"is_approved": true,
"leave_type": "Annual Leave",
"source_record_id": "LR-55231",
"status": "approved",
"to_date": "2026-07-24",
"worker": "1003"
}

Use this contract

The contract is a standard JSON Schema (draft 2020-12) document, so any JSON Schema validator can check a record against it. Keywords starting with x-demiton- add Demiton's own meaning, such as units and requiredness, and validators ignore them.

Schema URL
https://docs.demiton.io/registers/leave_request/v1.json
Show the full JSON Schema

Loading the schema…

Talk to the team

Tell us what you run - your ERP, field, payroll and document systems - and we will show you the registers Demiton would fill from them, on your data, in a 30-minute call.

Book a 30-minute callStart free