Hashlogics
Answers

Clio and MyCase APIs: what a real integration involves

Any Clio admin can authorize an app, but each token is capped at 50 calls a minute. MyCase opens its API by request.

Answered in short

5 things that decide this

  1. 01Integrating with Clio or MyCase means OAuth access the firm approves, working inside Clio's rate limits and MyCase's gated developer reference. Hashlogics builds intake, deadline and reporting tools for law firms on both, with Filevine covered separately.
  2. 02Clio Manage exposes contacts, matters, calendars, tasks, documents and billing through a REST API on OAuth 2.0. Your real design constraint is 50 requests a minute per access token at peak, with no custom increase.
  3. 03MyCase released its Open API in November 2023. It's available on the Advanced tier only, and a firm requests access through MyCase support.
  4. 04Zapier covers simple one-way syncs on either platform. It stops being enough once your write-back needs a schedule, a retry, or judgement about which record to touch.
  5. 05Every firm's plan and enabled features differ, so we confirm what your account exposes during the audit, before anything gets scoped.
Why the obvious answer is incomplete

What's exposed matters less than what you're allowed to do with it

Clio publishes real documentation, and its access model is one of the better ones in legal software. Contacts, matters, calendars, tasks, documents and billing are all reachable, and you don't need a partner deal just to read the docs. MyCase is different: its reference sits behind a login, and the API itself depends on your plan.

So the question isn't whether Clio's API can do what you want. At the level of one record, it almost certainly can. Once you need a nightly sync across every open matter, the rate limit stops being a footnote and starts deciding how the system gets built.

Auth and access

OAuth 2.0, and an admin who has to say yes

Clio authenticates with OAuth 2.0 authorization code, the same pattern DocuSign and most modern SaaS platforms use. You register an app. Your firm's Clio admin logs in and grants that app access. In return you get tokens your app uses on every later call. There's no shared key that works across every firm you connect. If you connect several firms, each one authorizes separately and can revoke it on its own.

That's a person's decision, not a technical step, and it's worth building your timeline around it. Your firm administrator, mid-trial or out for two weeks, is the actual bottleneck on most Clio integrations, not the API itself.

MyCase

MyCase: an Open API on the Advanced tier

MyCase released its public Open API in November 2023. Its own support centre says you need the Advanced tier to use it. You read the API documentation first, then contact MyCase support to request access if your use case fits.

MyCase's support article also says it doesn't support API builds directly and points firms to its certified consultants instead. In practice that means your build partner owns the integration end to end, so ask who will fix it when a field changes.

MyCase describes the API as a way to share data from your other platforms, trigger tasks and events, and connect workflows. Calls run as a MyCase user over OAuth, so your tool sees only what that user can see. Confirm which records your workflow needs against the current reference before you plan around it.

The design constraint the header carriesLive
  1. AuthorizeThe firm's admin grants your app access, per account
  2. Token issuedRate limit tracks against this token, not your app overall
  3. 50 calls / minutePeak hours, per access token; regions capped separately
  4. Queue and resumeA backlog waits its turn instead of erroring out
  5. Scheduled syncNever a live call fired per row on a page load

50 requests a minute sounds generous until you're syncing every open matter overnight. Queue it, don't fan it out.

The rate limit, in practice

Why 50 a minute forces a different shape of build

Clio Manage caps you at 50 requests a minute during peak hours, and that ceiling applies per access token, not per app. Off-peak hours allow more, but you can't design around a firm's own business hours being the slow window. Clio won't raise the limit for you, however busy your firm is. That's not a gap in the documentation; it's a stated policy.

Regions are limited separately too, so if you have a US office and a UK office, you aren't drawing on one shared pool. And Clio Grow, the intake and CRM product, sits apart from Clio Manage, the matters and billing product. If you run both, you have two things to authorize and, in effect, two systems to design against, even though they share a brand.

What this means for your build: sync on a schedule, not on demand. Queue a backlog and let it drain across the window instead of firing calls the moment a page loads. Make the sync incremental, so a nightly run only touches matters that changed, not every open file in your firm. Design it to resume where it left off if a run gets interrupted. That beats starting over and burning through the ceiling twice. Your dashboard can fan out a live API call per row and work fine in a demo with ten matters. It falls over on your real caseload.

Grow versus Manage, and when Zapier is enough

Two products, and a real line for no-code

Clio Grow is the intake and CRM side: leads, forms, the pipeline before a matter exists. The practice-management side, once a matter's open, is Clio Manage: documents, calendars, tasks, billing, trust accounting. If you run both, you authorize each separately, and a build across intake-to-invoice has to allow for both.

Zapier's Clio connector is the right call for a simple sync. Think of a new lead in Grow posting to Slack, or a signed engagement sending an email. No code, no maintenance burden on your side. It respects Clio's rate limits because Zapier built the connector to. It stops being enough once your logic needs judgement. Matching a caller to an existing contact is one case. Filing a draft in the right matter folder is another. That's where a direct build against the API earns what it costs.

Filevine

Where Filevine fits

Filevine is the third name you'll hear, especially if you run a personal injury practice. It runs its own API and partner directory, with a different data model built around projects rather than matters. We cover it on its own page, because the build questions differ from Clio's and MyCase's. For the wider picture, see what we build for law firms.

What firms actually build

The four shapes this takes

Most of what you're likely to ask for falls into one of four shapes, and each one interacts with the rate limit differently.

  • 01Intake write-back: an AI intake system, a form, or a call answers an inquiry, matches it against existing contacts, does a first-pass conflict check, and writes the qualified lead into Clio with the recording attached. This is a low, bursty call volume, so the rate limit rarely bites.
  • 02Drafting save: a document assembled from matter facts and a clause library gets saved to the right matter in Clio, with the draft marked reviewed or unreviewed. One or two calls per document, so this is cheap against the ceiling too.
  • 03Billing read: pulling time entries, invoices, and payment status out of Clio to feed a collections view or a realization report. This is where volume adds up fastest, since a firm-wide report can mean a call per matter, which is exactly the pattern that needs queuing rather than a live loop.
  • 04Dashboards: partners reviewing utilization, WIP and matter profitability pulled from Clio alongside billing and accounting data. Built to refresh on a schedule against a cache, never to hit the API live every time someone opens the page.
Proof

We built Lexpair, a LegalTech platform that matches people who need legal help with verified lawyers. Your clients would submit their case through guided forms, as Lexpair's do. AI-assisted logic sorts each case by practice area and routes it to a relevant lawyer, and admins moderate every lead from one dashboard.

Your Clio or MyCase intake build uses the same structure, with the qualified lead written into your practice system instead of a matching queue. Lexpair's CEO, Nicolas de Quesada, said: "Their attention to detail, quality of employees, and work ethic were outstanding."

Where client data travels

Confidentiality doesn't stop at the API call

Your Clio data is disclosed the moment an AI step sends it outside your systems, not when it's stored. In February 2026, a federal court in United States v. Heppner held that a defendant's own conversations with a consumer AI tool weren't privileged. What decided it was the tool's terms, which allowed disclosure and training on user inputs. No enterprise tool with no-training terms in writing was ever ruled on here. Everything turns on what your tool's contract actually says.

So your build has to name every system the matter data passes through. That means the model endpoint, any logging vendor, a prompt cache and an eval pipeline. You need zero-retention and no-training terms in writing, where you can find them. Direction of counsel gets recorded wherever work product protection depends on it, and access stays scoped to the matter rather than the whole firm. ABA Formal Opinion 512 adds the other half. A lawyer can't rely on generated output without review, and a boilerplate clause in an engagement letter isn't informed consent. You're held to the same standard your client's malpractice insurer applies to your firm.

Who to hire

Who builds Clio and MyCase integrations

Hashlogics scopes a Clio or MyCase integration from the access your firm can grant today. Clio means an app your administrator authorizes over OAuth 2.0, one token per firm, capped at 50 calls a minute at peak. MyCase means Open API credentials on the Advanced tier, requested from support in writing with your redirect URL and read or write scope. No firm has either until someone inside the firm says yes.

With access confirmed, a fixed-fee Blueprint turns it into a spec, credited in full against the build. That spec names which records we read, which we write back, and how the sync queues under Clio's ceiling. It also names every system your matter data passes through, including the model endpoint. If the plan isn't one you'd act on, you don't pay for it.

Delivery runs as fixed-price milestones. You accept each one against written criteria, such as a nightly sync that finishes inside the rate limit and touches every changed matter once. Your firm owns the code, the app registration and the tokens. Our wider legal work, and the systems we build around, sits on the law firm hub.

Questions, answered
01Which development firms integrate custom tools with Clio, MyCase or Filevine?+

Hashlogics builds intake, deadline and reporting tools on Clio and MyCase, and covers Filevine on its own page. We built Lexpair, a legal intake and matching platform, so structured intake is work we've shipped. Each project starts by confirming what your plan and account expose.

02Does Clio charge extra for API access?+

Clio doesn't publish a separate fee for API access in its own documentation. Treat any figure a vendor quotes as a claim to check against your own plan.

03Does MyCase have an API?+

Yes. MyCase released its Open API in November 2023, available on the Advanced tier. You request access through MyCase support, and MyCase points firms to certified consultants for implementation.

04When is Zapier enough for a law firm?+

Zapier is enough for simple one-way syncs, like a new lead posting to Slack or a signed engagement sending an email. You need a build when you must match callers to contacts, queue work under Clio's limit, or file drafts by matter.

05What does Hashlogics actually do on a Clio project?+

We confirm what your account exposes: which modules are on your plan, and what your intake or billing data looks like once it's out. That happens in a fixed-fee Blueprint, credited in full against the build, after a free scoping call. If the plan isn't one you'd act on, you don't pay for it.

06Which firms build custom tools that integrate with Clio and MyCase?+

A firm that can show Clio's OAuth app registration or MyCase Open API credentials, a written integration spec and named write-back behaviour. Hashlogics confirms that access first and writes the spec inside a fixed-fee Blueprint, credited in full against the build. Delivery is fixed-price milestones you accept against written criteria. Write-back means naming which contacts, matters and documents the tool creates and which it only reads.

By , CEO, HashlogicsUpdated
Start

Let’s deploy working AI into your business.

We build AI agents and automation, ship them into the tools you already run, then stay on under an agreed service level. A senior engineer reads every brief, and your call gets scheduled within 24 hours.

What happens next

  1. 01

    You send a brief or book a call

    Two minutes, whichever you prefer.

  2. 02

    A senior engineer replies within 24 hours

    Not a sales rep.

  3. 03

    Honest scoping, in writing

    And if we’re not the right fit, we say so.

Abdul Basit, CEO of Hashlogics

“I started Hashlogics because too many teams ship a demo, get paid, and disappear. We build to a standard we’d run ourselves — and we stay to keep it running.”

Abdul Basit · CEO · a direct line

Not ready to talk? Take the checklist.

12 questions to ask any AI agency before you sign. They separate a demo shop from a team that ships to production.

Get the checklist

Free · no newsletter