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

# Hmcts Dts Common Platform API Crime Court Hearing Cases

API to retrieve court hearing case data, including defendants, offences, and results. The API exposes 1 endpoints.

## For AI agents

Programmatically getcaselevelresults. Covers 1 operations.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- getCaseLevelResults
- Manage developer tools data programmatically
- Integrate Common Platform API Crime Court Hearing Cases into automated workflows
- Query and filter Common Platform API Crime Court Hearing Cases records by parameters
- Monitor Common Platform API Crime Court Hearing Cases operational status and events

## Use cases

### Developer Tools Operations

Use the Common Platform API Crime Court Hearing Cases to perform developer tools operations programmatically. The API provides 1 endpoints covering core functionality including getcaselevelresults.

Example prompt: Call GET /cases/{case_id}/results to getcaselevelresults

### Data Retrieval and Monitoring

Query Common Platform API Crime Court Hearing Cases 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 Crime Court Hearing Cases endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

AI agents discover and call Common Platform API Crime Court Hearing Cases 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 'getcaselevelresults', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /cases/{case_id}/results | getCaseLevelResults |

## Key resources

- **Cases** — Operations related to Cases

## Why Jentic

- **Setup:** Wiring the Crime Court Hearing Cases API by hand means coding its single results lookup against the service host and handling errors and retries yourself, even though it declares no auth scheme. Through Jentic you install once, import the Court Hearing Cases API from the API Directory, and your agent calls it.
- **Permission scoping:** This API puts the case id in the URL path (/cases/{case_id}/results), so a rule can pin your agent to one case: it can read that case's results and nothing else. This is the only operation exposed, and you choose whether the agent may call it.
- **Credential handling:** This Court Hearing Cases API declares no credential, so there is nothing to store. If your deployment later requires one, your own Jentic One instance stores it encrypted and injects it at execution time so it never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'get case-level results by case id', and Jentic returns the matching Court Hearing Cases operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the Common Platform API Crime Court Hearing Cases use?

The Common Platform API Crime Court Hearing Cases 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 getcaselevelresults with the Common Platform API Crime Court Hearing Cases?

Yes. Use the GET /cases/{case_id}/results 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 Crime Court Hearing Cases?

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

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

### How many endpoints does the Common Platform API Crime Court Hearing Cases have?

The Common Platform API Crime Court Hearing Cases exposes 1 endpoints covering cases operations.

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

Yes. Because you self-host Jentic One, your own rules decide which operations and credentials the agent may use, and this API exposes only one operation: GET /cases/{case_id}/results. You can set a rule that lets the agent read a single case's results and nothing else, since the case id sits in the URL path. You also choose whether the agent may call that operation at all.