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

# Hmcts Dts Common Platform API Refdata Court Hearing Court Houses

Reference Data API providing information on Court Houses associated with a Court Hearing. The API exposes 2 endpoints.

## For AI agents

Programmatically getcourthousebycourtidandcourtroomid, getcourthousebycourtid. Covers 2 operations.

## Scope

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

## Capabilities

- getCourthouseByCourtIdAndCourtRoomId
- getCourthouseByCourtId
- Integrate Common Platform API Refdata Court Hearing Court Houses into automated workflows
- Query and filter Common Platform API Refdata Court Hearing Court Houses records by parameters
- Monitor Common Platform API Refdata Court Hearing Court Houses operational status and events

## Use cases

### Identity and Authentication Operations

Use the Common Platform API Refdata Court Hearing Court Houses to perform identity auth operations programmatically. The API provides 2 endpoints covering core functionality including getcourthousebycourtidandcourtroomid, getcourthousebycourtid.

Example prompt: Call GET /courthouses/{court_id}/courtrooms/{court_room_id} to getcourthousebycourtidandcourtroomid

### Data Retrieval and Monitoring

Query Common Platform API Refdata Court Hearing Court Houses 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 Court Houses 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 Court Houses 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 'getcourthousebycourtidandcourtroomid', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /courthouses/{court_id}/courtrooms/{court_room_id} | getCourthouseByCourtIdAndCourtRoomId |
| GET | /courthouses/{court_id} | getCourthouseByCourtId |

## Key resources

- **Court Room** — Operations related to court room
- **Court House** — Operations related to court house

## Why Jentic

- **Setup:** Wiring this Court Houses reference API by hand means pointing at its SwaggerHub-hosted mock server, tracking the version in the base path, and mapping the nested courthouse and courtroom responses yourself. Through Jentic you install once, import it from the API Directory, and your agent calls it.
- **Permission scoping:** This API puts the court id and court room id in the URL path (/courthouses/{court_id}/courtrooms/{court_room_id}), so a rule can pin your agent to one courthouse: it reads that courthouse and its rooms and nothing else. You choose the operations it may call, so only the reads you need are 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 'look up a courthouse and its courtrooms', 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 Court Houses use?

The Common Platform API Refdata Court Hearing Court Houses 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 getcourthousebycourtidandcourtroomid with the Common Platform API Refdata Court Hearing Court Houses?

Yes. Use the GET /courthouses/{court_id}/courtrooms/{court_room_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 Court Houses?

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

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'getcourthousebycourtidandcourtroomid'. Jentic returns the matching Common Platform API Refdata Court Hearing Court Houses 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 Court Houses have?

The Common Platform API Refdata Court Hearing Court Houses exposes 2 endpoints covering court room, court house operations.

### Can I limit what my agent is allowed to do with the HMCTS Court Houses API?

Yes. Because you run Jentic One yourself, your own rules decide which of this API's operations the agent may call, and it only has the two GET reads (getCourthouseByCourtId and getCourthouseByCourtIdAndCourtRoomId) if you include them. Since the court id and court room id travel in the URL path, a rule can pin the agent to a single courthouse so it reads that courthouse and its rooms and nothing else. The agent cannot reach any operation you have not granted.