Update Player Email

This method updates a player’s email address.

The new email address is placed in a pending status until the player verifies it. The system sends a verification email that contains a verificaton link to the player’s new and old email addresses. use gateway.[msdomain]

Request (POST)

`/gateway/player-personal-details/player/details/emailUpdate/{version}/{brand_id}`

{
  "email": "aaa@aaa.com",
  "comment": "test"
}

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.
x-auth-token	header	string	true	Player login session.
eMail	body	string	true	Player new email.
comment	body	string	false	Comment to insert during update, if not set, default is: player request.

Response

Status 204 (No content)

Status 400

{
  "errMsg": "invalid input - invalid brand id"
}

Status 401

{
  "errMsg": "invalid input - invalid token"
}

Status 404

{
  "errMsg": "Player Personal Email not found"
}

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
email	email_required	An email address is required.
email	email_syntax_error	The email syntax is wrong. Format is aaa@bbb.ccc.
email	email_fraud	The mail domain will be checked against a fraud list (test players qqtst_ will not be checked).
email	email_already_exists	Email already exists.
email	email_long	Email to long.
email	invalid_email	Email entered is invalid.

{
  "result": [
    {
      "field": "email",
      "errorCode": "invalid_email"
    }
  ]
}

Status 500

{
  "result": "internal server error"
}