DMS service for enaio®
Apart from enaio® appconnector (OSRest), you can use the microservice: "DMS service" for enaio® (REST API). Although it offers less features at the moment, the technology stack is entirely new: it is a scalable, cloud-ready microservice, intended for "large systems." Our long-term goal is to extend this REST API step by step, so that it will have similar features to enaio® appconnector (status has been set to "deprecated" as of version 10.0).
As of version 11.0 we have a new USERS service for enaio® which is responsible for the topics of users, user groups and user-specific configurations.
The REST API of the DMS service is divided into two sections:
Core API
Native API (endpoints end with /native)
The Core API is almost identical to the "yuuvis-core” codebase and enables developers to write plug-ins for both technologies, while the Native API can only be used for enaio®. From time to time, endpoints in the Native API will be marked deprecated and move to the Core API if yuuvis® also has the need for a specific endpoint which already exists in the Native API. The deprecated endpoints will remain in the Native API for a couple of releases before they are removed permanently. All enaio® native endpoints in the API end with /native
.
- [POST] /{objectId}Team Flamingo (Apr 24, 2025)
- [PATCH] /{objectId}Team Flamingo (Apr 24, 2025)
- [POST] /objectsTeam Flamingo (Apr 24, 2025)
- [POST] /searchTechnische Redaktion (Apr 01, 2025)
- [DELETE] /fileTechnische Redaktion (Apr 01, 2025)
- [POST] /linksTechnische Redaktion (Apr 01, 2025)
- [POST] /restoreTechnische Redaktion (Apr 01, 2025)
- [DELETE] /trashTechnische Redaktion (Apr 01, 2025)
- [GET] /{objectId}Technische Redaktion (Apr 01, 2025)
- [GET] /nativeTechnische Redaktion (Apr 01, 2025)
- [GET] /schemaTechnische Redaktion (Apr 01, 2025)
- 1.5 Options for EndpointsTechnische Redaktion (Apr 01, 2025)
- 1.2 System FieldsTechnische Redaktion (Apr 01, 2025)
- 1.1 Date FormatTechnische Redaktion (Apr 01, 2025)
- DMS service for enaio®Technische Redaktion (Apr 01, 2025)
- [POST] /namesTechnische Redaktion (Apr 01, 2025)
- [POST] /zipTechnische Redaktion (Apr 01, 2025)
- [POST] /pdfTechnische Redaktion (Apr 01, 2025)
- /contentsTechnische Redaktion (Apr 01, 2025)
- /nativeTechnische Redaktion (Apr 01, 2025)