Hmcts Dts API Common Platform Prosecutor Interface

Name: API Common Platform Prosecutor Interface API
Brand: API Common Platform Prosecutor Interface
Availability: InStock

Browse all Swaggerhub Hmcts Dts APIs

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsSource Controlbearer4 Endpoints

Install Jentic One Beta

Connect the API Common Platform Prosecutor Interface to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the API Common Platform Prosecutor Interface, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with API Common Platform Prosecutor Interface API.

Submit Prosecution operation

Get Submission Operation

Integrate API Common Platform Prosecutor Interface into automated workflows

GET STARTED

Start building with API Common Platform Prosecutor Interface API

Explore with Jentic

View OpenAPI Document

For Agents

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

Use for: I need to submit prosecution operation, I want to submit materials operation, Search for submission operation, Find all case / application results

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

Use Cases

Patterns agents use API Common Platform Prosecutor Interface API for, with concrete tasks.

★ 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.

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.

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.

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

Key Endpoints

4 endpoints — crime api providing information on common platform prosecutor interface (cppi).

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

POST

/prosecutions

Submit Prosecution operation

POST

/prosecutions/{caseURN}/materials

Submit materials operation

GET

/submissions/{submissionId}

Get Submission Operation

GET

/results

Get case / application results

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

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.

Intent-based discovery

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.

Time to first call

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Github

Alternative developer tools API

Choose Github when you need a different approach to developer tools operations

Alternative

Gitlab

Alternative developer tools API

Choose Gitlab when you need a different approach to developer tools operations

FAQs

Specific to using API Common Platform Prosecutor Interface API through Jentic.

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.