Lawmatics APIConnect Lawmatics without building on its API
Lawmatics has a REST API. Customers only, on request: you email api@lawmatics.com to turn on Developer Settings for your account, then create a Developer App to get a client ID and secret (no plan requirement is stated). If you're reading the docs because you need Lawmatics 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 Lawmatics and your other tools.
- APIREST (JSON)
- AuthOAuth 2.0
- AccessCustomers, by request
What the Lawmatics API gives you
- Type
- REST (JSON)
- Authentication
- OAuth 2.0 (authorization code grant)
- Who can get access
- Customers only, on request: you email api@lawmatics.com to turn on Developer Settings for your account, then create a Developer App to get a client ID and secret (no plan requirement is stated).
- What it covers
- Contacts, companies, matters, tasks, events, activity, and invoicing, plus outbound webhooks for set events such as new matters, status changes, and form submissions.
- Limits
- 150 requests per minute per firm, and going over returns HTTP 429.
Official docs: docs.lawmatics.com. Checked September 2026. Vendors change access terms, so confirm with Lawmatics before you build.
Building on the Lawmatics API vs. having Caddi run it
| The job | Build it on the API | With Caddi |
|---|---|---|
| Getting access | Register an app, get Lawmatics credentials, and manage tokens and refreshes. | Connect your Lawmatics 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 Lawmatics 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 Lawmatics work off someone's desk, the build is the slow part.
What teams usually want the Lawmatics API for
Inbound intake capture
Caddi reads the referral email or intake form attachment, creates the Lawmatics contact and matter, and attaches the source document.
Converted-matter handoff
When a Lawmatics matter converts, Caddi opens the matter in practice management, creates the folder structure, and files the signed engagement letter.
Signed-agreement filing
Caddi picks up the completed e-signature, updates the Lawmatics record, renames the document to the firm's convention, and files it to the client.
Lawmatics API questions
Does Lawmatics have an API?
Yes. Lawmatics has a REST API, authenticated with OAuth 2.0 (authorization code grant). The official documentation is at https://docs.lawmatics.com/.
How do I get access to the Lawmatics API?
Customers only, on request: you email api@lawmatics.com to turn on Developer Settings for your account, then create a Developer App to get a client ID and secret (no plan requirement is stated).
Does the Lawmatics API have rate limits?
150 requests per minute per firm, and going over returns HTTP 429.
Can I connect Lawmatics to my other tools without writing code against its API?
Yes. With Caddi you show the Lawmatics task once, the way you'd train a new hire, and Caddi builds it as verified code that runs across Lawmatics 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 Lawmatics with Caddi?
No. There is no integration code for you to write or maintain. Every automation Caddi builds for Lawmatics is reviewed before it runs in production, and every run is logged.
Connect Lawmatics without the build.
Drop your work email and pick a time. We'll show you Caddi running your Lawmatics workflow end to end.