REST API & webhooks

Your attendance data, one request away

A clean REST API and HMAC-signed webhooks — pull who is on site, or push every clock event into your own stack.

Talk to us Read the docs 
# Who is on site right now?
curl https://api.tempclock.com/v1/on-site-now \
  -H "Authorization: Bearer tc_live_•••"

{
  "site": "Riverside DC",
  "as_of": "2026-06-01T09:14:22Z",
  "on_site": 12,
  "workers": [
    {
      "name": "James Patterson",
      "clock_in": "07:02",
      "distance_m": 50,
      "status": "on_site"
    }
  ]
}

GET /v1/on-site-now 200 OK 41ms

REST API

JSON over HTTPS, versioned under /v1, documented to OpenAPI 3.0.3.

Scoped keys

Bearer keys with least-privilege scopes, rotated or revoked any time.

HMAC webhooks

Each event is a signed POST you verify byte-for-byte, retried on failure.

Rate limits

60 req/min per key, with X-RateLimit-Remaining on every response.

Documentation

Everything you need to integrate

Start with authentication, copy a worked example, ship.

Authentication

Scoped keys and the Bearer header.

Endpoints

The eight v1 resources, in full.

Webhooks

Subscribe to events and verify HMAC.

Examples

Copy-paste recipes to get going.

Rate limits & errors

The limit, the headers, the codes.

OpenAPI 3.0.3 spec

Generate a typed client.

Get started