Introduction

All the data stored in the CoreOne Meta Directory can directly be accessed and modified by using our API V2. In earlier version (< 6.0), only a handful of operations where possible by using the V1 of the API. Those legacy endpoints will stay untouched, but new features will only be available in the newer version of the API. On the subsequent pages you will find all the details.

How-to article

Related article

...

Data Centric vs. Business Centric Endpoints

As described, the API-V2 exposes all data stored stored in the CoreOne Meta Directory. When performing mutations on that data, no business logic is executed. So even though you can add a new role to a core identity, no additional task such as the assignment task will be triggered. You will have to wait for the regular job intervall to start until your changes will be processed. In some cases this is fine and might be even desired.

However, if you would like to change data and also trigger the appropriate business logic, you should use the business centric endpoints described in the appropriate documentation.