Skip to main content
​
ProductAPIConnector

​
Terminals: names, verification, and a real unclaimed queue

Registering a machine
  • Machines now take an optional name (“Main gate — Pune HQ”), shown everywhere in place of the bare serial. The serial stays underneath as the key we match on the wire, and can’t be changed after registration.
  • A Verify button checks a serial before you commit, reporting whether a terminal with that serial has ever reached the connector — and blocking outright if another organization already holds it. “Not seen yet” is a warning, not a blocker: registering before the unit is plugged in is the normal install order.
Removing a machine
  • Machines can now be removed. One with no punch history is deleted outright, freeing its serial to register again; one with history is decommissioned instead, so every punch it recorded stays exactly where it is. The dialog tells you which will happen before you commit. Decommissioned machines are visible behind Show retired, and can be restored.
Terminal users
  • The flat “Terminal users” card is now an Unclaimed users tab, listing only IDs that still need a decision, with a count badge and which machines each ID has been seen on. Numbers that resolve only by the employee-code convention appear as a guess you can confirm in one click.
  • Confirmed enrollments now appear on the employee’s own Devices tab, with their terminal ID and the machines they’ve punched on. Previously that section was empty for everyone regardless of enrollment — a genuine bug, now fixed.
Employees list
  • Every column is sortable, not just four.
  • The selection action bar is visible as soon as you tick a row instead of only after scrolling, and is readable in dark mode.
  • Audit entries read as what happened (“Enrolled on biometric terminal”) rather than a generic action-and-category pair.
​
ProductAPIMCPConnector

​
Initial public documentation

First public release of the OnTime docs: full Help Center, developer guides, API reference generated from our OpenAPI spec, AI & MCP integration docs, and biometric terminal setup.What’s covered
  • Help Center — attendance and punching, leave, shifts and rosters, payroll, Indian statutory compliance, reports, people and organization administration, and both mobile apps. Plus a FAQ and a glossary.
  • Developers — the public REST API, webhooks with signature verification, the error and pagination contracts, and worked integration guides.
  • API Reference — generated directly from the OpenAPI specification, with an interactive playground.
  • AI & MCP — connecting Claude, Claude Code and ChatGPT, the full 71-tool catalog, and the security model.
  • Biometric Terminals — installing the connector, registering devices, mapping terminal users, and the punch lifecycle.