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

# Hmcts Dts Common Platform API Crime Court List Publisher

API for court list publishing service. The API exposes 6 endpoints.

## For AI agents

Programmatically publish court list, publish sjp court list to cath. Covers 6 operations.

## Scope

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

## Capabilities

- Publish court list
- Get court list publish statuses
- Cleanup old publish status records and blob files
- Download court list (e.g. PDF)
- Monitor Common Platform API Crime Court List Publisher operational status and events

## Use cases

### Developer Tools Operations

Use the Common Platform API Crime Court List Publisher to perform developer tools operations programmatically. The API provides 6 endpoints covering core functionality including publish court list, publish sjp court list to cath, get court list publish statuses.

Example prompt: Call POST `/api/court-list-publish/publish` to publish court list

### Automated court-list-publish Management

Automate court-list-publish operations by combining multiple Common Platform API Crime Court List Publisher endpoints. Agents can publish sjp court list to cath and then get court list publish statuses in a single workflow.

Example prompt: Call POST `/api/court-list-publish/sjp/publishCourtList` to publish sjp court list to cath, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Common Platform API Crime Court List Publisher 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 'publish court list', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/api/court-list-publish/publish` | Publish court list |
| POST | `/api/court-list-publish/sjp/publishCourtList` | Publish SJP court list to CaTH |
| GET | `/api/court-list-publish/publish-status` | Get court list publish statuses |
| GET | `/api/court-list-publish/publish-status-cleanup` | Cleanup old publish status records and blob files |
| POST | `/api/court-list-publish/download` | Download court list (e.g. PDF) |
| GET | `/api/files/download/{fileId}` | Download file by ID |

## Key resources

- **court-list-publish** — Operations related to court-list-publish
- **files** — Operations related to files

## Why Jentic

- **Setup:** Wiring the Crime Court List Publisher by hand means coding its publish, status, and download calls against the service host and handling retries yourself, even though it declares no auth scheme. Through Jentic you install once, import the Court List Publisher from the API Directory, and your agent calls it.
- **Permission scoping:** This API puts the file id in the URL path (`/api/files/download/{fileId}`) while the publish operations carry their target in the request body, so scoping is operations-only: you limit the agent to the operations it needs, such as checking publish status or downloading a file, and leave out publishing a court list unless you add it.
- **Credential handling:** This Court List Publisher 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 'publish a court list' or 'check publish status', and Jentic returns the matching Court List Publisher 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 List Publisher use?

The Common Platform API Crime Court List Publisher 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 publish court list with the Common Platform API Crime Court List Publisher?

Yes. Use the POST `/api/court-list-publish/publish` 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 List Publisher?

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 publish court list through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'publish court list'. Jentic returns the matching Common Platform API Crime Court List Publisher 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 List Publisher have?

The Common Platform API Crime Court List Publisher exposes 6 endpoints covering court-list-publish, files operations.

### Can I limit what my agent is allowed to do with the Common Platform API Crime Court List Publisher?

Yes. Because you run Jentic One yourself, your own rules decide which of this API's operations the agent may call, and scoping here is operations-only. You can allow read actions such as getting publish statuses (GET `/api/court-list-publish/publish-status`) or downloading a file by ID (GET `/api/files/download/{fileId}`) while withholding write actions such as publishing a court list (POST `/api/court-list-publish/publish`) or publishing an SJP court list to CaTH. The agent can only invoke the operations you have granted, so publishing stays off until you explicitly add it.