What we do
Tools
Industries
Department
How we workLet's talk →
Home/Clio/Clio API
Clio Manage API

The Clio API: From App Registration to Webhooks You Can Trust

Your integration passed every test against a US trial account. Then a firm on Clio's Canadian instance tried to connect it, and it couldn't. Clio's API is a well-documented REST API, and most of what catches developers sits around the endpoints rather than in them.

However you want to go about it
01
Version and format

API v4, JSON over HTTPS, under /api/v4 on the firm's regional host.

02
Auth

OAuth 2.0 authorization code flow. Access tokens last 30 days, and refresh tokens don't expire.

03
Regions

US app.clio.com, plus eu., ca. and au.app.clio.com, each with its own developer app.

04
Limits

Per access token, 50 requests a minute at peak hours, with a 429 and Retry-After when you go over.

From a developer account to your first Clio API call

  1. 1

    Get an account with API access

    For Clio Manage, start a trial with API access, which lasts seven days, then apply to turn it into a free developer account. Clio Grow's APIs sit on the separate Clio Platform portal, so check which product you're building for before signing up.

  2. 2

    Register a developer application

    developers.clio.com Apps New

    Give it a name, a website URL, one or more redirect URIs and the permissions it needs, and accept the developer terms. A deauthorization callback URL is optional, but worth setting so you hear when a firm disconnects. Copy the app key and secret.

    Watch for: an app registered in one region doesn't exist in the others. Serving US and EU firms means an account and an app in each.

  3. 3

    Send the user to authorize

    Redirect to /oauth/authorize on the firm's regional host with response_type=code, your client_id, a registered redirect_uri and a state value. Add redirect_on_decline=true if you'd rather handle a refusal yourself than leave the user on Clio's error page.

  4. 4

    Exchange the code for tokens

    POST to /oauth/token, form-encoded, with the code, client_id, client_secret, grant_type=authorization_code and the same redirect_uri. The code only lasts 10 minutes. You get an access token and a refresh token. Store the refresh token encrypted, along with the region it belongs to.

  5. 5

    First request: who_am_i

    Call GET /api/v4/users/who_am_i with the bearer token to confirm who you're acting as. From there, list endpoints return up to 200 records a page, and you ask for the fields you want with the fields parameter.

What Clio webhooks can tell you

Each webhook needs the model's own scope plus the webhooks scope, and an HTTPS URL.

Model Events Worth knowing
matter created, updated, deleted, matter_opened, matter_pended, matter_closed The status events save you diffing every update to spot a matter that just closed.
contact created, updated, deleted The usual trigger for pushing new clients into a CRM or conflict check.
activity created, updated, deleted Time and expense entries, for live reporting on hours without waiting for the bill.
bill, clio_payments_payment Bills: created, updated, deleted. Payments: created and updated only Payments never send a deleted event, so plan reversals around updates.
document, folder created, updated, deleted Folders use the Documents scope, not a scope of their own.
calendar_entry, task, communication created, updated, deleted Useful for deadline tracking and logging emails and calls in another system.

What stops a Clio integration a week after launch

Webhooks expire

How you'll know: Events stop arriving a few days after go-live, with no error anywhere.

Fix: A webhook expires 3 days after creation unless you set expires_at, and 31 days is the most you can ask for. Run a job that PATCHes expires_at well before it passes, and alert if a webhook isn't enabled.

The handshake never completed

How you'll know: The webhook sits in pending and nothing is delivered.

Fix: Clio's first POST carries an X-Hook-Secret header. Echo it back with a 200, or activate the webhook later with that secret. Keep the secret: every delivery is signed with it in X-Hook-Signature, an HMAC-SHA256 of the raw body.

A 410 turned the webhook off

How you'll know: A deploy briefly returned 410 Gone from your endpoint, and the subscription is now disabled.

Fix: Clio treats 410 as a request to stop, with no retries. Return 5xx during maintenance instead, so Clio backs off and tries again.

429s during the working day

How you'll know: A backfill runs fine at night and fails between morning and evening.

Fix: The 50-a-minute limit applies at peak hours: weekdays 4am to 7pm Pacific for the US and Canada regions, with EU and AU on their own local windows. Read X-RateLimit-Remaining as you go and wait out Retry-After. Clio doesn't raise limits on request.

Offset paging stops at 10,000 records

How you'll know: A full export of activities or contacts fails with a 422 partway through.

Fix: Use cursor paging with order=id(asc) and follow meta.paging.next until it's gone. It's sequential, but it has no ceiling.

Questions people ask

Does Clio have a public API?

Yes. Clio Manage has a documented REST API, version 4, secured with OAuth 2.0 and covering matters, contacts, activities, bills, calendars, tasks and documents. You build and test through Clio's developer portal. Clio Grow's APIs live on the newer Clio Platform portal.

What's the Clio App Directory?

It's Clio's listing of ready-made integrations firms can install, from email and storage to accounting and e-signature. Public apps go through Clio's launch requirements to be listed. An app built for one firm alone can stay private and never appear there.

Do I need a developer to use the Clio API?

Beyond a one-off test call, yes. OAuth with token refresh, regional hosts, the per-token limit and webhook renewal all need code that keeps running. n-frames builds and maintains Clio integrations for firms and legal-tech teams who'd rather not own that.

Can something outside Clio react automatically when a matter changes?

Yes, with webhooks. Subscribe to the matter model and Clio posts to your URL on create, update and delete, plus matter_opened, matter_pended and matter_closed. Verify each delivery's signature and renew the webhook before it expires.

What are the Clio API rate limits?

Limits are per access token. The default is 50 requests a minute during peak hours, higher off-peak, and some endpoints set their own. Every response carries X-RateLimit headers, and going over returns 429 with a Retry-After value.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.