introduces a first (beta) version of the Unomi GraphQL API. 1.1.1. INTRODUCING PROFILES ALIASES Profiles may now have alias IDs, which is a new way to reference profiles using multiple IDs. The Unomi ID still aliases can reference a single Unomi profile. This enables more flexible integrations with external systems, as well as provide more flexible and reliable merging mechanisms. A new REST API makes it easy Scopes can be easily created via the corresponding REST API ( cxs/scopes ) For example, an "apache" scope can be created using the following API call. 1.1.3. JSON SCHEMAS Apache Unomi 2 introduces support

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 2.5.7. REST API Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 4.1.1. Import API. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 4.2.1. Export API. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 2.6.4. REST API Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . "properties": } Some types can be dynamically defined at runtime by calling to the REST API while other extensions are done via Unomi plugins. Part of extending Unomi, therefore, is a matter and should depend on the Unomi API maven artifact: Apache Unomi 1.1.x - Documentation - 4 org.apache.unomi unomi-api ...