User

Both users participating in an insurance must be created (registered) beforehand. A returning user need not be registered again - it can be referenced using the Omocom ID (GUID) returned at registration, or it can be looked up using the find method.

Users are identified by an identity string defined by the platform, chad84 in the example below. When user is registered with Omocom, an Omocom ID is returned to be used for the remainder of the API communication.

Example of POST payload

{
    "MarketName": "SE",
    "UserId": "chad84",
    "FirstName": "Chad",
    "LastName": "Smith",
    "SocialSecurityNumber": {
        "SSN": "19840726-1234",
        "Country": "SE"
    },
    "PhoneNumber": "+46705554422",
    "StreetAddress": "Somestreet 6",
    "ZipCode": "12950",
    "CountryCode": "SE",
    "EmailAddress": "chad.smith.993@gmail.com",
    "Dob": "1984-07-26",
    "RatingPercent": 90,
    "Culture": "sv-SE",
    "ExternalProperties": [
        {
            "Type": "Text",
            "Name": "CustomerLevel",
            "Value": "Silver",
            "Description": "User tier of the customer"
        }]
}

The ExternalProperties information can be used as a general key/value pair to provide any information that do not have designated fields in the base DTO.

Notable fields

Property	Comment
Market	The scope of the user. The set of markets is defined at integration project start in collaboration with Omocom.
UserId	The login of the user on the platform. Normally scoped to the market, but in rare cases global to the platform.
Culture	The preferred language used in all communication with user.