Workever API · unofficial, by Cotlet

Create your own Workever API

Workever: no public API, API key or developer docs found on workever.com (checked 20 Nov 2026). With Cotlet you can build your own. Do a job once with your AI agent in your Workever 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 Workever 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 Workever. Workever is a trademark of its owner. If Workever's own integrations cover what you need, use them first.

curl
curl -X POST "https://cotlet.dev/api/v1/custom/jobs-for-day" \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"date": "2026-11-21"}'
Node.js
const url = "https://cotlet.dev/api/v1/custom/jobs-for-day";
const res = await fetch(url, {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.COTLET_API_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({ date: "2026-11-21" }),
});
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/jobs-for-day",
    headers={"Authorization": f"Bearer {key}"},
    json={"date": "2026-11-21"},
)
data = res.json()["data"]
Response 200 OK · JSON
{
  "data": [
    {
      "time": "08:30",
      "customer": "Dana R.",
      "site": "4 Mill Lane",
      "engineer": "Mark",
      "status": "scheduled"
    },
    {
      "time": "10:30",
      "customer": "Tom H.",
      "site": "18 Park Rd",
      "engineer": "Mark",
      "status": "scheduled"
    }
  ]
}

01 Build

How do you build a Workever endpoint with Cotlet?

  1. Sign in to Workever 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 the jobs on this day with the time, customer, site, engineer and status."

  3. Save it as an endpoint.

    Give it a name, choose its inputs, such as a date or an engineer, 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 Workever session.

02 Endpoints

Example endpoints you could build for Workever

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

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

    Jobs for a day

    Time, customer, site, engineer and status for each job

  • POST /api/v1/custom/overdue-invoices

    Overdue invoices

    Invoice, customer, amount and days overdue

  • POST /api/v1/custom/open-quotes

    Quotes waiting for an answer

    Quote, customer, amount and date sent

  • POST /api/v1/custom/customer-sites

    A customer's sites

    Sites and assets for one customer

  • POST /api/v1/custom/add-job-note writes

    Add a job note

    A note saved on a job, with its date

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

Request

curl -X POST "https://cotlet.dev/api/v1/custom/jobs-for-day" \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"date": "2026-11-21"}'

The answer is JSON, with your fields under data:

Response · 200 OK

{
  "data": [
    {
      "time": "08:30",
      "customer": "Dana R.",
      "site": "4 Mill Lane",
      "engineer": "Mark",
      "status": "scheduled"
    },
    {
      "time": "10:30",
      "customer": "Tom H.",
      "site": "18 Park Rd",
      "engineer": "Mark",
      "status": "scheduled"
    }
  ]
}

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 Workever endpoints for?

  • Schedule Cotlet endpoint Slack or email

    A morning report in n8n or Make.

    Today's jobs by engineer, sent to Slack or email before the vans leave.

  • Schedule endpoint Google Sheets

    A cash sheet.

    Overdue invoices pulled into Google Sheets every Monday.

  • Website form endpoint free slots

    A booking form on your own website.

    Free slots read from Workever when a customer asks for a visit.

  • Voice or chat agent endpoint next slot

    Your own AI receptionist.

    A voice or chat agent that checks the next free slot in Workever before it offers a time.

04 Access

What can an endpoint see and change?

An endpoint works in your own Workever session, so it can read and change only what your Workever 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 job note, 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 Workever have an official API?

Workever: no developer docs or API keys found (checked 20 Nov 2026). Workever has a Zapier app with 9 triggers and 17 actions on the Ultimate plan. The full picture with sources: Does Workever have an API or MCP server?

Want ChatGPT or Claude to work in Workever instead of code? See the Workever 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.

Workever API with Cotlet: questions

Is this an official Workever API?

No. Cotlet is independent and not affiliated with Workever. The endpoints you build run in your own signed-in Workever 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 Workever changes its screens?

An endpoint works while Workever works the way it did when you built it. If Workever 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 Workever 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.