...
The mobile number must be unique. To ensure this, the mobile number is sanitised and saved with its country-code prefix (45 in this example). If the mobile number is invalid or not unique, a 403400 response will be returned - see 1001: Create account for ApiStatusSubCode values.
...
200.1 | A verification SMS has been sent |
200.2 | The daily verification limit of 5 SMS verifications has been reached for this user. No SMS has been sent! This should be communicated to the user, so they know they need to wait until the next day before trying again. |
200.3 | The minimum time of 2 minutes has not passed since the last verification was sent to this number. No SMS has been sent! This should be communicated to the user, so they know they need to wait before trying again. |
After verification
The default API behaviour is to prevent verified mobile numbers from being changed. In this case, mobile fields sent to endpoint 1003: Update account data will simply be ignored.
...
The successful update returns status code 200. If a mobile number field was included in the update, and the new number is different to the existing number, and updating verified mobile numbers mobile numbers is enabled for the contract, then an ApiStatusSubCode of 200.1 or , 200.2 or 200.3 will be included in the response, as described above.
...