Lexamica API

Name: Lexamica API
Brand: Lexamica API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentProductivityCollaborationoauth29 EndpointsREST

For Agents

Manage legal cases, attach documents, and route referrals through Lexamica's case management platform with OAuth 2.0 access.

Install Jentic One Beta

Connect the Lexamica API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Lexamica API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Lexamica API.

Open and update legal matters with POST /cases, GET /cases/{id}, and PUT /cases/{id}

List the firm's open and closed cases via GET /cases with pagination

Capture inbound referrals from intake forms or partners through POST /referrals and inspect them with GET /referrals

GET STARTED

Start building with Lexamica API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for Lexamica API, keeping it validated and agent-ready. Lexamica provides legal document automation and case management for law firms and legal-ops teams, exposing endpoints for managing cases, attaching and retrieving documents, and routing client referrals through OAuth 2.0 with granular scopes and IP filtering. The 9-endpoint surface focuses on the case lifecycle, document handling, and inbound referral capture so firms can integrate intake and matter management into their broader stack.

Use Cases

Patterns agents use Lexamica API for, with concrete tasks.

★ Intake-to-matter automation

A law firm captures website intake submissions and partner referrals as Lexamica referrals via POST /referrals, then converts qualified leads into matters with POST /cases. The integration eliminates manual rekeying between the intake form and the case management system, reducing intake-to-engagement time and ensuring no referral is lost in an inbox.

POST /referrals with the prospect's name, contact, and incident summary, then if qualified, POST /cases with the matter type and reference back to the referral id.

Document attachment workflow

After a client signs a retainer or uploads supporting evidence, the firm's portal calls POST /documents to attach the file to a Lexamica case and later retrieves the catalogue with GET /documents for matter review. Centralising document references in the case record keeps attorney-client artefacts auditable and avoids local-drive sprawl.

POST /documents with case_id, document type 'retainer', and the storage URL of the signed PDF, then verify GET /documents lists it for that matter.

Partner referral routing

Co-counsel and referral partners send qualified prospects into the firm's intake. The integration accepts the partner's structured payload and posts it to POST /referrals with the partner identifier attached, then GET /referrals lets the intake team review and triage. This removes email handoff and gives partners a clean API endpoint to integrate against.

POST /referrals with partner_id 'firm_alpha' and the prospect's matter type, then GET /referrals filtered to last 24 hours for the intake team's morning review.

AI agent matter triage via Jentic

An AI legal-ops agent triages new client emails. When a new matter is identified, the agent searches Jentic for 'create a new legal case' or 'capture a client referral', loads the matching Lexamica operation, and executes with the OAuth tokens held in the Jentic vault. The agent opens the case, attaches the email as a document, and never sees raw OAuth secrets.

Use Jentic to search 'open a new legal case', load POST /cases, supply matter type 'employment', and attach the originating email via POST /documents.

Key Endpoints

9 endpoints — jentic publishes the only available openapi specification for lexamica api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/cases

Open a new legal case.

GET

/cases

List cases.

GET

/cases/{id}

Get a case by id.

PUT

/cases/{id}

Update a case.

POST

/referrals

Capture a new referral.

POST

/documents

Attach a document.

GET

/documents

List attached documents.

POST

/cases

Open a new legal case.

GET

/cases

List cases.

GET

/cases/{id}

Get a case by id.

PUT

/cases/{id}

Update a case.

POST

/referrals

Capture a new referral.

POST

/documents

Attach a document.

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Lexamica OAuth 2.0 access and refresh tokens are stored encrypted in the Jentic MAXsystem vault. Agents receive scoped access (read or write) to /cases, /documents, and /referrals — raw OAuth secrets and refresh tokens never enter agent context.

Intent-based discovery

Agents search Jentic with phrases like 'open a legal matter' or 'attach a document to a case' and get the matching Lexamica operation across the 9 endpoints with its full input schema, so the agent never has to browse Lexamica docs.

Time to first call

Direct integration: 1-2 days for OAuth flow, scope mapping, IP-filter setup, and case/document plumbing. Through Jentic: under an hour to search, load, and execute the first call.

FAQs

Specific to using Lexamica API through Jentic.

Why is there no official OpenAPI spec for Lexamica API?

Lexamica does not publish a maintained OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Lexamica via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Lexamica API use?

Lexamica uses OAuth 2.0 authorization code flow with granular read and write scopes and supports IP filtering on the client. The authorization endpoint is https://api.lexamica.com/oauth/authorize and tokens are issued at https://api.lexamica.com/oauth/token. Through Jentic the OAuth tokens are stored encrypted in the MAXsystem vault.

Can I open and update cases with the Lexamica API?

Yes. POST /cases creates a new matter, GET /cases/{id} retrieves it, and PUT /cases/{id} updates fields such as status or assigned attorney. GET /cases lists matters for the authenticated firm so an integration can paginate the active book.

What are the rate limits for the Lexamica API?

Lexamica does not publish exact rate-limit numbers in the public spec. Treat the 9 endpoints as standard OAuth-secured REST: paginate /cases and /documents listings, retry idempotent reads on 429 with backoff, and avoid concurrent writes on the same case_id.

How do I create a new case through Jentic?

Run 'pip install jentic', search for 'open a new legal case', and Jentic returns POST /cases with its schema. Load the operation, supply the matter type, client, and metadata, and execute. Jentic injects the OAuth bearer token automatically and refreshes it as needed.

Lexamica API

Connect the Lexamica API to your agent

Capabilities

Start building with Lexamica API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs