properties for URL parameters: The following event example in Apache Unomi 1.x: curl --location --request POST 'http://localhost:8181/cxs/scopes' \ -u 'karaf:karaf' \ --header 'Content-Type: application/json' unomiWebTracker.startTracker(); })(); JAVASCRIPT curl --location --request POST 'http://localhost:8181/cxs/scopes' \ --header 'Authorization: Basic a2FyYWY6a2FyYWY=' \ --header start the tracker unomiWebTracker.startTracker(); })(); JAVASCRIPT curl --location --request POST 'http://localhost:8181/cxs/events/search' \ --header 'Authorization: Basic a2FyYWY6a2FyYWY=' \

properties, as well as the profile’s segments and scores Apache Unomi 1.x - Documentation - 7 curl -X POST http://localhost:8181/context.json?sessionId=1234 \ -H "Content-Type: application/json" \ -d @- <<'EOF' profile. Let’s consider the following example of a rule: Apache Unomi 1.x - Documentation - 9 curl -X POST http://localhost:8181/cxs/rules \ --user karaf:karaf \ -H "Content-Type: application/json" \ -d @- could then simply send the contactInfoSubmitted event using a request similar to this one: curl -X POST http://localhost:8181/eventcollector \ -H "Content-Type: application/json" \ -d @- <<'EOF' { "sessionId"

xhr.open("POST", url, true); xhr.withCredentials = true; } else if (typeof XDomainRequest != "undefined") { xhr = new XDomainRequest(); xhr.open("POST", url); }