# Person mobile numbers

## Create a mobile number for a person

 - [POST /v1/persons/{person_id}/mobile_number](https://docs.solarisgroup.com/api-reference/onboarding/persons/person-mobile-numbers/paths/~1v1~1persons~1%7Bperson_id%7D~1mobile_number/post.md): Registers a new mobile number for a person. Please note the following:  Each customer may only have one mobile number at a time. The customer cannot use their mobile number until they verify it using the POST Request authorization and POST Confirm endpoints. The API removes spaces, dashes, underscores, and forward slashes from the mobile number value. 

## Retrieve a person's mobile number

 - [GET /v1/persons/{person_id}/mobile_number](https://docs.solarisgroup.com/api-reference/onboarding/persons/person-mobile-numbers/paths/~1v1~1persons~1%7Bperson_id%7D~1mobile_number/get.md): Returns information about a person's registered mobile number. Returns a  error if no mobile number has been registered.

## Deletes a person's mobile number

 - [DELETE /v1/persons/{person_id}/mobile_number](https://docs.solarisgroup.com/api-reference/onboarding/persons/person-mobile-numbers/paths/~1v1~1persons~1%7Bperson_id%7D~1mobile_number/delete.md): Removes a customer's registered mobile number.  If the request is successful and the mobile number has already been confirmed, then the API will trigger the  process. The person who owns the mobile number will receive an SMS informing them that the number was deleted. If the request is successful but the mobile number has  been verified, then the mobile number will be deleted without a change request.

## Request authorization for a person's mobile number

 - [POST /v1/persons/{person_id}/mobile_number/authorize](https://docs.solarisgroup.com/api-reference/onboarding/persons/person-mobile-numbers/paths/~1v1~1persons~1%7Bperson_id%7D~1mobile_number~1authorize/post.md): Requests an SMS OTP challenge to authorize a person's mobile number for use with 2FA. The API will return a 404 error if no mobile number was previously created for the customer or if the number in the request does not match the customer's existing mobile number. If the number has already been confirmed, then the API will return the confirmed mobile number.

## Confirm a customer's mobile number

 - [POST /v1/persons/{person_id}/mobile_number/confirm](https://docs.solarisgroup.com/api-reference/onboarding/persons/person-mobile-numbers/paths/~1v1~1persons~1%7Bperson_id%7D~1mobile_number~1confirm/post.md): Submits the SMS OTP that the customer received on their mobile number to confirm it and authorize it for use with 2FA. Please note the following:   The API will respond with a  error if the token has expired or if an invalid token is provided. The API will respond with a  error if you exceed the limit of 60 SMS messages per hour for a given mobile number. 

## Reauthorize mobile number

 - [POST /v1/persons/{person_id}/mobile_number/reauthorize](https://docs.solarisgroup.com/api-reference/onboarding/persons/person-mobile-numbers/paths/~1v1~1persons~1%7Bperson_id%7D~1mobile_number~1reauthorize/post.md): Request a new authorization challenge for a person's mobile number to use with 2FA.