Skip to content
ClockLap Developers
API reference clocklap.com Get an API key

Get started

Quickstart

Five minutes from nothing to your first response. You need a ClockLap workspace and to be an owner or admin (anyone who can manage integrations).

1. Create an API key#

  1. Open Developers settings

    In the console, go to Settings → Developers → API keys and click Create key.

  2. Name it and pick its access

    Name it after what will use it, for example “Payroll export”. Tick only the access it needs, such as Read time entries and timesheets. Pick Test to try things on sample data first.

  3. Copy the key

    It looks like tt_live_ca_9fK2… and is shown only once. Store it in your tool's secret settings or a password manager.

2. Make your first request#

Put the key in an environment variable, then list your workspace's locations. Pick your region so the examples use the right address. Your key shows it: tt_live_ca_… is Canada, tt_live_us_… is the United States.

export CLOCKLAP_API_KEY="tt_live_ca_9fK2…"

curl https://ca-api.clocklap.com/v1/locations \
  -H "Authorization: Bearer $CLOCKLAP_API_KEY"

You get back JSON with a data list:

{
  "data": [
    {
      "id": "loc_01J9Q…",
      "type": "site",
      "name": "Toronto Warehouse",
      "parent_id": "loc_01J9P…",
      "address": "120 Industrial St, Toronto",
      "timezone": null,
      "people": 14,
      "on_site": 9
    }
  ]
}

Locations are regions, sites and zones; build the tree from parent_id. A timezone of null means the site uses its region's or the workspace's.

3. Read some hours#

Now fetch last week's shifts. Times are ISO 8601 with an offset; each entry also carries its site's timezone and local_date.

curl -G https://ca-api.clocklap.com/v1/time-entries \
  -H "Authorization: Bearer $CLOCKLAP_API_KEY" \
  --data-urlencode "from=2026-10-19T00:00:00-04:00" \
  --data-urlencode "to=2026-10-26T00:00:00-04:00" \
  -d limit=100

More than 100? Pass next_cursor back as cursor until has_more is false. See pagination.

Next steps#