Integrate the iManage API.Caddi writes and runs the integration for you.
iManage has a REST API (the iManage Universal API). Your firm's iManage Work admin registers the app as a client application in Control Center. The full API reference sits behind an iManage login.
- 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.
Register an app, store iManage credentials, refresh tokens.
Connect your iManage account once. Caddi holds the connection.
The job doesn't stop at iManage.
An intake, a filing or a client update also runs through email, documents and the other systems your team works in. The iManage API only reaches iManage.
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 iManage API gives you
- Type
- REST (JSON)
- Authentication
- OAuth 2.0
- Who can get access
- Your firm's iManage Work admin registers the app as a client application in Control Center. The full API reference sits behind an iManage login.
- What it covers
- Documents, workspaces, folders and their metadata in iManage Work.
Official docs: docs.imanage.com. Checked September 2026. Vendors change access terms, so confirm with iManage before you build.
When to build the iManage 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 iManage work off someone's desk, the build is the slow part, and Caddi does it for you.
What teams usually want the iManage API for
Matter workspace creation
Caddi creates the iManage workspace for each new matter using the firm's template and files the initial intake documents.
Inbound email filing
Caddi files matter-related email and attachments from Outlook directly into the correct iManage workspace.
Conflict-check support
Caddi pulls relevant documents from iManage to support the conflict-check review and routes the result to the right team.
Everything Caddi does with iManage.
iManage API questions
Does iManage have an API?
Yes. iManage has a REST API (the iManage Universal API), authenticated with OAuth 2.0. The official documentation is at https://docs.imanage.com/cc-help/10.5.0/en-US/Applications.html.
How do I get access to the iManage API?
Your firm's iManage Work admin registers the app as a client application in Control Center. The full API reference sits behind an iManage login.
Can I connect iManage to my other tools without writing code against its API?
Yes. With Caddi you show the iManage task once, the way you'd train a new hire, and Caddi builds it as verified code that runs across iManage 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 iManage with Caddi?
No. There is no integration code for you to write or maintain. Every automation Caddi builds for iManage is reviewed before it runs in production, and every run is logged.