If you’re building an integration, automation, or custom workflow, our API is designed to help you connect LeanLaw with the other tools your firm relies on.
For the most up-to-date documentation, endpoint reference, authentication details, and examples, please use our developer portal:
What is an API (and why would I use it)?
An API (Application Programming Interface) is a set of rules that lets two programs securely communicate with each other.
Without an API, moving information (like clients, matters, or time entries) between systems often requires manual work—copying and pasting data line by line. With an API, a compatible service can exchange data with LeanLaw automatically, saving time and reducing errors.
How secure is an API key?
An API key works like a secure credential that grants approved access to specific LeanLaw data for the service you connect.
API keys are:
Unique and randomized
Revocable at any time (deleting a key permanently prevents future use)
Controlled by permissions (only authorized users can create/view keys)
What data can be accessed?
LeanLaw’s API supports building workflows around common firm operations—such as working with clients/matters and operational data needed for integrations.
For the current list of supported resources, write capabilities, and any limits/requirements, refer to the live documentation here:
Who can create or see API keys?
API keys are managed in LeanLaw settings and are visible only to users who have the appropriate firm-level permissions (for example, users who can access firm setup settings).
Getting started
Generate an API key in LeanLaw (in your firm settings).
Use that key to authenticate requests to the LeanLaw REST API.
Follow the endpoint reference and examples in the developer portal:
Need help?
If you have questions about what’s possible with the API, recommended integration approaches, or troubleshooting authentication, contact LeanLaw's Solution Engineering team and we’ll help you get moving.