Clio's Matter Dockets API computes court deadlines and has no way to edit them

Clio's Matter Dockets API computes court deadlines and has no way to edit them

The Clio Matter Dockets API is one of 95 APIs Clio has on apis.io, and it does one of the most valuable things in legal software. A matter docket connects a case to a court rule, and the court rule produces the calendar entries that follow from it: filing deadlines, response windows, hearing dates. A missed one can cost a client their case. The API exposes that feature in five operations, and none of them changes a docket after it is created.

What it ships

The contract is an OpenAPI 3.2 document at https://app.clio.com/api/v4, with production servers for the US, EU, Canada and Australia regions. The five operations:

Method Path What it does
GET /court_rules/matter_dockets/preview.json Preview the calendar dates a docket would create
GET /court_rules/matter_dockets.json List dockets
POST /court_rules/matter_dockets.json Create a docket
GET /court_rules/matter_dockets/{id}.json Read one docket
DELETE /court_rules/matter_dockets/{id}.json Delete a docket

The record lists an OpenAPI document, documentation, an API reference and OAuth 2.0 authorization.

The preview is the right design

The preview operation needs a jurisdiction, a trigger and a start date, and it returns the dates the docket would generate without writing anything. It is a dry run, and it is what you want from an API that writes to a lawyer’s calendar. An agent can show the deadlines to a person, get a yes, and only then call the create operation. Most APIs that write consequential data offer no such step.

No edit, so a correction is a delete and a create

There is no PATCH or PUT. If a trigger date was wrong, say a service date entered a day off, the only path is to delete the docket and create it again. The calendar entries go with it. For a feature whose purpose is getting dates right, that is a narrow surface.

The contract also differs between operations. The list, create, show and delete operations accept the X-API-VERSION header that Clio uses for minor versions (4.0.13 is the default), but the preview operation does not declare it. The delete operation documents only 204 and 403. A missing docket and an expired token are not described, though show and create both document 404 and 401.

Plan-gated

The description says Court Rules “is not available to all plan types” and links to Clio’s pricing page for which plans include it. That matters for anyone building an integration for many firms: the same call will work for one customer and fail for another, and the contract has no way to say which.

Takeaway

The Matter Dockets API gets the hard part right with a dry-run preview before anything is written. It leaves out the correction path a deadline tool needs. The reference is at docs.developers.clio.com, and Clio’s full set of 95 APIs is at apis.io/providers/clio/.

← Claude Code on Foundry Runs Through Azure API Management, and the Gateway Does the Governing
CloudWatch Takes API Keys for OpenTelemetry Traces, and SigV4 Stays the Default →