T TradieBridge Docs Sign in

Docs

Deputy

Timesheets, rosters, staff and leave.

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

Questions

hours staff

Hours worked between two days, by employee, area or day, largest first: hours, the approved part, cost and shifts. Discarded shifts and leave are left out.

from*
string. First day, e.g. 2026-09-01.
to
string. Last day, inclusive. Default today; at most 400 days.
by
string. Default employee.

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

59 resources

addresses Addresses

Addresses (employees' home, postal and emergency addresses, locations' and areas' addresses): street, city, state, postcode.

Keyed by source_id

6 columns
  • source_id string
  • modified_at datetime
  • street string
  • city string
  • state string
  • postcode string

areas Areas

Areas inside a location (Deputy's OperationalUnit) that shifts are rostered to: record_name, location_id, active.

Keyed by source_id

5 columns
  • source_id string
  • modified_at datetime
  • record_name string
  • location_id integer
  • active boolean

categories Categories

Categories Deputy sorts records into: record_name and category_group.

Keyed by source_id

4 columns
  • source_id string
  • modified_at datetime
  • record_name string
  • category_group string

comments Comments

Comments on Deputy records: orm names the kind of record and rec_id its Id.

Keyed by source_id

4 columns
  • source_id string
  • modified_at datetime
  • orm string
  • rec_id integer

company_periods Company periods

Each location's pay period dates: location_id, pay_period_id, date_start and date_end.

Keyed by source_id

6 columns
  • source_id string
  • modified_at datetime
  • location_id integer
  • pay_period_id integer
  • date_start string
  • date_end string

contacts Contacts

Contact records (email, phone) that employees, locations and areas name by Id.

Keyed by source_id

4 columns
  • source_id string
  • modified_at datetime
  • email string
  • phone string

countries Countries

Deputy's list of countries, which addresses name by Id.

Keyed by source_id

4 columns
  • source_id string
  • modified_at datetime
  • record_name string
  • code string

custom_app_data Custom app data

Data other apps installed in Deputy keep there: label, key_string, employee_id and area_id.

Keyed by source_id

6 columns
  • source_id string
  • modified_at datetime
  • label string
  • key_string string
  • employee_id integer
  • area_id integer

custom_field_data Custom field data

The values of custom fields (F01 to F128) that a record names by its CustomFieldData Id.

Keyed by source_id

2 columns
  • source_id string
  • modified_at datetime

custom_fields Custom fields

Custom fields set up in Deputy: record_name and api_name.

Keyed by source_id

4 columns
  • source_id string
  • modified_at datetime
  • record_name string
  • api_name string

employee_agreement_histories Employee agreement histories

Each version of an employee's pay agreement: employee_agreement_id, start_date, effective_date, base_rate and annual_salary.

Keyed by source_id

7 columns
  • source_id string
  • modified_at datetime
  • employee_agreement_id integer
  • start_date string
  • effective_date string
  • base_rate decimal
  • annual_salary decimal

employee_agreements Employee agreements

Each employee's pay agreement: employee_id, active, start_date, payroll_id and the pay rates in the document.

Keyed by source_id

6 columns
  • source_id string
  • modified_at datetime
  • employee_id integer
  • active boolean
  • start_date string
  • payroll_id string

employee_appraisals Employee appraisals

Performance ratings given to employees: employee_id, day and the marks.

Keyed by source_id

4 columns
  • source_id string
  • modified_at datetime
  • employee_id integer
  • day string

employee_availabilities Employee availabilities

When each employee says they can or cannot work: employee_id, day and the schedule.

Keyed by source_id

4 columns
  • source_id string
  • modified_at datetime
  • employee_id integer
  • day string

employee_histories Employee histories

Each version of an employee's record over time: employee_id, record_name, start_date and termination_date.

Keyed by source_id

6 columns
  • source_id string
  • modified_at datetime
  • employee_id integer
  • record_name string
  • start_date string
  • termination_date string

employee_paycycle_returns Employee paycycle returns

The pay lines of a pay cycle: employee_paycycle_id, pay_rule_id, value (hours or units), cost and approved.

Keyed by source_id

7 columns
  • source_id string
  • modified_at datetime
  • employee_paycycle_id integer
  • pay_rule_id integer
  • value decimal
  • cost decimal
  • approved boolean

employee_paycycles Employee paycycles

One employee's pay for one pay period: employee_id, pay_period_id, time_total (hours), cost_total, paid and exported.

Keyed by source_id

9 columns
  • source_id string
  • modified_at datetime
  • employee_id integer
  • employee_agreement_id integer
  • pay_period_id integer
  • time_total decimal
  • cost_total decimal
  • paid boolean
  • exported boolean

employee_profiles Employee profiles

Deputy's v2 employee list: each person with their contact, addresses, workplaces, training records and stress profile nested.

Keyed by source_id

3 columns
  • source_id string
  • modified_at datetime
  • record_name string

employee_roles Employee roles

Access levels in Deputy (employee, supervisor, location manager…) and their ranking.

Keyed by source_id

4 columns
  • source_id string
  • modified_at datetime
  • record_name string
  • ranking integer

employee_salary_opunit_costings Employee salary opunit costings

A salaried employee's cost spread across areas by day: employee_id, area_id, day and cost.

Keyed by source_id

6 columns
  • source_id string
  • modified_at datetime
  • employee_id integer
  • area_id integer
  • day string
  • cost decimal

employee_workplaces Employee workplaces

Which locations each employee works at (employee_id, location_id), with their agreements there.

Keyed by source_id

4 columns
  • source_id string
  • modified_at datetime
  • employee_id integer
  • location_id integer

employees Employees

Staff: record_name, active, location_id, start_date, termination_date, email, and the whole contact record (ContactObject).

Keyed by source_id

9 columns
  • source_id string
  • modified_at datetime
  • record_name string
  • active boolean
  • location_id integer
  • role_id integer
  • start_date string
  • termination_date string
  • email string

employment_conditions Employment conditions

Award conditions behind a contract: record_name, award_level and hours per day.

Keyed by source_id

4 columns
  • source_id string
  • modified_at datetime
  • record_name string
  • award_level string

employment_contract_leave_rules Employment contract leave rules

Which leave rules each contract allows (employment_contract_id, leave_rule_id), with their pay rules.

Keyed by source_id

4 columns
  • source_id string
  • modified_at datetime
  • employment_contract_id integer
  • leave_rule_id integer

employment_contracts Employment contracts

Awards and contracts employees are paid under: record_name, code, start_date, end_date and the pay rules.

Keyed by source_id

6 columns
  • source_id string
  • modified_at datetime
  • record_name string
  • code string
  • start_date string
  • end_date string

events Events

Events on the roster calendar: record_name and schedule_id.

Keyed by source_id

4 columns
  • source_id string
  • modified_at datetime
  • record_name string
  • schedule_id integer

geo_tags Geo tags

Where a record was made (a clock-in, for example): orm and rec_id name the record, with latitude and longitude.

Keyed by source_id

6 columns
  • source_id string
  • modified_at datetime
  • orm string
  • rec_id integer
  • latitude decimal
  • longitude decimal

journals Journals

Journal notes written against an employee: employee_id, day and the comment.

Keyed by source_id

4 columns
  • source_id string
  • modified_at datetime
  • employee_id integer
  • day string

kiosks Kiosks

Clock-in kiosks: record_name, location_id and when each was last used.

Keyed by source_id

4 columns
  • source_id string
  • modified_at datetime
  • record_name string
  • location_id integer

leave_accruals Leave accruals

Leave earned and taken, line by line: employee_id, leave_rule_id, day and hours. Balances: summarize hours by employee_id and leave_rule_id.

Keyed by source_id

6 columns
  • source_id string
  • modified_at datetime
  • employee_id integer
  • leave_rule_id integer
  • day string
  • hours decimal

leave_pay_lines Leave pay lines

The pay lines for leave taken: leave_request_id, leave_rule_id, timesheet_id, day, hours and cost.

Keyed by source_id

8 columns
  • source_id string
  • modified_at datetime
  • leave_request_id integer
  • leave_rule_id integer
  • timesheet_id integer
  • day string
  • hours decimal
  • cost decimal

leave_requests Leave requests

Leave: employee_id, leave_rule_id (leave_rules), date_start, date_end, total_hours and status (0 awaiting, 1 approved, 2 declined, 3 cancelled, 4 date only approved, 5 pay approved).

Keyed by source_id

8 columns
  • source_id string
  • modified_at datetime
  • employee_id integer
  • leave_rule_id integer
  • status integer
  • date_start string
  • date_end string
  • total_hours decimal

leave_rules Leave rules

The kinds of leave set up in Deputy (annual, personal and so on).

Keyed by source_id

4 columns
  • source_id string
  • modified_at datetime
  • record_name string
  • visible boolean

locations Locations

Deputy's locations (its Company object): record_name, code, active and whether each is a workplace.

Keyed by source_id

6 columns
  • source_id string
  • modified_at datetime
  • record_name string
  • code string
  • active boolean
  • workplace boolean

memos Memos

Newsfeed memos posted to staff.

Keyed by source_id

2 columns
  • source_id string
  • modified_at datetime

pay_periods Pay periods

Pay periods: record_name, start_date and active.

Keyed by source_id

5 columns
  • source_id string
  • modified_at datetime
  • record_name string
  • start_date string
  • active boolean

pay_rules Pay rules

Pay rules: record_name (PayTitle), hourly_rate and payroll_category.

Keyed by source_id

5 columns
  • source_id string
  • modified_at datetime
  • record_name string
  • hourly_rate decimal
  • payroll_category string

public_holidays Public holidays

Public holidays set up in Deputy: record_name and schedule_id (the schedule holds the date).

Keyed by source_id

4 columns
  • source_id string
  • modified_at datetime
  • record_name string
  • schedule_id integer

roster_opens Roster opens

Open shifts offered to employees, and who accepted (roster_id, employee_id, accepted).

Keyed by source_id

5 columns
  • source_id string
  • modified_at datetime
  • roster_id integer
  • employee_id integer
  • accepted boolean

roster_swaps Roster swaps

Shift swap requests between two rosters (source_roster_id, target_roster_id), with status.

Keyed by source_id

6 columns
  • source_id string
  • modified_at datetime
  • source_roster_id integer
  • target_roster_id integer
  • employee_id integer
  • status integer

rosters Rosters

The PLAN: shifts rostered to employee_id in area_id, by day, with total_hours, cost, published and open (unassigned). Never time worked.

Keyed by source_id

10 columns
  • source_id string
  • modified_at datetime
  • employee_id integer
  • area_id integer
  • day string
  • started_at string
  • total_hours decimal
  • cost decimal
  • published boolean
  • open boolean

sales_data Sales data

Sales figures used to plan rosters: day, area_id, employee_id, sales_type, sales_qty and sales_amount.

Keyed by source_id

8 columns
  • source_id string
  • modified_at datetime
  • employee_id integer
  • area_id integer
  • day string
  • sales_type string
  • sales_qty decimal
  • sales_amount decimal

schedules Schedules

Schedules that events, holidays and availability repeat on: record_name, start_date and end_date.

Keyed by source_id

5 columns
  • source_id string
  • modified_at datetime
  • record_name string
  • start_date string
  • end_date string

sms_logs Sms logs

Text messages Deputy sent: destination, the message and how many parts.

Keyed by source_id

3 columns
  • source_id string
  • modified_at datetime
  • destination string

states States

Deputy's list of states, by country.

Keyed by source_id

4 columns
  • source_id string
  • modified_at datetime
  • record_name string
  • code string

stress_profiles Stress profiles

Fatigue rules: the most hours a shift, a day or a week may hold.

Keyed by source_id

3 columns
  • source_id string
  • modified_at datetime
  • record_name string

system_usage_balances System usage balances

Deputy's account balance entries for paid features (text messages and so on): day, credit and description.

Keyed by source_id

5 columns
  • source_id string
  • modified_at datetime
  • day string
  • credit decimal
  • description string

system_usage_tracking System usage tracking

Each use of a paid Deputy feature: day, usage, description and employee_id.

Keyed by source_id

5 columns
  • source_id string
  • modified_at datetime
  • day string
  • usage decimal
  • employee_id integer

task_group_setups Task group setups

Task group templates: record_name and active.

Keyed by source_id

4 columns
  • source_id string
  • modified_at datetime
  • record_name string
  • active boolean

task_groups Task groups

Groups of tasks for an area on a day: record_name, area_id and day.

Keyed by source_id

5 columns
  • source_id string
  • modified_at datetime
  • record_name string
  • area_id integer
  • day string

task_opunit_configs Task opunit configs

Which task templates run in which area: task_setup_id, area_id and active.

Keyed by source_id

5 columns
  • source_id string
  • modified_at datetime
  • task_setup_id integer
  • area_id integer
  • active boolean

task_setups Task setups

The task templates: record_name (the question) and active.

Keyed by source_id

4 columns
  • source_id string
  • modified_at datetime
  • record_name string
  • active boolean

tasks Tasks

Tasks set against areas: record_name (the question), area_id, day and due_date.

Keyed by source_id

6 columns
  • source_id string
  • modified_at datetime
  • record_name string
  • area_id integer
  • day string
  • due_date string

teams Teams

Teams of employees and their leader (leader_employee_id).

Keyed by source_id

4 columns
  • source_id string
  • modified_at datetime
  • record_name string
  • leader_employee_id integer

timesheet_pay_returns Timesheet pay returns

The pay lines Deputy worked out for a timesheet: timesheet_id, pay_rule_id, value (hours or units), cost and overridden.

Keyed by source_id

7 columns
  • source_id string
  • modified_at datetime
  • timesheet_id integer
  • pay_rule_id integer
  • value decimal
  • cost decimal
  • overridden boolean

timesheets Timesheets

Time WORKED, as Deputy holds it: employee_id, area_id, day (the install's own day), started_at, total_hours, cost, approved, discarded, leave (a leave entry, not work) and in_progress. Hours worked: summarize total_hours where discarded is false.

Keyed by source_id

13 columns
  • source_id string
  • modified_at datetime
  • employee_id integer
  • area_id integer
  • day string
  • started_at string
  • total_hours decimal
  • cost decimal
  • roster_id integer
  • approved boolean
  • discarded boolean
  • leave boolean
  • in_progress boolean

training_modules Training modules

Training and qualifications set up in Deputy: record_name, provider, cost and renewal period.

Keyed by source_id

5 columns
  • source_id string
  • modified_at datetime
  • record_name string
  • provider string
  • cost decimal

training_records Training records

Training each employee completed: employee_id, training_module_id, training_date and expiry_date.

Keyed by source_id

6 columns
  • source_id string
  • modified_at datetime
  • employee_id integer
  • training_module_id integer
  • training_date string
  • expiry_date string

webhooks Webhooks

Webhooks set up on the install: topic and enabled. Their headers and any credentials in their address are not held.

Keyed by source_id

4 columns
  • source_id string
  • modified_at datetime
  • topic string
  • enabled boolean