Integrate the Clio API.Caddi writes and runs the integration for you.
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.
- 99%of agent runs complete successfully
- ~45 minon average to build your first agent
- 1M+back-office tasks completed
The connection is a project before it does anything.
Before the first record moves: an app registration, credentials, token refresh, and somewhere to host and monitor the code. 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.
Register an app, store Clio credentials, refresh tokens and code around the rate limits.
Connect your Clio account once. Caddi holds the connection.
The job doesn't stop at Clio.
An intake, a filing or a client update also runs through email, documents and the other systems your team works in. The Clio API only reaches Clio.
Each extra system is another API, another set of credentials, another integration to own.
One automation runs across every tool the job touches, each through its API.
Someone has to own the code.
API versions change, fields get added and your process moves.
A developer patches and redeploys the integration each time.
The person who does the work updates it by showing or describing the change. Every automation is reviewed before it runs in production, and every run is logged.
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.
When to build the Clio integration in-house
When you have engineers and the integration is your product, or you need one narrow sync between two systems and someone to own it. When the goal is getting Clio work off someone's desk, the build is the slow part, and Caddi does it for you.
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.
Everything Caddi does with Clio.
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. Steps that need a person's judgment are handed to Copilot or Claude, and Caddi monitors those too.
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.