How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Cadasto Additional API

Cadasto's own extension surface on top of openEHR REST, described by the vendor as "Cadasto-specific... This API only works within Cadasto". 27 operations across Datamap definitions and Datamap data (a simplified alias-to-openEHR-path JSON format for search, read and write), episodes of care with activate/deactivate/destroy, a FHIR ValueSet terminology helper, user info and caseload, and Kubernetes-style startup/live/ready health probes. Bearer JWT auth. No operationIds are declared in the published document.

This API exposes 27 operations across 17 paths, organized into 7 resource areas. It is described by OpenAPI 3.1.1, at version 1.0.0.

Requests are made against a single base URL, https://api.customer.cadasto.io.

27 operations 17 paths 0 schemas 3 DELETE13 GET2 HEAD3 POST6 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.1
API Version
1.0.0
Base URL
https://api.customer.cadasto.io
Authentication
HTTP Bearer
Resource Areas
7

Authentication & Security 1

Cadasto Additional API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth). By default, every request must be authenticated.

Paths & Operations 27

Across 17 paths, the API surfaces 27 operations — 3 DELETE, 13 GET, 2 HEAD, 3 POST, 6 PUT. They span 7 resource areas: Health, User, Datamap Definition, Datamap Query, Terminology, Episode, Admin. Each is listed below with its method, path, parameters, and response codes.

Health 3

Health checks for monitoring and orchestration. Used for startup, liveness, and readiness probes.

GET
/extra/health/startup
Startup probe
→ 200
GET
/extra/health/live
Liveness probe
→ 200
GET
/extra/health/ready
Readiness probe
→ 200
User 2

User information and caseload for the authenticated user.

GET
/extra/v1/user/info
Get user info
3 params → 200400404
GET
/extra/v1/user/caseload
Get user caseload
→ 200
Datamap Definition 6

Management of datamap definitions (XML). Defines what data is available and how it can be mapped/queried for Cadasto-specific integrations.

GET
/extra/v1/definition/datamap
List datamap definitions
→ 200
GET
/extra/v1/definition/datamap/{datamapName}
Get datamap definition
1 param → 200404
PUT
/extra/v1/definition/datamap/{datamapName}
Create or update datamap definition
1 param body → 200400404
DELETE
/extra/v1/definition/datamap/{datamapName}
Delete datamap definition
1 param → 200400404
HEAD
/extra/v1/definition/datamap/{datamapName}
Check datamap definition exists
1 param → 200404
GET
/extra/v1/definition/datamap/{datamapName}/schema
Get datamap JSON schema
1 param → 200404
Datamap Query 7

Run datamap queries and manage datamap data. Supports ad-hoc XML queries and CRUD via JSON for Cadasto.

POST
/extra/v1/datamap
Ad-hoc datamap query (XML body)
4 params body → 200400404
GET
/extra/v1/datamap/{datamapName}
Query datamap data (list)
5 params → 200400404
POST
/extra/v1/datamap/{datamapName}
Create datamap data
2 params body → 201400404
GET
/extra/v1/datamap/{datamapName}/{uidBasedId}
Get datamap data (by UID)
3 params → 200400404
PUT
/extra/v1/datamap/{datamapName}/{uidBasedId}
Update datamap data (by UID)
3 params body → 200400404
DELETE
/extra/v1/datamap/{datamapName}/{uidBasedId}
Delete datamap data (by UID)
3 params → 200400404
HEAD
/extra/v1/datamap/{datamapName}/{uidBasedId}
Check datamap data exists (by UID)
3 params → 200404
Terminology 1

Terminology helpers, such as retrieving FHIR ValueSet URLs.

GET
/extra/v1/terminology/code24
Get FHIR ValueSet URL
1 param → 200302400501
Episode 7

CRUD on episodes within an EHR and status changes (activate/deactivate). Episodes group medical data around a clinical problem or episode of care across time and encounters.

GET
/extra/v1/ehr/{ehrUid}/episode
List episodes
1 param → 200
POST
/extra/v1/ehr/{ehrUid}/episode
Create episode
1 param body → 201400404
GET
/extra/v1/ehr/{ehrUid}/episode/{uid}
Get episode
2 params → 200404
PUT
/extra/v1/ehr/{ehrUid}/episode/{uid}
Update episode
2 params body → 200400404
DELETE
/extra/v1/ehr/{ehrUid}/episode/{uid}
Delete episode
2 params → 200404
PUT
/extra/v1/ehr/{ehrUid}/episode/{uid}/activate
Activate episode
2 params → 200404
PUT
/extra/v1/ehr/{ehrUid}/episode/{uid}/deactivate
Deactivate episode
2 params → 200404
Admin 1

Admin-only actions, such as permanently deleting (destroy) episodes.

PUT
/extra/v1/admin/ehr/{ehrUid}/episode/{uid}/destroy
Destroy episode (admin)
2 params → 200404

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

cadasto-extra-api-openapi.json Raw ↑
Where this information came from

This is an independent, third-party profile of Cadasto Additional 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.