Unomi 1.x: curl --location --request POST 'http://localhost:8181/cxs/scopes' \ -u 'karaf:karaf' \ --header 'Content-Type: application/json' \ --data-raw '{ "itemId": "apache", "itemType": "scope" }' Is replaced curl --location --request POST 'http://localhost:8181/cxs/scopes' \ --header 'Authorization: Basic a2FyYWY6a2FyYWY=' \ --header 'Content-Type: application/json' \ --data-raw '{ "itemId": "unomi-tracker-test" --location --request POST 'http://localhost:8181/cxs/events/search' \ --header 'Authorization: Basic a2FyYWY6a2FyYWY=' \ --header 'Content-Type: application/json' \ --data-raw '{ "sortby" : "timeStamp:desc"

solution because as this is a protected event it will require sending the Unomi key as a request header, and as Unomi only supports a single key for the moment it could be problematic if the key is intercepted Unomi 1.x - Documentation - 24 curl -X POST -k -u karaf:karaf https://localhost:9443/cxs/rules \ --header "Content-Type: application/json" \ -d @- << EOF { "itemId": "form-mapping-example", "itemType": from the specified IP address, and if the secret-key is passed in the X-Unomi-Peer HTTP request header. The "env:" part means that it will attempt to read an environment variable by that name, and if