CKM REST API
REST API for the Clinical Knowledge Manager — 48 operations across 39 paths covering archetypes (list, search, ADL/XML/mindmap retrieval, specialisation parent, status by asset version, MD5 hash, import, trunk update, delete), templates (list, search, OET/OPT retrieval, file-set URL, required archetypes, embedded templates, validation report, status read and update, import, trunk update, delete), the archetype/template union "resources" view with the instance publisher namespace, projects and subdomains, change requests and resource proposals, and user and session management. Authentication is HTTP Basic or a JSESSIONID session header; public projects on a public instance read anonymously.
This API exposes 48 operations across 39 paths, organized into 9 resource areas, and defines 8 schemas. It is described by OpenAPI 2.0, at version 1.6.0.
Requests are made against the base URL https://ckm.openehr.org/ckm/rest/v1.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 2
CKM REST API declares
2 security schemes
for authenticating requests.
An API key is passed in the header as JSESSIONID (sessionid).
It defines a basic scheme (basicAuth).
sessionid— Once the session id is known, it can be used for authentication until expired. The provided session id is used (and validated) on making an actual request.basicAuth— Basic authentification using the CKM username and password. The provided credentials are used (and validated) on making an actual request.
Paths & Operations 48
Across 39 paths, the API surfaces 48 operations — 3 DELETE, 37 GET, 5 POST, 3 PUT. They span 9 resource areas: Archetypes, Change Requests, Projects, Resource Proposals, Resources, Sessions, Subdomains, Templates, Users. Each is listed below with its method, path, parameters, and response codes.
Endpoint for archetype-related services, including listing and getting archetypes.
Endpoint for change request-related services, including listing and getting change requests.
Endpoint for project-related services, including listing and getting projects.
Endpoint for resource proposal-related services, including listing and getting resource proposals.
Endpoint for generic resources, including archetypes and templates. May sometimes be easier to use.
Endpoint for creating a new user session or signing out.
Endpoint for subdomain-related services, including listing and getting subdomains.
Endpoint for template-related services, including listing and getting templates.
Endpoint for user-related services, including creating new users as an admin.
Schemas 8
The contract defines 8 schemas that model the data the API accepts and returns. The most detailed are TemplateValidationItem (21 properties), CkmResource (20 properties), ChangeRequest (15 properties), ResourceProposal (15 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
This is an independent, third-party profile of CKM REST API, 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.