Clarra API

Name: Clarra API API
Brand: Clarra API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentProductivityCollaborationapiKey, oauth2251 EndpointsREST

For Agents

Manage Clarra legal practice records — plaintiffs, matters, communications, claim payments, recoveries, and time entries — from one API surface for AI-driven workflow automation.

Quickstart

Get started with Clarra 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:
"create a legal matter"

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

Capabilities

What an agent can do with Clarra API API.

Create and update plaintiffs, individual contacts, and company contacts via /Contacts and /Plaintiffs endpoints

Track matter records, properties, and routing tables across the firm via /Matters and /MatterProperties endpoints

Log communications including calls, emails, and texts attached to a matter via /Communications/Create endpoints

Manage claim payment invoices, commissions, and recovery transactions via /ClaimPaymentInvoices and /Recovery endpoints

GET STARTED

Start building with Clarra API API

Explore with Jentic

View OpenAPI Document

Use for: Create a new plaintiff record with contact details and an associated matter, Log a phone call communication against an active matter, Retrieve all updated matters since the last sync timestamp, Post a claim payment invoice and reconcile the recovery distribution

Not supported: Does not handle court e-filing, jurisdiction lookups, or marketing automation — use for legal practice management workflows inside Clarra only.

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

Jentic publishes the only available OpenAPI specification for Clarra API, keeping it validated and agent-ready. Clarra is a legal practice management platform built around plaintiffs, matters, claims, communications, and trust accounting, and the API exposes 251 endpoints covering the full workflow. The surface includes contact and matter CRUD, claim payment invoices and commissions, expense and revenue forecasts, recovery distribution, time entries, communications, and Clarra Docs document management. Authentication supports both an ApiKey header and OAuth 2.0 for partner integrations.

Use Cases

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

★ Plaintiff and Matter Lifecycle Management

Create plaintiffs, attach matters with their properties and routing rules, and keep both records in sync as a case moves through intake, negotiation, and recovery. The /Plaintiffs, /Matters, and /MatterProperties endpoints together support the full lifecycle from intake to settlement, while /Search lets agents find existing records before writing new ones.

Search Clarra for an existing plaintiff by name via /Search, and if not found create one via /Contacts/CreateIndividualContact then attach a new matter via /Matters.

Claim Payment and Recovery Reconciliation

Process claim payment invoices, allocate commissions, and distribute recovered funds to parties involved in a matter. The /ClaimPaymentInvoices, /ClaimsPaymentCommissions, /RecoveryDistribution, /RecoveryParty, and /RecoveryTransaction endpoints cover the accounting workflow that follows a settlement so the firm's books stay accurate.

Create a claim payment invoice for a matter, attach the commission split via /ClaimsPaymentCommissions, and post the recovery distribution to the participating parties.

Communications and Document Capture

Attach every call, email, text, and document to its matter so the case file stays complete and discoverable. The /Communications/Create endpoints record outbound and inbound interactions while /ClarraDocs endpoints store and version the documents that anchor a case.

Create a CallCommunication via /Communications/Create/CallCommunication with the matter ID, duration, and notes, then attach the recording transcript as a Clarra Doc.

Time Tracking and Forecasting

Capture billable time and expenses against matters and roll them up into firm-wide revenue and expense forecasts. The /Timeslips, /Expenses, /RevenueForecast, and /ExpenseForecast endpoints turn day-to-day data entry into rolling financial visibility.

Post a 1.5 hour time slip on matter 12345 via /Timeslips and then refresh the firm's /RevenueForecast.

AI Agent Case Intake via Jentic

An AI agent runs the firm's intake interview, captures plaintiff details, opens the matter, and logs the first communication and document — all by searching Jentic for the relevant Clarra operations and executing them in sequence. Jentic vaults the ApiKey or OAuth credential so the agent never holds the secret.

Use the Jentic search query 'create a legal matter' to find /Plaintiffs/Create and /Matters and execute them in order with the intake data collected by the agent.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

POST

/Contacts/CreateIndividualContact

Create an individual contact record

POST

/Matters

Create a new matter

POST

/Communications/Create/CallCommunication

Log a call communication against a matter

POST

/Timeslips

Capture a billable time entry

POST

/ClaimPaymentInvoices

Create a claim payment invoice

POST

/ClarraDocs/Create

Create a Clarra Doc attached to a record

GET

/RevenueForecast

Retrieve firm-level revenue forecast

POST

/Contacts/CreateIndividualContact

Create an individual contact record

POST

/Matters

Create a new matter

POST

/Communications/Create/CallCommunication

Log a call communication against a matter

POST

/Timeslips

Capture a billable time entry

POST

/ClaimPaymentInvoices

Create a claim payment invoice

Why though Jentic?

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

Credential isolation

Clarra ApiKey and OAuth tokens are stored encrypted in the Jentic vault. Agents receive scoped execution rights and never see the raw header value or OAuth token.

Intent-based discovery

Agents search Jentic by intent such as 'create a legal matter' or 'log a billable time entry' and Jentic returns the matching Clarra operations with their schemas.

Time to first call

Direct Clarra integration: 1-2 weeks to wire up matter, communications, time, and recovery flows across 251 endpoints. Through Jentic: a few hours per workflow.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Salesforce

Enterprise CRM with custom objects that can model legal matters

Choose Salesforce when the firm has already standardised on it as the system of record and needs custom objects rather than legal-specific schemas.

Alternative

HubSpot

CRM platform with contact and pipeline management

Choose HubSpot when the firm wants marketing automation alongside lighter case tracking rather than full legal practice management.

Complementary

Stripe

Payment processing for fee and trust account collections

Pair Stripe when the firm needs to charge clients and reconcile payments back to claim payment invoices.

FAQs

Specific to using Clarra API API through Jentic.

Why is there no official OpenAPI spec for Clarra API?

Clarra does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Clarra 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 Clarra API use?

The API supports an ApiKey header and OAuth 2.0 for partner flows. Through Jentic both credential types are stored in the encrypted vault and the agent receives a scoped execution context, never the raw key.

Can I log a phone call against a matter with the Clarra API?

Yes. POST to /Communications/Create/CallCommunication with the matter ID, duration, and notes to attach the call to the case file. Email and text variants exist on the same /Communications/Create namespace.

Can I track billable time and run forecasts?

Yes. /Timeslips captures time entries by matter and user, and /RevenueForecast and /ExpenseForecast roll the entries into firm-level forecasts on demand.

How do I create a plaintiff and matter through Jentic?

Search Jentic for 'create a legal matter', load the /Contacts/CreateIndividualContact and /Matters schemas, and execute them in order. The Python SDK uses await client.search, await client.load, await client.execute.

How do I sync only updated records since the last run?

Use the /GetUpdated endpoints — for example /Communications/GetUpdatedCommunication or /ClarraDocs/GetUpdatedClarraDocsItem — to pull only records changed since a timestamp, which keeps incremental syncs efficient.