canonical: https://jentic.com/apis/swaggerhub.hmcts-dts/common-platform-api-refdata-court-hearing-judges

# Hmcts Dts Common Platform API Refdata Court Hearing Judges

Reference Data API providing information on Judges associated with a Court Hearing. The API exposes 1 endpoints.

## For AI agents

Programmatically getjudgebyid. Covers 1 operations.

## Scope

Does not handle payments, communications, or crm - use for identity and authentication only.

## Capabilities

- getJudgeById
- Manage identity auth data programmatically
- Integrate Common Platform API Refdata Court Hearing Judges into automated workflows
- Query and filter Common Platform API Refdata Court Hearing Judges records by parameters
- Monitor Common Platform API Refdata Court Hearing Judges operational status and events

## Use cases

### Identity and Authentication Operations

Use the Common Platform API Refdata Court Hearing Judges to perform identity auth operations programmatically. The API provides 1 endpoints covering core functionality including getjudgebyid.

Example prompt: Call GET /judges/{judge_id} to getjudgebyid

### Data Retrieval and Monitoring

Query Common Platform API Refdata Court Hearing Judges resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.

Example prompt: Poll the primary Common Platform API Refdata Court Hearing Judges endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

AI agents discover and call Common Platform API Refdata Court Hearing Judges 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 none tokens manually.

Example prompt: Search Jentic for 'getjudgebyid', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /judges/{judge_id} | getJudgeById |

## Key resources

- **Judges** — Operations related to Judges

## Why Jentic

- **Setup:** Wiring this Judges reference API by hand means pointing at its SwaggerHub-hosted mock server, tracking the version in the base path, and handling the response shape yourself. Through Jentic you install once, import it from the API Directory, and your agent calls it.
- **Permission scoping:** This API puts the judge id in the URL path (/judges/{judge_id}), so a rule can pin your agent to one judge record: it reads that judge and nothing else. You choose the operations it may call, so only the read you need is included unless you add more.
- **Credential handling:** This API declares no authentication, so there is no secret to pass. If the live endpoint later requires a credential, it is stored once, encrypted, by your own Jentic One instance and injected at execution time, never entering the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'get a judge by id', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Auth0** — Alternative identity auth API
- **Okta** — Alternative identity auth API

## FAQ

### What authentication does the Common Platform API Refdata Court Hearing Judges use?

The Common Platform API Refdata Court Hearing Judges uses no authentication. 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 getjudgebyid with the Common Platform API Refdata Court Hearing Judges?

Yes. Use the GET /judges/{judge_id} endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Common Platform API Refdata Court Hearing Judges?

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 getjudgebyid through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'getjudgebyid'. Jentic returns the matching Common Platform API Refdata Court Hearing Judges operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Common Platform API Refdata Court Hearing Judges have?

The Common Platform API Refdata Court Hearing Judges exposes 1 endpoints covering judges operations.

### Can I limit what my agent is allowed to do with the Common Platform API Refdata Court Hearing Judges?

Yes. Jentic One is self-hosted, so you set the rules that decide which operations your agent may call, and this API exposes only one, GET /judges/{judge_id} to read a judge by id. You can allow just that read and, because the judge id lives in the URL path, pin the agent to a single judge record so it retrieves that one entry and nothing more. Any credential the endpoint later needs is held and injected by your own Jentic One instance, so the agent never handles it directly.