canonical: https://jentic.com/apis/swaggerhub.hmcts-dts/digital-case-system-dcs-case-administration-apis # Hmcts Dts Digital Case System (DCS) case administration APIs DCS Case Administration API Specification. The API exposes 4 endpoints secured with bearer authentication. ## For AI agents Programmatically submit case and defendant details, send updated defendant details. Covers 4 operations with bearer authentication. ## Scope Does not handle payments, communications, or crm - use for developer tools only. ## Capabilities - Submit case and defendant details - Send updated defendant details - Add defence representation - Query and filter Digital Case System (DCS) case administration APIs records by parameters - Monitor Digital Case System (DCS) case administration APIs operational status and events ## Use cases ### 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. Example prompt: 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. Example prompt: 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. Example prompt: Search Jentic for 'submit case and defendant details', load the operation schema, and execute with Jentic-managed credentials ## Key endpoints | 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 | ## Key resources - **Case** — Operations for case ## Why Jentic - **Setup:** Wiring the Digital Case System case administration API by hand means learning its bearer token auth, pointing at the SwaggerHub-hosted host with the version in the base path, and handling request and error shapes yourself. Through Jentic you install once, import it from the API Directory, store the token once, and your agent calls it. - **Permission scoping:** The API puts the case URN and defendant referral in the URL path (/case/{caseUrn}/defendant/{defendantReferral}/...), so a rule can pin your agent to one case: it can add defendants, register defence representation, and attach material for that case and nothing else. You choose the operations it may call, so only the ones you list are included. - **Credential handling:** 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. - **Discovery method:** 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. ## Related APIs - **Github** — Alternative developer tools API - **Gitlab** — Alternative developer tools API ## FAQ ### 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.