Work activity categories

Work activity categories is one of Demiton's published registers for Australian civil construction. Job tasks normalised to a standard work activity taxonomy: piling, anchors and so on. 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 Financials in the register catalog.

Register ID

work_activity_categoriesUse this name to ask for the register. The API calls it a shelf ID.

Each record is

A stateThe current value of something, replaced when it changes.

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.

Download JSON SchemaSee an example record

Connectors

Connected today

Demiton keeps this register current from these systems now.

• Business Central

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 Acumatica

Fields

6 fields: 4 required, 2 optional.

Required

Every record carries these fields.

labelText

Human-readable work-activity name (the display name on the spine)

Example: Kerb and Channel

canonical_keyText

The canonical Level 1 work-activity slug (e.g. a work-type slug), the join key every consumer resolves against.

Example: kerb_and_channel

work_activity_idWhole number

Demiton canonical WORK_ACTIVITY spine node this fact is about.

Example: 301

source_external_idText

The raw record identity in the producing system (today the slug itself)

Example: T-00

Optional

Present when the source system records them.

job_task_noText

One BC Job_Task_No that maps to this slug — a sample, because the normalizer keeps only the first task_no seen per slug.

Example: BWG-2025-001-T01

legal_entity_idWhole number

Owning legal entity where the source is multi-company (BC company context)

Example record

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

work_activity_categories.example.json

{
  "canonical_key": "kerb_and_channel",
  "job_task_no": "BWG-2025-001-T01",
  "label": "Kerb and Channel",
  "source_external_id": "T-00",
  "source_system": "D365_BUSINESS_CENTRAL",
  "work_activity_id": 301
}

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/work_activity_categories/v1.json

Show the full JSON Schema

Loading the schema…