ClockShark API · unofficial, by Cotlet

Create your own ClockShark API

ClockShark: no public developer API found on clockshark.com (checked 20 Nov 2026). With Cotlet you can build your own. Do a job once with your AI agent in your ClockShark account, save it as an endpoint, and call it from n8n, Make, Zapier or your own code. Each endpoint runs in your own signed-in ClockShark session and returns only what your login can see.

Try it free now

Free 7-day trial, 2,000 credits, no card

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by ClockShark. ClockShark is a trademark of its owner. If ClockShark's own integrations cover what you need, use them first.

curl
curl -X POST "https://cotlet.dev/api/v1/custom/timesheets-with-alerts" \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"week": "2026-11-16"}'
Node.js
const url = "https://cotlet.dev/api/v1/custom/timesheets-with-alerts";
const res = await fetch(url, {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.COTLET_API_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({ week: "2026-11-16" }),
});
const { data } = await res.json();
Python
import os
import requests

key = os.environ["COTLET_API_KEY"]
res = requests.post(
    "https://cotlet.dev/api/v1/custom/timesheets-with-alerts",
    headers={"Authorization": f"Bearer {key}"},
    json={"week": "2026-11-16"},
)
data = res.json()["data"]
Response 200 OK · JSON
{
  "data": [
    {
      "employee": "Luis M.",
      "job": "42 Oak Street",
      "hours": 9.5,
      "alert": "Missing Out"
    },
    {
      "employee": "Sam K.",
      "job": "12 Pine Ave",
      "hours": 11,
      "alert": "Overtime"
    }
  ]
}

01 Build

How do you build a ClockShark endpoint with Cotlet?

  1. Sign in to ClockShark in your Cloud Browser.

    You type your password yourself. Cotlet keeps the signed-in session, encrypted, never the password.

  2. Do the job once with your agent.

    For example: "List last week's timesheets that have alerts, with the employee, job, hours and alert."

  3. Save it as an endpoint.

    Give it a name, choose its inputs, such as a week or an employee, and the fields it returns.

  4. Call it with your Cotlet API key.

    Each endpoint gets its own address, POST https://cotlet.dev/api/v1/custom/<name>. You send JSON in and get JSON back, from the same signed-in ClockShark session.

02 Endpoints

Example endpoints you could build for ClockShark

Cotlet ships no fixed list of ClockShark endpoints. You decide which endpoints you build and what each one returns.

  • POST /api/v1/custom/timesheets-with-alerts

    Timesheets with alerts

    Employee, job, hours and alert for each shift that needs a look

  • POST /api/v1/custom/schedule-for-day

    Schedule for a day

    Shifts by employee with job, address and start time

  • POST /api/v1/custom/hours-by-job

    Hours by job

    Tracked hours per job for a period, for job costing

  • POST /api/v1/custom/time-off-waiting

    Time off waiting

    Requests still waiting for approval, with their dates

  • POST /api/v1/custom/add-shift writes

    Add a shift

    A draft shift for an employee on a job, with its start and end

A call to an endpoint you built could look like this:

Request

curl -X POST "https://cotlet.dev/api/v1/custom/timesheets-with-alerts" \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"week": "2026-11-16"}'

The answer is JSON, with your fields under data:

Response · 200 OK

{
  "data": [
    {
      "employee": "Luis M.",
      "job": "42 Oak Street",
      "hours": 9.5,
      "alert": "Missing Out"
    },
    {
      "employee": "Sam K.",
      "job": "12 Pine Ave",
      "hours": 11,
      "alert": "Overtime"
    }
  ]
}

When you save an endpoint, Cotlet gives you its curl example and an OpenAPI description to paste into n8n, Make or your code.

03 Uses

What can you use your ClockShark endpoints for?

  • Schedule Cotlet endpoint Slack or email

    A Monday payroll check in n8n or Make.

    Last week's timesheets with alerts, sent to the office before payroll.

  • Schedule endpoint Google Sheets

    Job costing in a sheet.

    Hours by job pulled into Google Sheets each week.

  • Schedule endpoint Text or chat

    A crew message before the day starts.

    Tomorrow's shifts per employee, sent each evening.

  • Chat agent endpoint schedule

    Your own AI assistant.

    A chat agent that checks who is free before it offers a new job a start date.

04 Access

What can an endpoint see and change?

An endpoint works in your own ClockShark session, so it can read and change only what your ClockShark login can. An owner login sees the whole business. A team login sees what its permissions allow. You choose what each endpoint does when you build it.

An endpoint that changes something, such as adding a shift, first runs as a dry run: Cotlet shows you each request it would send, and nothing is sent. You allow the writes once in the Cotlet console and set a daily cap. A call over the cap fails whole, never half done.

05 Official API

Does ClockShark have an official API?

ClockShark: no public developer API found on clockshark.com or its help center, and developer.clockshark.com does not resolve (checked 20 Nov 2026). ClockShark has a Zapier app and a CSV Export report. The full picture with sources: Does ClockShark have an API or MCP server?

Want ChatGPT or Claude to work in ClockShark instead of code? See the ClockShark MCP server.

06 Pricing

What does it cost?

per successful call
10 credits
when a call fails
0
in the smallest pack
≈ 500 calls
free trial, no card
7 days

A call to your endpoint costs 10 credits when it succeeds and nothing when it fails, with no browser minutes on top. Credits come in one-time packs from $29 for 5,000 credits, so a pack covers about 500 successful calls. The free trial gives you 2,000 credits for 7 days, no card.

ClockShark API with Cotlet: questions

Is this an official ClockShark API?

No. Cotlet is independent and not affiliated with ClockShark. The endpoints you build run in your own signed-in ClockShark account.

Do I need to code?

Not to build an endpoint: you do the job once with your agent and save it. To call it, you need a tool that sends HTTP requests, such as n8n, Make, Zapier or a script.

What happens when ClockShark changes its screens?

An endpoint works while ClockShark works the way it did when you built it. If ClockShark changes and a call fails, you get an email. After 3 failures in a row the endpoint turns off until you rebuild it with your agent or in the console. A failed call costs nothing.

How long can a call take?

Up to 90 seconds, and the answer can be up to 1 MB of JSON.

Build your first ClockShark endpoint

Sign in once, do the job with your agent and save it as an endpoint.

Try it free now

No card. Takes about 5 minutes.