Changes to the Matrix TimeCard API that an integrator can see. The newest entry is first.
2026-11-06: records that another source system owns
- Proposed changes:
a proposal that changes nothing on a record that another source system owns now reads
matches_current. Before, it wasrefusedwithowned_by:<owner>. A proposal that would change such a record is still refused. - Activity import: a group for an activity
of the same kind that another source system owns now counts as
unchangedwhen it sends the values that Matrix TimeCard shows. Before, it was a row error. A group that would change such an activity is still a row error, and the message now names the fields. - Equipment: the
f_pattern filters onGET /equipment-catalogare now documented. - Use with AI agents: a skill file for AI agents, a plain Markdown copy of
each page (add
.mdto the page address) and an index at/llms.txt.
2026-11-05: v1 documentation published
The API is version 1. Every path starts with /api/v1. The API key routes available today:
| Area | Capability |
|---|---|
| Activities | List, read, create and update Jobs, Work Orders and Meet Points. Import up to 1,000 rows a request, with a dry run. |
| Phase Codes | List, add and update the Phase Codes of one activity. List Phase Codes across a company's Jobs. Apply one Phase Code to many Jobs. |
| Boundaries | Send a boundary with an activity, redraw it, and turn it off or on. Publish at once with geofences:publish. |
| Equipment | List, read, create, update, deactivate and reactivate equipment |
| Proposed changes | Propose Jobs, Phase Codes and equipment for an administrator to approve |
| Reference lists | Reporting types and reporting frequencies |
| Authentication | API keys with scopes, company binding and a source system |
| Errors | RFC 9457 problem responses with stable codes |
| Safe updates | expectedUpdatedAt on activity and equipment updates |
These pages replace the earlier Postman collection.