Clio API · unofficial, by Cotlet

Create your own Clio API

Clio: the Clio Manage API opens for 7 days on a trial, then needs an approved free developer account (checked 20 Nov 2026). With Cotlet you can build your own. Do a job once with your AI agent in your Clio 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 Clio 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 Clio. Clio is a trademark of its owner. If Clio's own integrations cover what you need, use them first.

curl
curl -X POST "https://cotlet.dev/api/v1/custom/upcoming-deadlines" \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"days": 14}'
Node.js
const url = "https://cotlet.dev/api/v1/custom/upcoming-deadlines";
const res = await fetch(url, {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.COTLET_API_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({ days: 14 }),
});
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/upcoming-deadlines",
    headers={"Authorization": f"Bearer {key}"},
    json={"days": 14},
)
data = res.json()["data"]
Response 200 OK · JSON
{
  "data": [
    {
      "date": "2026-11-24",
      "matter": "Patel v. Ruiz",
      "deadline": "Reply brief due",
      "responsible_attorney": "Ana"
    },
    {
      "date": "2026-11-27",
      "matter": "Ortiz lease",
      "deadline": "Notice period ends",
      "responsible_attorney": "Ben"
    }
  ]
}

01 Build

How do you build a Clio endpoint with Cotlet?

  1. Sign in to Clio 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 matters with a deadline in the next 14 days, with the date, matter and responsible attorney."

  3. Save it as an endpoint.

    Give it a name, choose its inputs, such as a number of days or an attorney, 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 Clio session.

02 Endpoints

Example endpoints you could build for Clio

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

  • POST /api/v1/custom/upcoming-deadlines

    Upcoming deadlines

    Date, matter, deadline and responsible attorney

  • POST /api/v1/custom/unbilled-time

    Unbilled time by matter

    Hours and amount not yet billed on each matter

  • POST /api/v1/custom/tasks-due

    Tasks due

    Tasks due in the period you name, by attorney

  • POST /api/v1/custom/find-contact

    Find a contact

    Matching contacts with their matters

  • POST /api/v1/custom/add-time-entry writes

    Add a time entry

    A time entry on the matter you name, with hours and a description

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

Request

curl -X POST "https://cotlet.dev/api/v1/custom/upcoming-deadlines" \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"days": 14}'

The answer is JSON, with your fields under data:

Response · 200 OK

{
  "data": [
    {
      "date": "2026-11-24",
      "matter": "Patel v. Ruiz",
      "deadline": "Reply brief due",
      "responsible_attorney": "Ana"
    },
    {
      "date": "2026-11-27",
      "matter": "Ortiz lease",
      "deadline": "Notice period ends",
      "responsible_attorney": "Ben"
    }
  ]
}

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

  • Schedule Cotlet endpoint Slack or email

    A Monday deadline list in n8n or Make.

    This week's deadlines by attorney, sent to Slack or email.

  • Calendar endpoint time entry

    Time from your calendar.

    Meetings in your own calendar become time entries on the right Clio matter.

  • Schedule endpoint Google Sheets

    A dashboard or a sheet.

    Unbilled time by matter, pulled into Google Sheets every Friday.

  • Chat agent endpoint contacts

    Your own intake assistant.

    A chat agent that checks whether a caller is already a client before it books a call.

04 Access

What can an endpoint see and change?

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

Clio documents a Clio Manage API; after a 7-day trial a developer applies for a free developer account, and a private app can serve one firm (checked 20 Nov 2026). Clio has apps on Zapier and Make and webhooks for apps. The full picture with sources: Does Clio have an API or MCP server?

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

Clio API with Cotlet: questions

Is this an official Clio API?

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

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