T TradieBridge Docs Sign in

Docs

ELMO

People, employment details, leave, positions and departments.

See ELMO data backup on tradiebridge.com.

Each record is held whole. A resource's columns are what a list filters and sorts by.

Questions

leave staff

Leave taken or booked between two days, by person, leave type or status: requests and hours, most hours first. A request that overlaps the days counts whole.

from*
string. First day, e.g. 2026-09-01.
to
string. Last day, inclusive. Default today; at most 400 days.
by
string. Default person.
status
string. Only this status, e.g. APPROVED, SUBMITTED or REJECTED. Default every status.

headcount staff

How many active people ELMO holds now, by department, location, position, legal entity or role, most first.

by
string. Default department.

Ask with ask_question, or GET …/answers/{question} with the arguments as query parameters.

13 resources

candidates Candidates

Recruitment candidates: record_name, email, mobile and address, with education, languages, experience and skills in the document.

Keyed by source_id

7 columns
  • source_id string
  • modified_at datetime
  • record_name string
  • email string
  • mobile string
  • suburb string
  • state string

contact_details Contact details

Each person's personal contact details, keyed by their user id: personal_email, personal_mobile, phones and address.

Keyed by source_id

7 columns
  • source_id string
  • modified_at datetime
  • personal_email string
  • personal_mobile string
  • suburb string
  • state string
  • post_code string

departments Departments

Departments: record_name, code (ELMO's department ID), parent_id and deleted.

Keyed by source_id

6 columns
  • source_id string
  • modified_at datetime
  • record_name string
  • code string
  • parent_id string
  • deleted boolean

employees Employees

Each person's employment details, keyed by ELMO's employment id: employment_type, rate, rate_type, units_per_week, pay_cycle and termination_date. Bank accounts, tax declaration, super fund and emergency contacts are in the document.

Keyed by source_id

8 columns
  • source_id string
  • modified_at datetime
  • employment_type string
  • rate decimal
  • rate_type string
  • units_per_week decimal
  • pay_cycle string
  • termination_date string

leave_requests Leave requests

Leave requests: user_id, leave_type_id, status, starts_on and ends_on (YYYY-MM-DD) and hours.

Keyed by source_id

8 columns
  • source_id string
  • modified_at datetime
  • user_id string
  • leave_type_id string
  • status string
  • starts_on string
  • ends_on string
  • hours decimal

leave_types Leave types

The kinds of leave set up in ELMO: record_name, code, accrual_type and entitlement_type.

Keyed by source_id

7 columns
  • source_id string
  • modified_at datetime
  • record_name string
  • code string
  • accrual_type string
  • entitlement_type string
  • deleted boolean

locations Locations

Locations: record_name, code, suburb, state, parent_id and deleted, with the address in the document.

Keyed by source_id

8 columns
  • source_id string
  • modified_at datetime
  • record_name string
  • code string
  • suburb string
  • state string
  • parent_id string
  • deleted boolean

onboarding_users Onboarding users

People still being onboarded in ELMO, not yet users: record_name, email, start_date and where they will sit.

Keyed by source_id

11 columns
  • source_id string
  • modified_at datetime
  • record_name string
  • email string
  • active boolean
  • position_id string
  • location_id string
  • department_id string
  • legal_entity_id string
  • manager_id string
  • start_date string

payroll_cycles Payroll cycles

Payroll cycles (pay calendars): record_name, cycle_type, jurisdiction and whether it is the default.

Keyed by source_id

6 columns
  • source_id string
  • modified_at datetime
  • record_name string
  • cycle_type string
  • jurisdiction string
  • is_default boolean

positions Positions

Positions (job titles): record_name, code, parent_id and deleted, with qualifications in the document.

Keyed by source_id

6 columns
  • source_id string
  • modified_at datetime
  • record_name string
  • code string
  • parent_id string
  • deleted boolean

settings Settings

ELMO's settings for its configurable user, position and contact detail fields: who may see, edit or must fill each, keyed by path.

Keyed by source_id

3 columns
  • source_id string
  • modified_at datetime
  • record_name string

users Users

The people in ELMO, inactive and deleted ones too: record_name, email, employee_number, active, role, start_date, end_date (YYYY-MM-DD), manager_id, and the position_id, location_id, department_id and legal_entity_id they sit in. Custom fields are in the document.

Keyed by source_id

14 columns
  • source_id string
  • modified_at datetime
  • record_name string
  • email string
  • active boolean
  • position_id string
  • location_id string
  • department_id string
  • legal_entity_id string
  • manager_id string
  • start_date string
  • employee_number string
  • role string
  • end_date string