API Authentication
All API requests to TrackMyMachines require authentication using API keys. Each API key is associated with an organization and has specific permissions based on its role.
Clocking on and off jobs
The jobs endpoint allows you to retrieve, start, and finish jobs in your manufacturing process. TrackMyMachines uses this data to produce reports, calculate estimated finish times, and alert you when your machines run jobs exceeding the quoted time from your ERP system.
Machines
The machines endpoint lists your organisation's machines by the identifiers the rest of the API accepts: foreignid (sent as machineforeignid / machineforeignids) and displayname (sent as machinedisplayname). Use it to build a machine picker, or to check which identifiers to send when clocking on a job.
Timeline events
The events endpoint returns timeline-style events for one or more machines over a short time window. It is intended for building live timeline views — overlays of cycles, steps, part counts, shifts, downtime reasons, and work order operations on a per-machine timeline.
Machine activities
The machine activities endpoint returns aggregated machine status buckets for a short time window — the same data that powers the timeline status strip. Each row represents a contiguous span of time during which a machine was in one status (active, idle, or off).
Datasets
GET /api/v1/charts/:dataset returns the aggregated data behind TrackMyMachines' dashboards as rows.
Connecting Claude or Copilot (MCP)
TrackMyMachines exposes an MCP server — a standard interface that lets AI assistants query your machine data directly. Once connected, you can ask questions in plain English ("which machines had the most downtime last week?") and the assistant fetches the answer from the same aggregated data that powers your dashboards.