anchor.diff:                  "message": "Password reset email has been sent"
               }
   
  -# Group Device Management Endpoints
  +# Group Device Endpoints
  +## Overview
  +SnapBundle may be used to capture metadata about devices in order to make the association that _this user used this device_. The 
  +`identification` field is the most important field in this data type, as it represents the unique identifier of the device. On a 
  +laptop, this could be the computer's network MAC address, or serial number printed on an asset tag affixed to the computer, or 
  +on a cell phone it could be the manufacturer's IMEI string or perhaps the phone number.
  +
  +> SnapBundle makes no inferences from the device identification. Theoretically, an account with 100 devices could simply sequence the identification of each device, i.e. 1, 2, 3, etc.
  +
  +## Device Fields
  +Field | Data Type | Required | Can Update | Serialization Level | Default Value
  +------------ | ------------- | ------------ | ------------ | ------------ | ------------
  +urn | String  | true | false | Minimum | Generated
  +account | IAccount  | true | false | Full | Generated
  +lastModifiedTimestamp | long   | true | false | Standard | Generated
  +moniker | String  | false | true | Standard | null
  +name | String  | true | true | Minimum | 
  +description | String  | false | true | Standard | 
  +activeFlag | Boolean  | true | true | Standard  | true
  +identification | String | true | false | Minimum |
  +type | String | true | true | Minimum |  
  +
  +### Field Notes
  +- The `identification` key MUST be treated as a unique value within your Account's Device set. Multiple devices with identical values is explicitly _not_ supported.
  +- The `type` field is available to create an ontology or high level categories that can be used to group related devices. The platform makes no inferences about this case-sensitive field.
   
   ## Device Definitions [/devices]
   ### Create a new device associated with an arbitrary identification value [PUT]
  
positive.code: 
              SnapBundle-Event : DeviceUpdated    
  
  ## Lookup Specific Device by URN [/devices/{urn}{?view}]
  ### Lookup a specific device by its system-assigned URN key [GET]
  
  
negative.code: - `activeFlag` is optional and may be omitted (defaults to **true**)
  - `moniker` is optional and may be omitted (defaults to **null**)
  
  #### Idempotent Behavior
  This endpoint is idempotent and will respond with an appropriate HTTP status code to indicate the actual result 
  
  - **201 SUCCESS_CREATED** if the record is new
  - **200 SUCCESS_OK** if a Device with the given `identification` already existed in the database, in which case **no data is merged; existing record is left as-is**
  
  + Request (application/json)
  
      + Headers
  