iManage API
A REST API (v2) exists and is documented at docs.imanage.com. Access requires app registration in iManage Control Center, admin approval, and an active license; there is no open developer program. Docs are scattered across multiple sources with inconsistent versioning.
Frequently asked questions
iManage scores F on Supergood's API Report Card. A REST API (v2) exists and is documented at docs.imanage.com. Access requires app registration in iManage Control Center, admin approval, and an active license; there is no open developer program. Docs are scattered across multiple sources with inconsistent versioning.
Without a usable official API, teams fall back on manual exports, file drops, or one-off vendor integrations. The other option is an unofficial API layer like Supergood that automates the authenticated web app directly. Site terms may apply to any integration approach, and how they apply is a determination each team makes for itself.
iManage is the leading Knowledge Work Platform specializing in document and email management for law firms, corporate legal departments, and professional services organizations.
Legal, Typically for large and mid-size law firms, corporate legal departments, accounting firms, and professional services organizations managing high volumes of sensitive documents and emails. Law firms and legal departments use iManage daily to store, organize, and retrieve documents and emails associated with client matters.
8/10, iManage is the dominant legal DMS with an estimated 65-70% market share in the legal sector. Revenue is ~$262M. It has 333+ G2 reviews (4.3 stars), 585+ tracked enterprise customers on Enlyft, and serves 4,000+ organizations worldwide.
Yes, iManage holds extremely critical operating data for legal organizations: all client matter documents, attorney work product, privileged communications, contracts, litigation files, corporate governance records, and email correspondence.
~31 years old, founded 1995. Originally a public company, acquired by HP/Autonomy, then spun out as independent in 2015.
Difficulty finding current API documentation; docs are scattered and versioned inconsistently. API access requires app registration and admin approval, creating friction for developers. Full sourced list under Sources below.
Common alternatives include NetDocuments, OpenText (eDOCS), M-Files, Worldox, LexWorkplace. Graded alternatives appear under "More from the report card" below.
Supergood's grades measure one thing: can a customer's engineering team get their own data out programmatically? Supergood checks six things (whether a real API exists, how access is gated, data coverage, auth quality, docs and developer experience, and stability) and rolls them into a letter grade. Supergood re-verifies grades, and they only move on evidence.
Yes, via a managed API layer. Supergood builds REST APIs and MCP servers for authenticated enterprise web apps, so AI agents and internal tools can read and write data programmatically. Site terms may apply to any integration approach, and how they apply is a determination each team makes for itself.
iManage has partial MCP support. iManage markets an official iManage MCP Server on its platform page as the way tools like Microsoft Copilot, Harvey, and Legora reach governed content. Public install documentation and a registry listing were not found, so access appears limited to customers and partners.
Partially. MCP support for iManage exists but is incomplete, so what MCP clients like Claude, Cursor, and Codex can reach depends on what the available server covers.