Add-on .legal Public API

Build the integrations your organisation needs. Our Public API gives you programmatic access to your legal entities, contracts and assets, so you can connect .legal directly to the systems your team already works in.

.legal Public API documentation showing endpoints for legal entities, contracts and assets

API request creating a legal entity in the .legal compliance platform with custom field values

Full Access to Your Core Compliance Data

Read and write the data that matters most. The Public API covers legal entities, contracts and assets with the same core operations across all three, so you can build reliable integrations without workarounds.

Legal Entities: Create, retrieve, update and delete vendors, customers, group companies and more. List and filter your existing entities, look up a specific one by ID, or update individual fields without resending the whole record.
Contracts: Create, retrieve and update contracts, and paginate through your contract list with filtering by business area and date. Replace linked business areas in a single call and update custom field values in bulk.
Assets and Suppliers: Everything you can do with contracts, plus supplier management. Add a supplier to an asset, look one up, or remove it again.
Supporting Endpoints: Retrieve your active business areas and entity templates, including custom field schemas, so external systems know the shape of your data before sending anything.

Versioned API endpoint structure showing /api/v1/ path for stable compliance integrations

Built for Stability

An integration is only useful if it keeps working. That is why every endpoint is versioned and every change is designed to be safe for the integrations you have already built.

Versioned Endpoints: Every endpoint is versioned through the URL, for example /api/v1/legal-entities, so you always know exactly which legal entity you are building against.
Additive Changes Only: Within a major version we only add new fields, endpoints and enum values. Your integration should tolerate these without breaking.
Long Deprecation Notice: If an endpoint is ever retired, it will be marked as deprecated first, with at least 12 months' notice before it is switched off.