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 ITEM TAG API

Management of [ITEM_TAG](https://specifications.openehr.org/releases/RM/latest/common.html#_item_tag_class) resources attached to demographic versioned objects (PERSON, AGENT, GROUP, ORGANISATION, ROLE). See also the [ITEM_TAG guide](/docs/guides/item-tag).

Cadasto ITEM TAG API is one of 24 APIs that Cadasto publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include ITEM_TAG. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and authentication docs.

This API exposes 23 operations across 16 paths, and defines 20 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 2 base URLs: https://{baseUrl}/v1, https://{baseUrl}/openehr/v1.

23 operations 16 paths 20 schemas 7 DELETE9 GET7 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://{mycompany}.api.prod.cadasto.io/openehr/v1
Resource Areas
1

Paths & Operations 23

Across 16 paths, the API surfaces 23 operations — 7 DELETE, 9 GET, 7 PUT. Each is listed below with its method, path, parameters, and response codes.

Item Tag 23

Management of ITEMTAG resources attached to demographic versioned objects (PERSON, AGENT, GROUP, ORGANISATION, ROLE). See also the ITEMTAG guide.

GET
/demographic/tags
Get demographic tags
demographic_tags_get 3 params → 200400
GET
/demographic/agent/{uid_based_id}/tags
Get AGENT tags
agent_tags_get 1 param → 200404
PUT
/demographic/agent/{uid_based_id}/tags
Update AGENT tags
agent_tags_update 2 params body → 200204400404
DELETE
/demographic/agent/{uid_based_id}/tags/{key}
Delete AGENT tag by key
agent_tags_delete 2 params → 204404
GET
/demographic/group/{uid_based_id}/tags
Get GROUP tags
group_tags_get 1 param → 200404
PUT
/demographic/group/{uid_based_id}/tags
Update GROUP tags
group_tags_update 2 params body → 200204400404
DELETE
/demographic/group/{uid_based_id}/tags/{key}
Delete GROUP tag by key
group_tags_delete 2 params → 204404
GET
/demographic/organisation/{uid_based_id}/tags
Get ORGANISATION tags
organisation_tags_get 1 param → 200404
PUT
/demographic/organisation/{uid_based_id}/tags
Update ORGANISATION tags
organisation_tags_update 2 params body → 200204400404
DELETE
/demographic/organisation/{uid_based_id}/tags/{key}
Delete ORGANISATION tag by key
organisation_tags_delete 2 params → 204404
GET
/demographic/person/{uid_based_id}/tags
Get PERSON tags
person_tags_get 1 param → 200404
PUT
/demographic/person/{uid_based_id}/tags
Update PERSON tags
person_tags_update 2 params body → 200204400404
DELETE
/demographic/person/{uid_based_id}/tags/{key}
Delete PERSON tag by key
person_tags_delete 2 params → 204404
GET
/demographic/role/{uid_based_id}/tags
Get ROLE tags
role_tags_get 1 param → 200404
PUT
/demographic/role/{uid_based_id}/tags
Update ROLE tags
role_tags_update 2 params body → 200204400404
DELETE
/demographic/role/{uid_based_id}/tags/{key}
Delete ROLE tag by key
role_tags_delete 2 params → 204404
GET
/ehr/{ehr_id}/tags
Get EHR tags
ehr_tags_get 4 params → 200400404
GET
/ehr/{ehr_id}/composition/{uid_based_id}/tags
Get COMPOSITION tags
composition_tags_get 2 params → 200404
PUT
/ehr/{ehr_id}/composition/{uid_based_id}/tags
Update COMPOSITION tags
composition_tags_update 3 params body → 200204400404
DELETE
/ehr/{ehr_id}/composition/{uid_based_id}/tags/{key}
Delete COMPOSITION tag by key
composition_tags_delete 3 params → 204404
GET
/ehr/{ehr_id}/ehr_status/{uid_based_id}/tags
Get EHRSTATUS tags
ehr_status_tags_get 2 params → 200404
PUT
/ehr/{ehr_id}/ehr_status/{uid_based_id}/tags
Update EHRSTATUS tags
ehr_status_tags_update 3 params body → 200204400404
DELETE
/ehr/{ehr_id}/ehr_status/{uid_based_id}/tags/{key}
Delete EHRSTATUS tag by key
ehr_status_tags_delete 3 params → 204404

Schemas 20

The contract defines 20 schemas that model the data the API accepts and returns. The most detailed are ItemTagOfAgent (5 properties), ItemTagOfEhrStatus (5 properties), ItemTagOfRole (5 properties), ItemTagOfGroup (5 properties). Each schema is shown below with its type and property counts.

ItemTagOfAgent
object
5 properties 3 required
UpdateItemTag
object
3 properties 1 required
ObjectRefOfObjectVersionId
object
3 properties 3 required
ItemTagOfPerson
object
5 properties 3 required
ItemTagOfOrganisation
object
5 properties 3 required
ItemTagOfGroup
object
5 properties 3 required
UMObjectVersionId
object
2 properties 2 required
ItemTagOfRole
object
5 properties 3 required
Error
object
2 properties 2 required
UpdateItemTag_2
object
3 properties 1 required
UMGenericId
object
3 properties 3 required
UMHierObjectId
object
2 properties 2 required
ItemTagOfEhrStatus
object
5 properties 3 required
UObjectId
UMTerminologyId
object
2 properties 2 required
UMArchetypeId
object
2 properties 2 required
UMObjectVersionId_2
object
2 properties 2 required
ObjectRef
object
3 properties 3 required
UMTemplateId
object
2 properties 2 required
ItemTagOfComposition
object
5 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

cadasto-item-tag-api-openapi.yml Raw ↑

Other APIs Cadasto publishes across the network.

openEHR Assistant MCP Server
Cadasto ADL1.4 API
Cadasto ADL2 API
Cadasto Admin API
Cadasto AGENT API
Cadasto COMPOSITION API
Cadasto CONTRIBUTION API
Cadasto Datamap Definition API
Cadasto Datamap Query API
Cadasto DIRECTORY API
Cadasto EHR API
Cadasto EHR STATUS API
Where this information came from

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