HMCTS Common Platform case administration status tracking APIs

Name: HMCTS Common Platform case administration status tracking APIs API
Brand: HMCTS Common Platform case administration status tracking APIs
Availability: InStock

★ Only Publicly Available OpenAPI DocumentAnalyticsWeb Analyticsbearer2 EndpointsREST

For Agents

Connect the HMCTS Common Platform case administration status tracking APIs to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the HMCTS Common Platform case administration status tracking 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.

Install Jentic One Beta (Self-Hosted)

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

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 HMCTS Common Platform case administration status tracking APIs API.

Healthcheck endpoint to get status of CP service

Send status updates on transaction sent earlier

Integrate HMCTS Common Platform case administration status tracking APIs into automated workflows

Query and filter HMCTS Common Platform case administration status tracking APIs records by parameters

GET STARTED

Start building with HMCTS Common Platform case administration status tracking APIs API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use HMCTS Common Platform case administration status tracking APIs API for, with concrete tasks.

★ Analytics Operations

Use the HMCTS Common Platform case administration status tracking APIs to perform analytics operations programmatically. The API provides 2 endpoints covering core functionality including healthcheck endpoint to get status of cp service, send status updates on transaction sent earlier.

Call GET /healthcheck to healthcheck endpoint to get status of cp service

Data Retrieval and Monitoring

Query HMCTS Common Platform case administration status tracking APIs 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 HMCTS Common Platform case administration status tracking APIs endpoint, compare response to last known state, and alert if changed

AI Agent Integration via Jentic

AI agents discover and call HMCTS Common Platform case administration status tracking 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 'healthcheck endpoint to get status of cp service', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

2 endpoints — hmcts common platform case administration status tracking apis.

METHOD

PATH

DESCRIPTION

GET

/healthcheck

Healthcheck endpoint to get status of CP service

POST

/transaction/{transactionRef}

Send status updates on transaction sent earlier

GET

/healthcheck

Healthcheck endpoint to get status of CP service

POST

/transaction/{transactionRef}

Send status updates on transaction sent earlier

Why though Jentic?

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

Credential isolation

HMCTS Common Platform case administration status tracking APIs bearer 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., 'healthcheck endpoint to get status of cp service') and Jentic returns the matching HMCTS Common Platform case administration status tracking APIs operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct HMCTS Common Platform case administration status tracking APIs 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.

Alternative

Mixpanel

Alternative analytics API

Choose Mixpanel when you need a different approach to analytics operations

Alternative

Amplitude

Alternative analytics API

Choose Amplitude when you need a different approach to analytics operations

Complementary

Segment

Complementary analytics API

Choose Segment when you need a complementary approach to analytics operations

Complementary

Pendo

Complementary analytics API

Choose Pendo when you need a complementary approach to analytics operations

FAQs

Specific to using HMCTS Common Platform case administration status tracking APIs API through Jentic.

What authentication does the HMCTS Common Platform case administration status tracking APIs use?

The HMCTS Common Platform case administration status tracking APIs uses a Bearer token in the Authorization header. 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 healthcheck endpoint to get status of cp service with the HMCTS Common Platform case administration status tracking APIs?

Yes. Use the GET /healthcheck endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the HMCTS Common Platform case administration status tracking 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 healthcheck endpoint to get status of cp service through Jentic?

Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'healthcheck endpoint to get status of cp service'. Jentic returns the matching HMCTS Common Platform case administration status tracking APIs operation with its input schema. Load the schema and execute the call — credentials are injected automatically.

How many endpoints does the HMCTS Common Platform case administration status tracking APIs have?

The HMCTS Common Platform case administration status tracking APIs exposes 2 endpoints covering healthcheck, transaction operations.