Successful Verification (no delay)

Username: gooduser

Password: Test1

This user completes all actions without errors and without delay
Has accounts on all sportsbooks and places bets on each sportsbook every day
You will receive an bettoraccount.verified and a refreshresponse.created webhook on login
If this is the first account you have linked with a give internalId, you will receive a bettor.created webhook on login

Successful Verification (delayed)

Username: realuser

Password: Test2

This user completes all actions without error with artificial delay of 10 seconds on login and 30 seconds on refresh bet history
Has accounts on all sportsbooks and places bets on each sportsbook every day
You will receive an 📱✅ bettorAccount.verified and a 🔄 refreshResponse.created webhook on login
If this is the first account you have linked with a give internalId, you will receive a 👤 ✅ bettor.created webhook on login.

Username: errorloginuser

Password: Test3

This user results in an error upon account verification. In production this could be caused a sportsbook site being down for maintenence
If this is a first time attempt at verification for a specific sportsbook we will delete the bettorAccount altogether
If this login is used on sportsbook with an existing bettorAccount we will maintain the same verified state
You will receive an 📱⚠️bettorAccount.unverified webhook when attempting to refresh a user with these credentials

Username: errorbetuser
Password: Test4

This user successfully logs in and verifies their account on every sportbook
When a bet refresh request is made for the verified bettorAccount the corresponding webhook contains a RefreshResponse object with a 500 error status due to a sportsbook's website being down or a SharpSports internal server error
You will receive an 📱⚠️bettorAccount.unverified webhook when attempting to refresh a user with these credentials

Username: changepassworduser

Password: Test5

This user successfully logs in and verifies their account on every sportbook
When a bet refresh request is made for the verified bettorAccount the corresponding webhook contains a RefreshResponse object with a 401 error status due to a changed password
You will receive an 📱⚠️bettorAccount.unverified webhook when attempting to refresh a user with these credentials

Username: 2FAuser

Password: Test6

Upon login with this user you will receive a UI prompt to enter an OTP
- The correct OTP for this user is 123456
If you input a bad OTP or no OTP on a refresh the corresponding webhook contains a RefreshResponse object with a 406 error status.
If you input a good OTP (123456) you will receive a 📱✅ bettorAccount.verified and a 🔄 refreshResponse.created webhook on login.
If this is the first account you have linked with a give internalId, you will receive a 👤 ✅ bettor.created webhook on login.

Any other username and password combo will result in the following:

If this is a first time attempt at verification we will delete the bettorAccount altogether
If this is a previously verified bettorAccount we will changed verified field to false