The GEM Time API. Approved hours, employees and one-off payroll lines move between GEM Time and your payroll, HR or accounting system — without exporting a spreadsheet or typing anything twice.
GEM Time Connect is a secure JSON API on your own GEM Time account. Your payroll system, or a bridge we build for it, asks GEM Time for what it needs and sends back what changed.
Pull the calculated hours per employee for a pay period — regular, each overtime tier, night and other premium hours, holiday, paid leave and banked time — or day by day for a date range. The same figures as the Payroll screen, never a second calculation.
Read the employee list with employee numbers, department, position and hire and end dates, so both systems agree on who works there. Send new joiners, leavers and department changes the other way, so nobody is entered twice.
Post a bonus, a commission, a deduction or the tips from the till straight onto the payroll. Each line is checked against your own pay codes, and a refused line says why without stopping the rest of the batch.
The API runs the same calculation engine as GEM Time's own Payroll screen, so the hours your supervisors approved are the hours your payroll system receives.
A machine-readable field list gives each hour type its meaning, its unit and whether it is payable — so an integration cannot book banked time as paid time by mistake.
A dry run shows exactly what a batch would do, row by row, and writes nothing. Retrying a batch that timed out is safe: the same reference is never applied twice.
Integrations pull a pay period after it is closed and approved, and the API flags any hours still waiting for a supervisor's decision.
Batches and their rows are visible inside GEM Time, and a batch can be undone as one unit until its lines have been paid on a locked payroll.
Data comes in through the same checks as the screens. An integration cannot do anything a person could not do in GEM Time.
Each integration gets its own access key, tied to one company and able to see only that company's data. GEM Time stores only a hash of the key, and the key itself is shown once, when it is created. Keys are read-only by default; a key that can write is issued by GEM IT for one named integration. Lose a key, or retire an integration, and that one key is revoked without touching the others. Requests are rate-limited, and repeated bad keys lock the caller out.
GEM Time Connect speaks standard HTTPS and JSON, so any payroll, HR or accounting system that can call a web service can use it. Tell us which system you pay from, and we build and support the bridge to it.
We check what it can import or expose, and agree what moves in each direction.
Regular, overtime tiers, night premium and holiday hours are matched to your payroll's wage codes, once.
We run a real, closed pay period through it and check it against your payroll before the first live run.
Tell us which payroll or HR system you use and we will tell you how it connects.
Talk to Our Team