API Access

The Lextree API is a read-only, cursor-paginated JSON API over your subscription’s data. It’s available on the Enterprise plan Enterprise — this page is an orientation to what it offers, and the full endpoint-by-endpoint reference lives in the interactive docs linked below.

What the API Offers

The API exposes two families of data: the records you work with in the app, and the resources that attach to those records across every module.

Record Types and Related Resources

Record types are the records themselves — legal entities, contracts, boards, filings — each reachable at its own path. Related resources attach to records across every module: attachments (files), calendar events, workflows, and timeline entries. Both families share the same authentication, pagination, and error handling, so once you’ve queried one record type, every other type and resource works the same way.

Authentication and Endpoints

Every request carries a Bearer API key in the Authorization header. A record type’s path segment is its record_type slug — for example, entity_registry for legal entities:

1
2

curl https://app.example.com/api/v1/entity_registry \
  -H "Authorization: Bearer lt_live_ab12cd34_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"

An interactive reference is served at /api/v1/docs (Swagger UI) — the authoritative source for every endpoint, parameter, and response shape.

Getting and Using a Key

An admin creates and revokes API keys on the Subscription page — see creating and revoking a key. A key is shown once, in full, at creation time and can’t be retrieved again, so store it securely.

A key is scoped to the whole subscription rather than to a person: it carries no access-group membership, so it can read across every module the subscription has enabled — including records an individual teammate wouldn’t see in the app. Scope who holds a key accordingly.

Connecting an AI Assistant

The same API key works with the Lextree MCP server, which is available to Enterprise API keys and exposes the same records and related resources as tools an AI assistant can call — the same authentication, module gating, and read-only guarantee as the REST API, with no separate rate-limit allowance. Connection setup is documented in the app’s own product documentation.

Rate Limits and Full Reference

Requests are limited per subscription rather than per key, so all of a subscription’s keys share one budget: a burst-and-refill token bucket, plus a cap on requests running at once. There are no daily caps. Exceeding a limit returns a 429 response telling you how long to wait before retrying.

For the complete set of endpoints, parameters, and response fields — including record-type schemas, filtering, and the related-resource catalog — use the Swagger UI at /api/v1/docs. This page covers only what you need to get started; the interactive reference is kept current automatically as your subscription’s schema changes.