The Legatics API (Application Programming Interface) lets you connect Legatics to your firm's other systems and tools. Rather than working only inside the Legatics interface, you can use the API to read and write Legatics data programmatically, automating workflows, feeding data into dashboards, or building custom integrations tailored to your firm.
Note: The API is included for all Legatics customers at no additional cost.
Overview
What the API is
An API is a standard way for software systems to communicate with each other. The Legatics API exposes your transaction data (matters, lists, signing, data rooms, and more) so that other authorised systems can access it securely and in real time.
You don't need to export spreadsheets or manually transfer data. The API gives connected systems direct, controlled access to the information they need.
How it works
The Legatics API follows the REST standard, which means it works over standard web protocols and returns data in JSON format. Any system capable of making web requests can connect to it.
Access is controlled through OAuth 2.0 with PKCE (Proof Key for Code Exchange), an industry-standard authorisation protocol. This means:
No passwords are shared between systems
Access is granted through a secure, time-limited token
Your system admin controls which applications are authorised and what they can access
Access can be revoked at any time without changing user credentials
To connect an application to the Legatics API, a system admin first creates a connected app in the Administration System. The connected app defines what the integration is, what data it can access, and how it authenticates.
What you can do with it
The Legatics API enables a wide range of use cases, including:
Pulling live matter and list data into your firm's internal dashboards or reporting tools
Integrating Legatics with document management systems (DMS) beyond the native iManage and NetDocuments integrations
Building custom workflows that combine Legatics data with other firm systems
Tip: Want to connect an AI tool or assistant so it can read and update live transaction data? Use the MCP server rather than the API. Read Legatics MCP explained.
What data you can access
The specific data accessible via the API depends on the scopes assigned to a connected app. Scopes are defined when a system admin creates the connected app. Examples include read access to matters, lists, and users, as well as write access where the integration needs to update records.
Note: A full list of available scopes is provided when creating a connected app in the Administration System.
Security and compliance
How access is controlled
All API access flows through connected apps. There are no shared passwords or long-lived credentials. Each connected app:
Is created and managed by a system admin
Has a defined, limited set of permissions (scopes)
Authenticates using short-lived access tokens
Can be disabled or deleted at any time
Data residency
API responses only return data from your Legatics environment. No data is shared between customers.
Note: If you have questions about API security for your firm's compliance requirements, contact your Legatics account manager or consult our security whitepaper.
Getting started
To start using the Legatics API, a system admin needs to create a connected app. The connected app generates the credentials the external system needs to authenticate. Read Create and manage connected apps for step-by-step setup instructions.
For your API base URL and the browsable API reference for your instance, read Finding your Legatics API and MCP URLs. If you need further help getting set up, contact your Legatics account manager or reach out to Legatics support.
Next step: Connected apps explained