Skip to content

/verify_email_change

/me/verify_email_change

Target audience: Developers

1
Release version: 4.1.4.x

Introduction

This endpoint lets the user complete the e-mail change process by supplying the confirmation code received in the initial request. This is to verify the user is who she or he says.

URI

Environment URI
Stage https://payway-api.stage.adeprimo.se/external/api/v1/me/verify_email_change
Production https://backend.worldoftulo.com/external/api/v1/me/verify_email_change

Required scope

1
/external/me/w

Parameters

Field Required Type Description
confirmation_code Required String The confirmation code to verify the user.
Size range: 36

Curl Example

1
2
3
4
5
6
7
8
curl --request PUT \
--url https://payway-api.stage.adeprimo.se/external/api/v1/me/request_email_change \
--header 'accept: application/json' \
--header 'authorization: Bearer token' \
--header 'content-type: application/json' \
--data '{
         "confirmation_code": "89bd6d78-4ace-4a0c-a517-afbbbc97c659"            
       }'

Response

Example Response: Successfully requested e-mail change

1
2
HTTP 200
{}

HTTP 400 Bad Request

Name Type Description
invalid_parameter Object Validation error on any of the fields in the posted json
json_parser_error Object The request body could not be parsed as valid json
invalid_content_type_error Object The requests Content-Type header isn't set to application/json
unknown_parameter Object One or more of the fields in the posted json was not recognized

HTTP 404 Not Found

Name Type Description
not_found Object The account or product could not be found

HTTP 409 Conflict

Name Type Description
invalid_confirmation_code Object The confirmation code does not match that of the first request

HTTP 500 Internal Server Error

Name Type Description
internal_server_error Object Something unexpected happened server side