In late 2023 MyCase released an Open API, and in 2026 it is still one of the more quietly frustrating things in legal tech. The API is real and useful. It lets law firms share data between MyCase and other platforms, trigger tasks and events programmatically, and build connected workflows. The friction is everything around it: the API sits on MyCase's higher-priced tier, and MyCase itself says it does not support implementations and that you should hire a certified consultant.
So you are handed a capable API and told the build is your problem. This is a guide to what the Open API actually does, the three honest ways to integrate it, and how to keep client data privileged while you do.
What the MyCase Open API actually gives you
At a practical level, the Open API lets software outside MyCase do three things: read your firm's data (matters, contacts, activities, invoices), write back to it (create time entries, tasks, calendar events), and react to events so other tools stay in sync. That is enough to wire MyCase into an intake form, an accounting system, a document tool, or an AI assistant. It is not enough, on its own, to make any of that happen. The API is the socket. Someone still has to build the plug.
The three honest ways to integrate it
There is no single right answer here. The right path depends on whether you have an engineer, how custom the workflow is, and how sensitive the data is.
1. Build it in-house
If you have a developer, the Open API is documented and you can build directly against it. This is the cheapest path in dollars and the most expensive in attention. The traps are the ones the docs gloss over: token scoping, rate limits, fields the API quietly ignores, and keeping the integration alive when MyCase changes something. Good fit for a firm with real engineering capacity and a simple, stable workflow.
2. Use an open-source connector
For the common case of connecting MyCase to an AI assistant, an MCP connector already does the hard part. It sits on top of the Open API and exposes MyCase to a tool like Claude through a controlled interface, so the assistant can look up a matter or log time without anyone hand-rolling API calls. Oktopeak maintains an open-source MyCase MCP connector you can run yourself. Good fit if your workflow is AI-assisted and you are comfortable with a little setup.
3. Done-for-you setup
If you want the connection working without touching the API, this is the path MyCase points you toward when it says hire a consultant. The value is not writing the integration, it is owning the parts that bite later: least-privilege tokens, an audit trail, error handling, and a setup your firm actually controls. Good fit for a firm that wants the outcome, not the project.
The part most integration guides skip: keeping it privileged
MyCase holds privileged client data, so an integration is not just a technical question, it is a confidentiality one. Three things matter and are easy to get wrong:
- Least-privilege tokens. Scope the API token to only what the integration needs. A reporting tool does not need write access.
- An audit trail. Record every read and write the integration makes, so you can answer who accessed what. This is also what an ethics review will ask for.
- Access, not just retention. For AI integrations, the exposure is that a model provider saw the data, not only whether it was logged. The clean answer for privileged content is a zero-data-retention path so nothing is retained by the model provider.
Where Oktopeak fits
We build legal integrations for regulated firms, and the MyCase Open API is squarely in that lane. If you want to run it yourself, our MyCase MCP connector is open source and free. If you want it done for you, our Guided Setup starts at $1,700 and gets your MyCase connection working, scoped and audited, without you touching the API. Larger custom integrations are scoped per firm after a free discovery call.
If MyCase told you to find a consultant for your Open API integration, that is the gap we fill. See how the MyCase integration works or book a free discovery call.