Hmcts Dts Digital Case System (DCS) case administration APIs

Name: Digital Case System (DCS) case administration APIs
Brand: Digital Case System (DCS) case administration APIs
Availability: InStock

Browse all Swaggerhub Hmcts Dts APIs

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsSource Controlbearer

Install Jentic One Beta

Connect the Digital Case System (DCS) case administration APIs to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Digital Case System (DCS) case administration APIs, 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 Digital Case System (DCS) case administration APIs.

Submit case and defendant details

Send updated defendant details

Add defence representation

GET STARTED

Start building with Digital Case System (DCS) case administration APIs

Explore with Jentic

View OpenAPI Document

For Agents

Programmatically submit case and defendant details, send updated defendant details. Covers 4 operations with bearer authentication.

Use for: I need to submit case and defendant details, I want to send updated defendant details, Search for add defence representation, Find all submit material

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

Use Cases

Patterns agents use Digital Case System (DCS) case administration APIs for, with concrete tasks.

★ Developer Tools Operations

Use the Digital Case System (DCS) case administration APIs to perform developer tools operations programmatically. The API provides 4 endpoints covering core functionality including submit case and defendant details, send updated defendant details, add defence representation.

Call POST /case/{caseUrn}/defendants to submit case and defendant details

Automated Case Management

Automate case operations by combining multiple Digital Case System (DCS) case administration APIs endpoints. Agents can send updated defendant details and then add defence representation in a single workflow.

Call POST /case/{caseUrn}/defendant/{defendantReferral} to send updated defendant details, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Digital Case System (DCS) case administration APIs 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 case and defendant details', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

4 endpoints — dcs case administration api specification.

METHOD

PATH

DESCRIPTION

POST

/case/{caseUrn}/defendants

Submit case and defendant details

POST

/case/{caseUrn}/defendant/{defendantReferral}

Send updated defendant details

POST

/case/{caseUrn}/defendant/{defendantReferral}/defenceRepresentation

Add defence representation

POST

/case/{caseUrn}/material

Submit material

POST

/case/{caseUrn}/defendants

Submit case and defendant details

POST

/case/{caseUrn}/defendant/{defendantReferral}

Send updated defendant details

POST

/case/{caseUrn}/defendant/{defendantReferral}/defenceRepresentation

Add defence representation

POST

/case/{caseUrn}/material

Submit material

Why Jentic?

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

Credential isolation

Your Digital Case System bearer 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 'add a defendant to a case' or 'attach case material', and Jentic returns the matching 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 Digital Case System (DCS) case administration APIs through Jentic.

What authentication does the Digital Case System (DCS) case administration APIs use?

The Digital Case System (DCS) case administration APIs 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 case and defendant details with the Digital Case System (DCS) case administration APIs?

Yes. Use the POST /case/{caseUrn}/defendants endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Digital Case System (DCS) case administration APIs?

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 case and defendant details through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'submit case and defendant details'. Jentic returns the matching Digital Case System (DCS) case administration APIs operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Digital Case System (DCS) case administration APIs have?

The Digital Case System (DCS) case administration APIs exposes 4 endpoints covering case operations.

Can I limit what my agent is allowed to do with the Digital Case System (DCS) case administration APIs?

Yes. Because you run Jentic One yourself, your own rules decide which of the four operations the agent may call and which credentials it may use, so you can allow only submitting case and defendant details while blocking the rest. Since the case URN and defendant referral sit in the URL path, such as /case/{caseUrn}/defendant/{defendantReferral}, a rule can pin the agent to a single case so it can add defendants, register defence representation, and attach material for that case and nothing else. Only the operations you list are made available to the agent, and the stored bearer token is injected at execution time rather than exposed to it.