@take2identity/verosint 0.2.63 → 0.2.65

package/README.md

@@ -251,16 +251,24 @@ verosint evaluate rules-batch ip:0 email:1 phone:2 \
 
 You can submit events to the SignalPrint endpoint using the
 `signalprint send-events` subcommand. This subcommand works like the
-batch commands for rules. An event timestamp, IP address, and
-user agent is required for each event. You can optionally add an
-accountId, email, type, and/or phone with each event.
+batch commands for rules. An IP address, a user agent, and an event
+type are required for each event. You can optionally submit an
+event timestamp, an account identifier, an email address, and
+a phone number as well.
 
 The timestamp is expected to be in the
 [RFC3339](https://www.rfc-editor.org/rfc/rfc3339) format. For example:
 `2019-01-22T03:56:17+03:30`.
 
-The type can be one of:
-LOGIN_SUCCESS, LOGIN_FAILED, MFA_SUCCESS, MFA_FAILED, or VERIFICATION_SUCCESS
+The type must be one of:
+
+* `LOGIN_SUCCESS`
+* `LOGIN_FAILED`
+* `MFA_SUCCESS`
+* `MFA_FAILED`
+* `SIGNUP_SUCCESS`
+* `SIGNUP_FAILED`
+* `VERIFICATION_SUCCESS`
 
 ##### Examples for Signal Print
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@take2identity/verosint",
-  "version": "0.2.63",
+  "version": "0.2.65",
   "description": "Official CLI to interact with Verosint API",
   "main": "index.js",
   "scripts": {