Once your users link a sportsbook account, they'll need the ability to manually refresh, pause, remove and see the status of accounts they've linked.
To integrate the linked account management functionality into your existing user experience, you can use the SharpSports API to create the necessary functionality. Below is a guide to some of the suggested features.
Sometimes users want to pause syncing for a particular account. You can give users the ability to pause an account with the ⏸️ pause call.
You can remove an account by changing
access to false on a specific bettorAccount using the ❌ remove access endpoint. When
bettorAccount.access=false, you will no longer be able to refresh the account or get any associated information. When a user links the account again, the account will change to
access = true and you will have access to refreshes and account data again.
A bettorAccount can be in one of three verified states:
unverifiable. Everytime a refresh is run, the bettorAccount verified state might update.
These states are represented by the following fields:
bettorAccount.verified = true/false
bettorAccount.isUnverifiable = true/false
Use the 🔎 bettorAccount detail endpoint to check these values.
You can use this information, along with
bettorAccount.latestRefreshResponse.detail to prompt the owner of the account to fix the issue.
An individual bettorAccount can be verified, unverified or unverifiable. For unverified and unverifiable accounts, you'll need to provide the user a path to reverifying their account.
curl -X POST -H "Authorization: Token <public_API_key>" https://api.sharpsports.io/v1/bettorAccounts/BACT_RHcNmovNT1pX5RZjrjwbQ/refresh?reverify=true
bettorAccount.verified = false
An account becomes unverified when a refresh is unsuccessful. This could be the result of a change in password, an error on the sportsbook site, or a prompt from the sportsbook to accept new terms of services or other actions. We will attempt to reverify unverified accounts periodically, but the user can trigger a reverification themselves with the 🔄 refresh bettorAccount with the
reverify=true query param . These requests are treated the same as normal refresh requests, except they will attempt to connect to the sportsbook even if the account is unverified (but not unverifiable).
bettorAccount.isUnverifiable = true
Multiple reverification attempts will result in the bettorAccount becoming unverifiable. Unverifiable accounts can only be reverified by the user relinking their account in the UI. For these users, you'll need to direct the users to the UI using the 🔗 Linking Accounts path.
Updated 2 days ago