Getting Started

Getting Started with the API

Name: TempClock
Author: TempClock

Connect your existing ATS, CRM, or payroll system to TempClock via the REST API.

5 min read

Before You Start Request Access Receive Your Key Your First Request Explore Endpoints Monitoring Usage What's Next

Before You Start

Make sure you have everything you need to get up and running.

Before you start

A TempClock account with Admin access
An API key provided to you by TempClock (see below)
A tool for making HTTP requests — curl, Postman, or your programming language of choice
Basic understanding of REST APIs and JSON

Note

The API lets your existing platforms pull timesheet data, manage workers, view shifts, and even trigger clock-ins programmatically. It is designed for integrating TempClock into your wider tech stack.

Step 1: Request API Access

Contact TempClock to get API access enabled for your account.

For security, API access is not enabled by default and API keys are created exclusively by TempClock. To get started, contact us and let us know:

Your company/account name in TempClock

What systems you plan to integrate (e.g. your ATS, CRM, payroll software)

A brief description of how you intend to use the API

Note

We review every API access request to ensure data security. Once approved, we will enable API access for your account and generate your API key.

Step 2: Receive Your API Key

TempClock will generate and securely send you your API key.

Once your request is approved, TempClock will create a named API key for your account and provide it to you securely. Your key will look like this:

tc_live_a1b2c3d4e5f6a1b2c3d4e5f6a1b2c3d4e5f6a1b2

After receiving your key, you can view it in your manage portal under Settings > API Keys. The full key is only shown once at creation, so store it securely as soon as you receive it.

Manage Portal — API Keys (View Only)

NameKey PrefixStatusLast Used

Bullhorn Integration tc_live_a1b2... Active 10 Mar 2026

You can view your assigned keys here. To request new keys or revoke existing ones, contact TempClock.

Important

Security: Store your API key in a secure location such as a password manager or secrets vault. Never commit it to version control, share it in emails, or expose it in client-side code. If you believe a key has been compromised, contact TempClock immediately to have it revoked.

Step 3: Make Your First Request

Test your API key by fetching your list of workers.

Every API request requires a Bearer token in the Authorization header. Here is a quick test using curl:

Terminal — curl request

$ curl -X GET \

"https://tempclock.com/api/v1/workers.php" \

-H "Authorization: Bearer tc_live_YOUR_KEY_HERE"

If everything is working, you will receive a JSON response containing your workers:

API Response — 200 OK

{

"data": [

{ "id": 1, "name": "John Smith", "active": 1 },

{ "id": 2, "name": "Jane Doe", "active": 1 }

"pagination": { "total": 2, "limit": 50, "offset": 0, "has_more": false }

}

Tip

If you receive a 401 error, double-check that your API key is correct and that the Authorization header is formatted as Bearer <your_key>.

Explore the Endpoints

The TempClock API provides endpoints for all the key areas of your workforce data.

Here is a summary of the available endpoints. For full details, parameters, and response examples, visit the Endpoints Reference.

Workers

List and view workers — names, roles, active status, and assignment details.

Timesheets

Fetch time entries with filters for date range, worker, and location.

Locations

List your work sites with addresses, capacity, and settings.

Clock In/Out

Programmatically clock workers in or out at a location.

Shifts

View scheduled shifts or create new shift assignments.

Departments

List departments for filtering and organising data.

Cost Codes

List cost codes for project-based time tracking.

Note

All endpoints are scoped to your account — you can only access data belonging to your organisation. Each API key is independently rate-limited to 60 requests per minute.

Monitoring Your API Usage

Keep track of how your integrations are using the API.

The API Logs page in your manage portal shows every request made with your API keys. You can see:

Total requests today, this week, and this month

Average response times

Which endpoints are being called most frequently

Status codes for every request (success vs errors)

The IP address and user agent of each request

Manage Portal — API Logs

142

Today

893

This Week

3,241

This Month

45ms

Avg Response

TimeMethodEndpointStatusSpeed

14:32GET/workers20038ms

14:31POST/clock20152ms

Important

Regularly check your API logs to ensure your integrations are working correctly. If you see unexpected 401 or 403 errors, it may indicate a compromised key — revoke it immediately.