canonical: https://jentic.com/apis/clarra.com/clarra # Clarra API 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. ## For AI agents Manage Clarra legal practice records - plaintiffs, matters, communications, claim payments, recoveries, and time entries - from one API surface for AI-driven workflow automation. ## Scope Does not handle court e-filing, jurisdiction lookups, or marketing automation - use for legal practice management workflows inside Clarra only. ## Capabilities - 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 ### 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. Example prompt: 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. Example prompt: 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. Example prompt: 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. Example prompt: 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. Example prompt: 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 | 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 | ## Key resources - **Plaintiffs** — Create, read, update, and search plaintiff records and their attached documents and notes - **Matters** — Manage matter records, properties, routing tables, and lifecycle states - **Communications** — Log calls, emails, and texts against matters with download and edit support - **ClaimPaymentInvoices** — Track claim payment invoices, commissions, and recovery distributions - **ClarraDocs** — Create, update, search, and version documents linked to plaintiffs and matters - **Timeslips** — Capture billable time entries by matter and user - **Expenses** — Record expenses and feed them into matter and firm-level forecasts ## Why Jentic - **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 handling:** 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. - **Discovery method:** 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 - **Salesforce** — Enterprise CRM with custom objects that can model legal matters - **HubSpot** — CRM platform with contact and pipeline management - **Stripe** — Payment processing for fee and trust account collections ## FAQ ### 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.