UniCourt Enterprise APIs
Browse all Unicourt APIsCommunity OpenAPI document · agent-readyHR recruitingRecruiting Atsbearer158 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Programmatically gets details for a requested attorney id., gets associated party details for a requested attorney id.. Covers 158 operations with bearer authentication.
Use for: I need to gets details for a requested attorney id., I want to gets associated party details for a requested attorney id., Search for specify the billing cycle to know the API usage., Find all all the previous 12 billing cycles.
Not supported: Does not handle payments, communications, or crm - use for hr and recruiting only.
<button><a href="/enterpriseapi/download/UniCourt-Enterprise-API-Spec.yaml" >Download UniCourt Enterprise APIs Specification</a></button>. The API exposes 158 endpoints secured with bearer authentication.
Install Jentic One Beta
Connect the UniCourt Enterprise APIs to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the UniCourt Enterprise APIs, 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%2Funicourt.com%2Funicourt-enterprise-apis" | 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%2Funicourt.com%2Funicourt-enterprise-apis" | 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 UniCourt Enterprise APIs.
Gets details for a requested Attorney ID.
Specify the billing cycle to know the API usage.
Get all the previous 12 billing cycles.
Query and filter UniCourt Enterprise APIs records by parameters
Monitor UniCourt Enterprise APIs operational status and events
Use Cases
Patterns agents use UniCourt Enterprise APIs for, with concrete tasks.
★ HR and Recruiting Operations
Use the UniCourt Enterprise APIs to perform hr recruiting operations programmatically. The API provides 158 endpoints covering core functionality including gets details for a requested attorney id., gets associated party details for a requested attorney id., specify the billing cycle to know the API usage..
Call GET /attorney/{attorneyId} to gets details for a requested attorney id.
Automated Authentication API Management
Automate authentication API operations by combining multiple UniCourt Enterprise APIs endpoints. Agents can gets associated party details for a requested attorney id. and then specify the billing cycle to know the API usage. in a single workflow.
Call GET /attorney/{attorneyId}/associatedParties to gets associated party details for a requested attorney id., then verify the result
AI Agent Integration via Jentic
AI agents discover and call UniCourt Enterprise APIs endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually.
Search Jentic for 'gets details for a requested attorney id.', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
158 endpoints — <button><a href="/enterpriseapi/download/unicourt-enterprise-api-spec.
METHOD
PATH
DESCRIPTION
GET
/attorney/{attorneyId}
Gets details for a requested Attorney ID.
GET
/attorney/{attorneyId}/associatedParties
Gets Associated Party details for a requested Attorney ID.
GET
/billingCycleUsage/{billingCycle}
Specify the billing cycle to know the API usage.
GET
/billingCycles
Get all the previous 12 billing cycles.
GET
/callbacks
Get list of callback types with count for a requested Date.
GET
/case/{caseId}
Gets case information for a requested Case ID.
GET
/case/{caseId}/attorneys
Gets Attorneys for a requested Case ID.
GET
/case/{caseId}/docketEntries
Gets Docket Entries for a requested Case ID.
GET
/attorney/{attorneyId}
Gets details for a requested Attorney ID.
GET
/attorney/{attorneyId}/associatedParties
Gets Associated Party details for a requested Attorney ID.
GET
/billingCycleUsage/{billingCycle}
Specify the billing cycle to know the API usage.
GET
/billingCycles
Get all the previous 12 billing cycles.
GET
/callbacks
Get list of callback types with count for a requested Date.
GET
/case/{caseId}
Gets case information for a requested Case ID.
GET
/case/{caseId}/attorneys
Gets Attorneys for a requested Case ID.
GET
/case/{caseId}/docketEntries
Gets Docket Entries for a requested Case ID.
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the UniCourt Enterprise APIs by hand means attaching a bearer token on every call, pointing at the enterprise host, and matching each case, attorney, and billing operation to its request shape yourself. Through Jentic you install once, import the UniCourt Enterprise APIs from the API Directory, store the token once, and your agent calls it.
Permission scoping
UniCourt puts the case id in the URL path (/case/{caseId}/...), so a rule can pin your agent to one case: it can read that case, its attorneys, and its docket entries and nothing else. You choose the operations it may call, so unrelated queries like attorney or billing lookups are not included unless you add them.
Credential isolation
Your UniCourt token 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 'get details for a case' or 'list a case's docket entries', and Jentic returns the matching UniCourt 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.
FAQs
Specific to using UniCourt Enterprise APIs through Jentic.
What authentication does the UniCourt Enterprise APIs use?
The UniCourt Enterprise APIs uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I gets details for a requested attorney id. with the UniCourt Enterprise APIs?
Yes. Use the GET /attorney/{attorneyId} endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the UniCourt Enterprise APIs?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I gets details for a requested attorney id. through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'gets details for a requested attorney id.'. Jentic returns the matching UniCourt Enterprise APIs operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the UniCourt Enterprise APIs have?
The UniCourt Enterprise APIs exposes 158 endpoints covering authentication API, usage API, case search API operations.
Can I limit what my agent is allowed to do with the UniCourt Enterprise APIs?
Yes. Because you self-host Jentic One, your own rules decide which UniCourt operations and credentials the agent may use, and it can only call what you allow. Since UniCourt puts the case ID in the URL path, such as /case/{caseId}/attorneys and /case/{caseId}/docketEntries, you can pin the agent to a single case so it reads that case, its attorneys, and its docket entries and nothing else. Unrelated calls like attorney lookups (/attorney/{attorneyId}) or billing cycle queries (/billingCycleUsage/{billingCycle}) stay off limits unless you explicitly add them.
GET STARTED