Register SMS Number

Used for manual verification of a user

The backoffice user initiates the request to send the OTP to the user's sms

The user then reads back the OTP which the backoffice user enters in the verifactionCode property for requests that require it

post/v2/users/registration/sms

Request body

smsNumberstring required

The phone number of a device that the user can receive sms messages on

Example request

{
  "smsNumber": "11235555555"
}

Response

request completed okay

Changes

Changed in 5 of the 50 revisions of this API.10419

Sep 25, 2020dd71433847a6318See the full diff
- ▲
  the / response's property type changed from no type to object for status
  response-property-type-changed
- ▲
  the / response's property type changed from no type to object for status
  response-property-type-changed
- ▲
  the / response's property type changed from no type to object for status
  response-property-type-changed
- ○
  added the optional property // to the response with the status
  response-optional-property-added
- ○
  added the optional property // to the response with the status
  response-optional-property-added
- ○
  added the optional property // to the response with the status
  response-optional-property-added
- ○
  added the optional property // to the response with the status
  response-optional-property-added
- ○
  added the optional property // to the response with the status
  response-optional-property-added
- ○
  added the optional property // to the response with the status
  response-optional-property-added
- ○
  added the optional property // to the response with the status
  response-optional-property-added
- ○
  added the optional property // to the response with the status
  response-optional-property-added
- ○
  added the optional property // to the response with the status
  response-optional-property-added
- ○
  added the optional property to the response with the status
  response-optional-property-added
- ○
  added the optional property to the response with the status
  response-optional-property-added
- ○
  added the optional property to the response with the status
  response-optional-property-added
- ○
  response property errors/items/locationType deprecated
  response-property-deprecated
- ○
  response property errors/items/locationType deprecated
  response-property-deprecated
- ○
  response property errors/items/locationType deprecated
  response-property-deprecated
- ○
  response property errors/items/reasonCode deprecated
  response-property-deprecated
- ○
  response property errors/items/reasonCode deprecated
  response-property-deprecated
- ○
  response property errors/items/reasonCode deprecated
  response-property-deprecated
This revision also has 9 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
Aug 13, 202075bb7af5ae631See the full diff
- ●
  changed the pattern of the request property from ^\+?[1-9]\d{1,14}$ to ^\+[1-9]\d{1,14}$
  request-property-pattern-changed
Jan 28, 20201b2abf26b5d663See the full diff
- ▲
  the response's body type changed from object to no type for status
  response-body-type-changed
- ▲
  the response's body type changed from object to no type for status
  response-body-type-changed
- ▲
  the response's body type changed from object to no type for status
  response-body-type-changed
- ▲
  the / response's property type changed from object to no type for status
  response-property-type-changed
- ▲
  the / response's property type changed from object to no type for status
  response-property-type-changed
- ▲
  the / response's property type changed from object to no type for status
  response-property-type-changed
- ●
  added the new requestParam enum value to the // response property for the response status
  response-property-enum-value-added
- ●
  added the new requestParam enum value to the // response property for the response status
  response-property-enum-value-added
- ●
  added the new requestParam enum value to the // response property for the response status
  response-property-enum-value-added
This revision also has 13 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
Dec 11, 2019a0b19fa311c01See the full diff
- ○
  endpoint added
  endpoint-added
This revision also has 6 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
Jul 15, 2019ced8e167a97c1See the full diff
- ▲
  api path removed without deprecation
  api-path-removed-without-deprecation
This revision also has 257 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

Full history