canonical: https://jentic.com/apis/swaggerhub.hmcts-dts/api-common-platform-prosecutor-interface

# Hmcts Dts API Common Platform Prosecutor Interface

Crime API providing information on Common Platform Prosecutor Interface (CPPI). The API exposes 4 endpoints secured with bearer authentication.

## For AI agents

Programmatically submit prosecution operation, submit materials operation. Covers 4 operations with bearer authentication.

## Scope

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

## Capabilities

- Submit Prosecution operation
- Get Submission Operation
- Integrate API Common Platform Prosecutor Interface into automated workflows
- Query and filter API Common Platform Prosecutor Interface records by parameters
- Monitor API Common Platform Prosecutor Interface operational status and events

## Use cases

### Developer Tools Operations

Use the API Common Platform Prosecutor Interface to perform developer tools operations programmatically. The API provides 4 endpoints covering core functionality including submit prosecution operation, submit materials operation, get submission operation.

Example prompt: Call POST /prosecutions to submit prosecution operation

### Automated Prosecutions Management

Automate prosecutions operations by combining multiple API Common Platform Prosecutor Interface endpoints. Agents can submit materials operation and then get submission operation in a single workflow.

Example prompt: Call POST /prosecutions/{caseURN}/materials to submit materials operation, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call API Common Platform Prosecutor Interface 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.

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /prosecutions | Submit Prosecution operation |
| POST | /prosecutions/{caseURN}/materials | Submit materials operation |
| GET | /submissions/{submissionId} | Get Submission Operation |
| GET | /results | Get case / application results |

## Key resources

- **Prosecutions** — Operations for prosecutions
- **Results** — Operations for results
- **Submissions** — Operations for submissions

## Why Jentic

- **Setup:** Wiring the Common Platform Prosecutor Interface by hand means implementing its bearer token auth, coding the prosecution and submission calls, and handling retries yourself. Through Jentic you install once, import the Prosecutor Interface from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** This API puts the case URN and submission id in the URL path (/prosecutions/{caseURN}/materials, /submissions/{submissionId}), so a rule can pin your agent to one case or submission: it can read that submission or results and nothing else. You choose the operations it may call, so writes like submitting a prosecution or adding materials are not included unless you add them.
- **Credential handling:** Your Prosecutor Interface 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.
- **Discovery method:** Agents search Jentic by intent such as 'submit a prosecution' or 'get a submission by id', and Jentic returns the matching Prosecutor Interface 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 API Common Platform Prosecutor Interface use?

The API Common Platform Prosecutor Interface 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 submit prosecution operation with the API Common Platform Prosecutor Interface?

Yes. Use the POST /prosecutions endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the API Common Platform Prosecutor Interface?

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 submit prosecution operation through Jentic?

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

### How many endpoints does the API Common Platform Prosecutor Interface have?

The API Common Platform Prosecutor Interface exposes 4 endpoints covering prosecutions, results, submissions operations.

### Can I limit what my agent is allowed to do with the Common Platform Prosecutor Interface?

Yes. Jentic One is self-hosted, so your own rules decide which operations and credentials the agent may use, and you can allow only the calls you want, such as GET /submissions/{submissionId} and GET /results while excluding writes like POST /prosecutions or POST /prosecutions/{caseURN}/materials. Because the case URN and submission id sit in the URL path, a rule can pin the agent to a single case or submission so it reads only that record and nothing else. The stored bearer token is injected at execution time within the boundaries you set.