iManage APIConnect iManage without building on its API
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. If you're reading the docs because you need iManage 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 iManage and your other tools.
- APIREST (JSON)
- AuthOAuth 2.0
- AccessRegistered by your admin
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.
Building on the iManage API vs. having Caddi run it
| The job | Build it on the API | With Caddi |
|---|---|---|
| Getting access | Register an app, get iManage credentials, and manage tokens and refreshes. | Connect your iManage 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 iManage 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 iManage work off someone's desk, the build is the slow part.
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.
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. Where a step has no API, Caddi uses a secure, audited browser session in the same automation.
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.
Connect iManage without the build.
Drop your work email and pick a time. We'll show you Caddi running your iManage workflow end to end.