Clio APIConnect Clio without building on its API
Clio has a public REST API (v4) with webhooks. Anyone can create a Clio developer account and register an app. Clio Manage and Clio Grow sit on separate developer portals, so an integration that uses both needs two apps and two user authorizations. If you're reading the docs because you need Clio to talk to the rest of your stack, Caddi does that without you writing or maintaining integration code: you show it the job once, and it runs it across Clio and your other tools.
- APIREST (JSON), v4
- AuthOAuth 2.0
- AccessSelf-serve
What the Clio API gives you
- Type
- REST (JSON), v4
- Authentication
- OAuth 2.0
- Who can get access
- Anyone can create a Clio developer account and register an app. Clio Manage and Clio Grow sit on separate developer portals, so an integration that uses both needs two apps and two user authorizations.
- What it covers
- Matters, contacts, time and expense entries, documents, bills, communications, calendar entries and tasks, plus webhooks.
- Limits
- Clio Manage allows 50 requests per minute per access token at peak hours (more off-peak). The Clio Grow API allows 3 requests per second per app per region.
Official docs: docs.developers.clio.com. Checked September 2026. Vendors change access terms, so confirm with Clio before you build.
Building on the Clio API vs. having Caddi run it
| The job | Build it on the API | With Caddi |
|---|---|---|
| Getting access | Register an app, get Clio credentials, and manage tokens and refreshes. | Connect your Clio account once. Caddi holds the connection. |
| Writing the integration | A developer maps fields, handles pagination, retries and rate limits, and writes the sync. | You show Caddi the Clio task the way you'd train a new hire. It writes verified code for it. |
| Steps the API doesn't cover | Screens with no endpoint stay manual, or need a separate RPA tool. | Caddi uses a secure, audited browser session where there's no API, in the same automation. |
| The other systems in the loop | Each extra tool is another API, another set of credentials, another integration to own. | One automation runs across all the tools the job touches. |
| Keeping it running | Someone owns the code when the API version, fields or your process change. | Every automation is reviewed before it runs in production, and every run is logged. |
Building on the API is the right call when you have engineers and the integration is your product. When the goal is getting Clio work off someone's desk, the build is the slow part.
What teams usually want the Clio API for
Initials-Based File Naming
Caddi looks up claim numbers in the matter system to confirm the assigned paralegal and renames documents with the correct initials, reducing cross-referencing work.
Docketed Mail Uploads
Caddi cross-checks docketed mail items, uploads the required documents to the board mail folder, and archives processed files — reducing manual tracking for legal operations teams.
Payment Order Uploads
Caddi batch-uploads payment order PDFs to the correct matters and verifies each assignment before finalizing.
Check PDF Uploads
Caddi renames check PDFs to a standard format, uploads them to the correct matter, and shares them with clients through the client portal.
Clio API questions
Does Clio have an API?
Yes. Clio has a public REST API (v4) with webhooks, authenticated with OAuth 2.0. The official documentation is at https://docs.developers.clio.com/.
How do I get access to the Clio API?
Anyone can create a Clio developer account and register an app. Clio Manage and Clio Grow sit on separate developer portals, so an integration that uses both needs two apps and two user authorizations.
Does the Clio API have rate limits?
Clio Manage allows 50 requests per minute per access token at peak hours (more off-peak). The Clio Grow API allows 3 requests per second per app per region.
Can I connect Clio to my other tools without writing code against its API?
Yes. With Caddi you show the Clio task once, the way you'd train a new hire, and Caddi builds it as verified code that runs across Clio and the other tools the job touches. Where a step has no API, Caddi uses a secure, audited browser session in the same automation.
Do I need a developer to automate Clio with Caddi?
No. There is no integration code for you to write or maintain. Every automation Caddi builds for Clio is reviewed before it runs in production, and every run is logged.
Connect Clio without the build.
Drop your work email and pick a time. We'll show you Caddi running your Clio workflow end to end.