Clarra API
Agent-ready OpenAPI document · curated by JenticProductivityCollaborationapiKey, oauth2251 EndpointsREST
Know of an official OpenAPI document? Contribute it →
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.
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 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.
Install Jentic One Beta
Connect the Clarra API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Clarra 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.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fclarra.com%2Fclarra" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fclarra.com%2Fclarra" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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 Clarra 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
Capture time slips and expense entries against a matter via /Timeslips and /Expenses endpoints
Run revenue and expense forecasts at the firm or matter level via /RevenueForecast and /ExpenseForecast endpoints
Create, update, and search Clarra Docs documents via /ClarraDocs/Create, /ClarraDocs/Update, and /ClarraDocs/Query
Use Cases
Patterns agents use Clarra 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 securely stores 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
POST
/ClarraDocs/Create
Create a Clarra Doc attached to a record
GET
/RevenueForecast
Retrieve firm-level revenue forecast
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Clarra by hand means handling its ApiKey header alongside an OAuth2 flow and mapping calls across its large set of legal-practice operations yourself. Through Jentic you install once, import Clarra from the API Directory, store the key once, and your agent calls it.
Permission scoping
You choose which Clarra operations the agent may call, so you can limit it to the operations it needs, such as creating an individual contact or a timeslip, and leave the rest out of the allowed set unless you add them.
Credential isolation
Your Clarra API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'create a matter' or 'log a timeslip in Clarra', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
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 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 with Jentic One, the self-hosted execution layer.
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.
Can I limit what my agent is allowed to do with the Clarra API?
Yes. Because Jentic One is self-hosted, you set the rules on your own instance, and you choose exactly which Clarra operations the agent may call. You can restrict it to just the endpoints it needs, such as /Contacts/CreateIndividualContact to create an individual contact or /Timeslips to capture a billable time entry, and leave the rest of the 251 operations out of the allowed set unless you add them. The stored ApiKey or OAuth credential is injected only when one of those permitted operations runs, so the agent can never call an operation you did not approve.
GET STARTED