CosmoLex API

Name: CosmoLex API API
Brand: CosmoLex API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentProductivityTask Managementbearer30 EndpointsREST

For Agents

Manage law-firm contacts, matters, time entries, invoices, trust accounts, calendar events, and tasks in CosmoLex. JWT bearer-token authentication with full CRUD on each resource.

Quickstart

Get started with CosmoLex API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"log a CosmoLex time entry"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with CosmoLex API API.

Create, list, update, and delete contacts so the firm's client and counterparty records stay current

Open, edit, and close matters that anchor every billable engagement and document

Log, edit, and remove time entries against matters to drive accurate WIP and invoicing

Generate and retrieve invoices to bill clients for time and disbursements

GET STARTED

Start building with CosmoLex API API

Explore with Jentic

View OpenAPI Document

Use for: Create a new client contact in CosmoLex, List all open matters for a specific attorney, I need to log a time entry of 0.6 hours against matter M-1042, Generate an invoice for last month's work on a matter

Not supported: Does not handle court e-filing, document automation, or document storage — use for CosmoLex contact, matter, time, invoice, trust, calendar, and task management only.

Jentic publishes the only available OpenAPI document for CosmoLex API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for CosmoLex API, keeping it validated and agent-ready. The CosmoLex API gives law firms programmatic access to their cloud-based practice management workspace, covering contacts, matters, time entries, invoices, trust accounts, calendar events, and tasks across 30 endpoints. Authentication is via a JWT bearer token, and the surface follows a consistent CRUD shape per resource so workflows that touch multiple resources — such as opening a matter, logging time, and invoicing — are straightforward to assemble.

Use Cases

Patterns agents use CosmoLex API API for, with concrete tasks.

★ Time Capture from Email and Documents

Capture billable time automatically as attorneys send emails or edit documents: an agent or middleware classifies the activity, identifies the matter, and posts a time entry to CosmoLex. This shrinks the time-leak between work performed and time recorded, which is one of the largest profitability drivers for law firms.

On each tracked email, call POST /timeentries with the matter ID, duration, and narrative; then GET /timeentries to confirm it appears in the daily timesheet.

Matter Intake and Invoice Lifecycle

Onboard a new client, open a matter, log time entries against it, and generate the invoice when the engagement closes. Each step is a single endpoint call, so the intake form and billing process can be wired together without manual portal entry.

Call POST /contacts to create the client, POST /matters to open the matter, POST /timeentries as work is logged, and POST /invoices when the matter is ready to bill.

Trust Account Reconciliation Reporting

Pull every trust account, fetch the balance for each, and reconcile against the firm's accounting system on a daily cadence. Even though the API is read-only on the trust resource, the listing plus per-account fetch is enough to drive a reconciliation report and flag drift before month-end.

Call GET /trustaccounts to list all trust accounts, then GET /trustaccounts/{trustAccountId} for each to capture the balance, and post the totals into the reconciliation worksheet.

AI Agent Legal Practice Assistant via Jentic

An assistant for a managing partner answers operational questions like 'what are my open tasks today?' or 'what is the WIP on the Smith matter?' by searching Jentic for the right CosmoLex operation. The agent reasons over capabilities rather than memorising CosmoLex's 30-endpoint surface.

Search Jentic for 'list CosmoLex tasks' or 'list time entries by matter', load the matching operation, and execute it with the matter ID or attorney filter the partner asked about.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

POST

/matters

Open a new matter

POST

/contacts

Create a contact

POST

/timeentries

Log a time entry

POST

/invoices

Create an invoice

GET

/trustaccounts/{trustAccountId}

Read a trust account balance

POST

/events

Schedule a calendar event

POST

/tasks

Create a task

POST

/matters

Open a new matter

POST

/contacts

Create a contact

POST

/timeentries

Log a time entry

POST

/invoices

Create an invoice

GET

/trustaccounts/{trustAccountId}

Read a trust account balance

POST

Why though Jentic?

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

Credential isolation

The CosmoLex JWT bearer token is stored encrypted in the Jentic vault (MAXsystem). Agents receive a scoped execution handle — the JWT is injected into the Authorization header at call time, refreshed on expiry, and never enters the agent's context.

Intent-based discovery

Agents search by intent (e.g., 'log CosmoLex time entry' or 'list trust accounts') and Jentic returns the matching operation with input and response schemas, so the agent picks the right endpoint without browsing CosmoLex documentation.

Time to first call

Direct CosmoLex integration: 2-4 days for JWT auth, pagination, and consistent error mapping across the 30 endpoints. Through Jentic: under 1 hour — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Clio Manage API

Larger legal practice management platform with deeper third-party app marketplace than CosmoLex.

Choose Clio when integration breadth or large-firm scale is the priority; CosmoLex is the better fit for small firms wanting built-in trust accounting and a single tool.

Complementary

Xero Accounting API

General-ledger accounting platform that can ingest CosmoLex invoices and trust transactions.

Pair with CosmoLex when the firm uses Xero as the back-office GL and needs invoice and trust totals reflected there.

Complementary

Stripe API

Payment processor that can collect on CosmoLex invoices via card or ACH.

Pair with CosmoLex when the firm wants online invoice payment and reconciliation back into the practice ledger.

FAQs

Specific to using CosmoLex API API through Jentic.

Why is there no official OpenAPI spec for CosmoLex API?

CosmoLex publishes API documentation but not a single OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call CosmoLex API 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 CosmoLex API use?

The API uses HTTP bearer-token authentication with JWTs: every request must carry an Authorization: Bearer <jwt> header. Through Jentic the JWT is held in the encrypted vault and injected per call so the agent never sees the raw token.

Can I log a time entry against a matter with this API?

Yes. POST /timeentries creates a time entry tied to a matter ID, duration, and narrative, which is the canonical primitive for any time-capture automation built on top of CosmoLex.

Can I read trust account balances?

Yes. GET /trustaccounts lists every trust account on the firm and GET /trustaccounts/{trustAccountId} returns the detail for one account, which is enough to drive a daily reconciliation report. The current spec does not expose write operations on trust accounts.

What are the rate limits for the CosmoLex API?

The OpenAPI spec does not declare numeric rate limits. Treat HTTP 429 responses as authoritative, back off using the Retry-After header where present, and consult the CosmoLex support team for plan-specific limits before high-volume sync jobs.

How do I create a matter through Jentic?

Search Jentic for 'create CosmoLex matter', load POST /matters, and execute it with the contact ID, matter type, and description. Jentic returns the operation schema so the agent does not need to read CosmoLex docs to know which fields are required.