Integration · Public API

Connect your own systems with API version 1.3

Your booking system, ATS, payroll or turnstiles can work with TempClock directly. The same rules as the screens apply, every key has only the access you give it, and signed webhooks tell you the moment something changes.

Talk to us See how it works
app.tempclock.com/admin/api
Setup · API · Booking system key Active
Workers Read and write
Shifts and requirements Read and write
Availability Read
Timesheets Read
Pay Off
Charges Off
60 requests a minute · expires 31 Mar Rotate
Illustration. Pay and charges have their own access levels and start switched off.
01/What connects

What your systems can do

21 endpoints under /api/v1, described in an OpenAPI 3.0.3 file you can load into your own tools.

Bookings and requirements

Create, change and cancel bookings, read and fill requirements, and ask who is free for a slot, best matches first. The Shifts board's checks apply, and workers are told about a change just as when you make it on screen.

Workers kept in step

Worker records with department, cost code, status, dormant flag and leaving reason. Sync only what changed with updated_since.

Locked payroll weeks

See when a pay week is locked, then pull exactly what the Sage 50 Payroll file pays, line for line: the Sage payment reference, hours, rate and amount.

Clocks from your own terminals

Turnstiles and other terminals send clocks that follow the kiosk's rules and link to the booked shift. An Idempotency-Key makes a retry safe.

Timesheets, exceptions and charges

Every timesheet shift says whether payroll will pay it and why. Read exceptions, client amendment requests, the charge schedule and rate rules too.

A payroll integration
In TempClock Payroll locks the week
Your endpoint pay_week.locked
TempClock API Payroll for that week

A failed delivery is retried, up to 5 attempts, and kept in the delivery log for 90 days.

02/A webhook

What your endpoint receives when a week is locked

Check the signature over the exact body, reply 2xx within 5 seconds, and use the delivery id to ignore a repeat. Then pull the week with the payroll API.

# Sample delivery (sample values)
POST /your/endpoint
X-TempClock-Event: pay_week.locked
X-TempClock-Delivery: 8841
X-TempClock-Signature: sha256=5d0b3c...

{
  "event": "pay_week.locked",
  "timestamp": "2026-09-28T07:08:52Z",
  "data": {
    "client_id": 68,
    "week_start": "2026-09-21",
    "week_end": "2026-09-27",
    "lock_id": 33
  }
}

HMAC-SHA256 of the raw body · up to 5 attempts · delivery log kept 90 days

02/The benefit

Built for systems that must not drift

The API follows the same rules and the same pricing engine as the screens, so a connected system never sees a different answer.

Keys with only the access they need

Access per resource, with Pay and Charges as their own levels. A key can have an expiry date, its own rate limit and a list of browser origins. Rotate swaps the secret without downtime.

Webhooks you can trust

Every delivery is signed with HMAC-SHA256 and carries a delivery id for ignoring repeats. Events fire for changes made on screen and in the client portal, and never carry pay figures or contact details.

Documented, and tested

An endpoint reference, a webhooks page, conventions, an agency integration guide and a Postman collection, with examples tested before each release.

03/Honest scope

What the API covers, and what it does not

The API works within the same rules as the screens. Here is the plain list.

Included today

Workers, sites, departments, cost codes, bookings, requirements, offers, availability, absences, timesheets, clocks, who is on site now, exceptions, amendments, payroll, pay weeks, export batches, charges, rate rules and webhook subscriptions
Webhook events for clocks, time entries, approvals, rejections, queries, amendments, locked weeks, exports, bookings, no-shows and workers
A per-key rate limit, 60 requests a minute unless you raise it, with the remaining count on every reply
An error_code on every error and an X-Request-Id on every reply, with refused calls in the API log
Exact times across the clock change: send times with Z or an offset

Not part of the API

Changing a booking that has been worked, or anything in a locked pay week: correct the timesheet in TempClock
Deleting a client
An event for every change: a worker taking or declining an offer, and cover booked from the Shifts board, send none yet. The developer Webhooks page lists them
Pay or charge figures for a key without Pay or Charges access

Start with the developer docs and the webhooks reference. To make a key, see the API keys guide and the webhook set-up guide.

Other integrations

Sage Payroll file and invoices Xero Invoice and timesheet files Card readers: coming soon NFC and RFID cards, once tested Microsoft 365 Send mail from your own tenant Twilio Optional SMS add-on

Building something custom? The REST API (version 1.3) and signed webhooks let you connect any system.

Plug TempClock into the way you already work

Read the developer docs, or tell us what you need to connect and we will show you the calls.

Talk to us See pricing

Hosted in the EU · Your largest site live first, with us alongside · No app needed to clock in