When you interact with the Sandbox environment, you’ll be able to use test users to simulate different behaviors. Simulate the possession checks using the client-side SDK.
The testing environment doesn’t send text messages or validate real customer information.
If an unexpected code is returned, reference the Error and Status Codes page.
sandbox test users can only be used with project credentials. Attempting to use these test users with different project credentials will result in an unauthorized access error.

​
Test Users List

​
Short-term test user

Use the following test users for initial testing with cURL or Postman. This user always passes the possession check but no Prove Key is generated.
Phone NumberFirst NameLast Name
2001004018BarbaraanneCanet
After initial short-term testing, use the remaining test users to test your implementation.

​
Unify Test Users

Follow the Testing Steps for expected behavior per step.
Phone NumberFirst NameLast Name
2001004014LorantNerger
2001004017JesseMashro

​
Testing Steps

Now that you’ve done client-side, server-side, and CX implementation, test using the test users.
Follow the steps below to test the Prove Unify flow with Lorant Nerger on desktop. This user will pass the entire Unify flow using Prove’s possession and return success=true in the /unify-status response.
1

Prompt Customer

Start the onboarding flow on the initial screen and enter the phone number for Lorant Nerger.
2

Initiate Start Request

Your front end will send the phone number, possession type, and final target URL to the back end. Your back end will then send the phone number to the /unify endpoint. The response will provide an auth token, correlation ID, and success=pending because possession still needs to be performed.
3

Send Auth Token to the Front End

Your back end will send the authToken to the front end. The front end will run Instant Link handling. You will see the following page.
4

Verify Mobile Number

Once the front end finishes the possession check, the back end calls the /unify-status endpoint with the correlation ID to validate the phone number. The response provides:
  • correlationId that is tied to this flow.
  • success=true
  • phoneNumber that was initially passed.
You have a successful flow but no Prove key is placed as the Prove key only applies to mobile devices. Send the user on through your authenticated flow.
If you receive 400 or 500 response errors when running these test scenarios, refer to the Error and Status Codes page. If you still have issues, send your correlationId from a failing request. Use either the Support button in the Portal or contact your account representative.
Production AccessFor Production access, contact your sales representative.