canonical: https://jentic.com/apis/swaggerhub.hmcts-dts/common-platform-api-scheduling-and-listing-court-s

# Hmcts Dts Common Platform API Scheduling and Listing Court Schedule

Scheduling and Listing API providing the court schedule. The API exposes 1 endpoints.

## For AI agents

Programmatically getcourtschedulebycaseurn. Covers 1 operations.

## Scope

Does not handle payments, communications, or crm - use for hr and recruiting only.

## Capabilities

- getCourtScheduleByCaseUrn
- Manage hr recruiting data programmatically
- Integrate Common Platform API Scheduling and Listing Court Schedule into automated workflows
- Query and filter Common Platform API Scheduling and Listing Court Schedule records by parameters
- Monitor Common Platform API Scheduling and Listing Court Schedule operational status and events

## Use cases

### HR and Recruiting Operations

Use the Common Platform API Scheduling and Listing Court Schedule to perform hr recruiting operations programmatically. The API provides 1 endpoints covering core functionality including getcourtschedulebycaseurn.

Example prompt: Call GET /case/{case_urn}/courtschedule to getcourtschedulebycaseurn

### Data Retrieval and Monitoring

Query Common Platform API Scheduling and Listing Court Schedule 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.

Example prompt: Poll the primary Common Platform API Scheduling and Listing Court Schedule endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

AI agents discover and call Common Platform API Scheduling and Listing Court Schedule 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.

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /case/{case_urn}/courtschedule | getCourtScheduleByCaseUrn |

## Key resources

- **Court Schedule** — Court Schedule API

## Why Jentic

- **Setup:** Wiring the Scheduling and Listing Court Schedule API by hand means coding its single schedule lookup against the service host and handling errors and retries yourself, even though it declares no auth scheme. Through Jentic you install once, import the Court Schedule API from the API Directory, and your agent calls it.
- **Permission scoping:** This API puts the case URN in the URL path (/case/{case_urn}/courtschedule), so a rule can pin your agent to one case: it can read that case's court schedule and nothing else. This is the only operation exposed, and you choose whether the agent may call it.
- **Credential handling:** This Court Schedule API declares no credential, so there is nothing to store. If your deployment later requires one, your own Jentic One instance stores it encrypted and injects it at execution time so it never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'get a court schedule by case URN', and Jentic returns the matching Court Schedule operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Greenhouse** — Alternative hr recruiting API
- **Lever** — Alternative hr recruiting API
- **Workday** — Complementary hr recruiting API

## FAQ

### What authentication does the Common Platform API Scheduling and Listing Court Schedule use?

The Common Platform API Scheduling and Listing Court Schedule uses no authentication. 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 getcourtschedulebycaseurn with the Common Platform API Scheduling and Listing Court Schedule?

Yes. Use the GET /case/{case_urn}/courtschedule 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 Scheduling and Listing Court Schedule?

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 getcourtschedulebycaseurn through Jentic?

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

### How many endpoints does the Common Platform API Scheduling and Listing Court Schedule have?

The Common Platform API Scheduling and Listing Court Schedule exposes 1 endpoints covering court schedule operations.

### Can I limit what my agent is allowed to do with the Common Platform Court Schedule API?

Yes. Jentic One is self-hosted, so your own rules decide which operations and credentials the agent may use. This API exposes a single operation, GET /case/{case_urn}/courtschedule, and you choose whether the agent may call it at all. Because the case URN sits in the URL path, you can write a rule that pins the agent to one case so it reads only that case's court schedule and nothing else.