HM Courts & Tribunals Service
HM Courts & Tribunals Service (HMCTS) is the executive agency of the UK Ministry of Justice responsible for administering the criminal, civil and family courts in England and Wales and the reserved unified tribunals across the United Kingdom. Its engineering teams publish open source code on GitHub (github.com/hmcts) and the "HMCTS way" engineering standards at hmcts.github.io, including Spectral API linting rulesets used in its API repositories.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles HM Courts & Tribunals Service the way a machine reads it — 47 machine-readable artifacts across 10 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — HM Courts & Tribunals Service scores 50.0/100 (developing), with a separate agent-readiness read of 36/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-10-17 · rubric v0.24.0
Put this on your own site. The badge is drawn live from HM Courts & Tribunals Service's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/hmcts/"
title="HM Courts & Tribunals Service on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/hmcts.svg"
alt="HM Courts & Tribunals Service Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/hmcts/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/hmcts/"
title="HM Courts & Tribunals Service on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/hmcts/card.svg"
alt="HM Courts & Tribunals Service Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile HM Courts & Tribunals Service
Each block below is one kind of artifact we hold for HM Courts & Tribunals Service. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 20
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
HM Courts & Tribunals Service Admin API
Administrative operations such as jobs can be run from this set of endpoints.
HM Courts & Tribunals Service Application Codes API
Application Codes are reference data, not managed in App Reg. They are required to provide a set repeatable data that can be used by Application List Entries, such as the title,...
HM Courts & Tribunals Service Application List Entries API
An Application List Entry records all details of an individual Application. This will always belong to an Application List.
HM Courts & Tribunals Service Application List Entry Results API
An Application List Entry Result records the result of an individual Application. Each Application can have multiple child Results and Results cannot exist without a parent Appl...
HM Courts & Tribunals Service Application Lists API
An Application List records the date, time and location at which one or more Applications is to be considered by a magistrate or delegated authority.
HM Courts & Tribunals Service Caseworkers API
The Caseworkers API from HM Courts & Tribunals Service — 5 operation(s) for caseworkers.
HM Courts & Tribunals Service Court Locations API
Court Locations are reference data, not managed in App Reg. They are a consolidation of both crown and magistrates courts where an application will be heard and resulted.
HM Courts & Tribunals Service Criminal Justice Areas API
Criminal Justice Areas are reference data, not managed in App Reg. They are officially recognized justice regions and used to classify records by jurisdiction.
HM Courts & Tribunals Service Data API
The Data API from HM Courts & Tribunals Service — 2 operation(s) for data.
HM Courts & Tribunals Service Display API
The Display API from HM Courts & Tribunals Service — 4 operation(s) for display.
HM Courts & Tribunals Service Internal API
The Internal API from HM Courts & Tribunals Service — 1 operation(s) for internal.
HM Courts & Tribunals Service Jobs API
Background job operations for asynchronous tasks (polling status across all job types).
HM Courts & Tribunals Service Notification API
The Notification API from HM Courts & Tribunals Service — 1 operation(s) for notification.
HM Courts & Tribunals Service Reports API
Endpoints to generate and retrieve CSV reports asynchronously.
HM Courts & Tribunals Service Result Codes API
Result codes are reference data, not managed in App Reg. They are required to provide a set of ways an Application List Entry can be resulted. e.g. Approved/Denied.
HM Courts & Tribunals Service Root API
The root API from HM Courts & Tribunals Service — 1 operation(s) for root.
HM Courts & Tribunals Service Standard Applicants API
Standard Applicants are reference data, not managed in App Reg. Only code, name and usage dates are exposed by reference-data endpoints and exports. Personal and contact details...
HM Courts & Tribunals Service Subscription API
The Subscription API from HM Courts & Tribunals Service — 4 operation(s) for subscription.
HM Courts & Tribunals Service Validation API
The validation API from HM Courts & Tribunals Service — 1 operation(s) for validation.
HM Courts & Tribunals Service Validation Rules API
The validation-rules API from HM Courts & Tribunals Service — 2 operation(s) for validation-rules.
Scroll within the panel for all 20 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Hmcts Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Hmcts Rate Limits
RATE LIMITSEvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Hmcts Webhooks
ASYNCAPISemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Hmcts Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
JSON Schema 17
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
application-code-get-detail-dto
JSON SCHEMAClientSubscriptionRequest
JSON SCHEMAClientSubscription
JSON SCHEMADraftValidationRequest
JSON SCHEMADraftValidationResponse
JSON SCHEMAentry-create-dto
JSON SCHEMAentry-get-detail-dto_1
JSON SCHEMAentry-get-detail-dto
JSON SCHEMAentry-update-dto
JSON SCHEMAEventPayload
JSON SCHEMAEventTypeResponse
JSON SCHEMAHmacCredentials
JSON SCHEMAjob-acknowledgement
JSON SCHEMARotateSecretRequest
JSON SCHEMARuleDetailResponse
JSON SCHEMARuleListResponse
JSON SCHEMAUpdateRuleRequest
JSON SCHEMAScroll within the panel for all 17 ·
Security Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for HM Courts & Tribunals Service — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 1
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 3
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 13
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 13 ·
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 6
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 6
The organization behind the API
Other 4
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/hmcts · machine-readable index on apis.io
This is an independent, third-party profile of HM Courts & Tribunals Service, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.