Registration Step Two

This method completes the user registration process and makes the player’s account permanent.use gateway.[msdomain]

Request (POST)

/gateway/reg-step-two/{version}/{brand_id}

{
  "auth_token": "9deda661-7e8d",
  "firstName": "Firstname",
  "lastName": "Lastname",
  "birthDate": "01/01/1990",
  "gender": "M",
  "language": "en",
  "country": "HU",
  "city": "City",
  "address": "st. Somestreet, 10",
  "zipCode": "12345",
  "mobileNumber": "39-34535345",
  "uuid": "102d7d3834f4694ef00662"
}

Parameters:

Name In Type Required Description
version path string true The API version to use.
brand_id path int true The ID of the casino. If a brand_id is not provided, all message formats will be fetched from default storage.
auth_token body string true Token received from step one result OR token received during login with incomplete registration status.
firstName body string true Player first name.
lastName body string true Player last name.
birthdate body boolean true Player date of birth, should be in format of: DD/MM/YYYY.
language body boolean true Language to use on site.
country body boolean true Player country.
city body string true Player city.
address body string true Player address.
zipCode body string true Player address zip postal code.
mobileNumber body string true Player mobile number, should contain country code prefix + number (XX-YYYYYY).
uuid body string true TMX validation param.

Response

Status 200 The response to a successful.

{
  "message": "",
  "result": "OK",
  "auth_token": "null",
  "authToken": "null"
}

Status 400

{
  "message": "malformed_request",
  "result": "malformed_request",
  "auth_token": "null",
  "authToken": "null"
}

Status 401.

{
  "message": "",
  "result": "malformed_token",
  "auth_token": "null",
  "authToken": "null"
}

Status 400.

{
  "result": "general_error"
}

If you receive a 422 error code for an Unprocessable Entity error, the client should not use the Message Format method to send a request to the server, but use its internal logic to present the message for one or more fields that didn’t pass the validation.

When a 422 validation error occurs, the response returns an array of one or more error codes detailing the fields that have validation errors. Multiple error messages are issued in the same validation form. The site should handle these validation errors and present a validation message to the player.

This will not call the message format.

The following table explains validation code behavior:

Field Error Code Description
firstName first_name_invalid Invalid characters in first name. This field accepts only letters and numbers.
lastName last_name_invalid Invalid characters in last name. This field accepts only letters and numbers.
birthDate birth_date_required Birth date empty.
birthDate birth_date_invalid Birth date is not valid (31.2).
birthDate birth_date_over18 Player must be over 18.
gender gender_required Gender field empty.
language language_required Invalid language.
country country_required Country field empty.
address address_invalid Address format not valid.
mobileNumber mobile_required User didn’t provide a mobile number.
mobileNumber mobile_invalid Mobile number contains invalid characters. 
{
  "message": "",
  "result": [
    {
      "field": "firstName",
      "errorCode": "first_name_invalid",
      "result": "",
      "status": "422"
    }
  ],
  "auth_token": "null",
  "authToken": "null"
}

Status 500

{
  "result": "internal server error"
}

Response Parameters:

Name Description
auth_token UUID to be used when sending registration step two requst.
player_id unique id for the generated player.