Introduction

this document describes the rest interface to engine4, the data structure and how interface applications should be built via this rest / json api it is possible to read and write data in or from engine4 authentication is performed via oauth 2 0 for all accesses, the permissions assigned in engine4 are taken into account according to the user's security role an example client can be found further down in this documentation under best practises docid\ dmxiyqv2vnxw0ymj oc0u general notes the engine4 api runs on different saas or onpremise environments the examples in this document all point to the test environment (saas) the url for the test environment (saas) is https //test engine4 io https //test engine4 io/externalapidocs/ the url for the production development environment (saas) is https //prodapi engine4 io https //prod engine4 io/externalapidocs/ for onpremise installations, use the externally accessible url! to use the api, you need a clientid, a valid account, and information about the relationships of entities and their references to each other you can obtain this information from your responsible consultant requirenments clientid the clientid is an additional factor in authentication clientids can be defined via "identityserverkonfiguration" through your consultant of mobile function it is recommended to create one clientid per customer/client the clientid is considered as an additional parameter to username and password an assignment of the clientid to user or client is not necessary account an account (username and password) is required, which has the necessary rights/roles in the respective system to read or write (or depending on the use case) limitations it is possible/required to define limitations for api requests for external apis but also the usage of e4 itself (via the normal user interface) see "apirequestlog/ limitationconfig" (mf) license its necessary that you obtain a license for rest api usage on a regular basis your sales manager can support you for this