Hmcts Dts Common Platform API Case URN Mapper
Browse all Swaggerhub Hmcts Dts APIs★ Only Publicly Available OpenAPI DocumentMaps GeolocationGeocodingnone1 EndpointsREST
For Agents
Programmatically getcaseidbycaseurn. Covers 1 operations.
Use for: I need to getcaseidbycaseurn, Find available maps geolocation operations, Get the current status of Common Platform API Case URN Mapper resources, List all records from Common Platform API Case URN Mapper
Not supported: Does not handle payments, communications, or crm — use for maps and geolocation only.
Case URL Mapper specification. The API exposes 1 endpoints.
Install Jentic One Beta
Connect the Common Platform API Case URN Mapper to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Common Platform API Case URN Mapper, 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.
1
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 | sh2
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 instanceJentic 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 Common Platform API Case URN Mapper API.
getCaseIdByCaseUrn
Manage maps geolocation data programmatically
Integrate Common Platform API Case URN Mapper into automated workflows
Query and filter Common Platform API Case URN Mapper records by parameters
Monitor Common Platform API Case URN Mapper operational status and events
Use Cases
Patterns agents use Common Platform API Case URN Mapper API for, with concrete tasks.
★ Maps and Geolocation Operations
Use the Common Platform API Case URN Mapper to perform maps geolocation operations programmatically. The API provides 1 endpoints covering core functionality including getcaseidbycaseurn.
Call GET /urnmapper/{case_urn} to getcaseidbycaseurn
Data Retrieval and Monitoring
Query Common Platform API Case URN Mapper resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.
Poll the primary Common Platform API Case URN Mapper endpoint, compare response to last known state, and alert if changed
AI Agent Integration via Jentic
AI agents discover and call Common Platform API Case URN Mapper 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.
Search Jentic for 'getcaseidbycaseurn', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
1 endpoints — case url mapper specification.
METHOD
PATH
DESCRIPTION
GET
/urnmapper/{case_urn}
getCaseIdByCaseUrn
GET
/urnmapper/{case_urn}
getCaseIdByCaseUrn
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Common Platform API Case URN Mapper none credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.
Intent-based discovery
Agents search by intent (e.g., 'getcaseidbycaseurn') and Jentic returns the matching Common Platform API Case URN Mapper operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct Common Platform API Case URN Mapper integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Common Platform API Case URN Mapper API through Jentic.
What authentication does the Common Platform API Case URN Mapper use?
The Common Platform API Case URN Mapper uses no authentication. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.
Can I getcaseidbycaseurn with the Common Platform API Case URN Mapper?
Yes. Use the GET /urnmapper/{case_urn} 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 Case URN Mapper?
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 getcaseidbycaseurn through Jentic?
Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'getcaseidbycaseurn'. Jentic returns the matching Common Platform API Case URN Mapper operation with its input schema. Load the schema and execute the call — credentials are injected automatically.
How many endpoints does the Common Platform API Case URN Mapper have?
The Common Platform API Case URN Mapper exposes 1 endpoints covering caseidbycaseurn operations.
GET STARTED