πͺ Handling Webhooks
Best Practices
Bettor Events
- π€ β
bettor.created
- Be sure to store the
bettorId
alongside theinternalId
in your database.
- Be sure to store the
BettorAccount Events
- π±β
bettorAccount.verified
- If you are creating custom Bettor Account Management functionality, use this endpoint to keep the account status up to date.
- π±β οΈbettorAccount.unverified
- Use this endpoint to notify users when there is an issue with their account.
- π± β bettorAccount.inaccessible
- Use this endpoint to update any internal representation of a users' status and permissions.
RefreshResponse Events
-
-
Be sure to handle the various
status
codes on the π Refresh Response objects.
It's recommended to process the betSlips in the refreshResponse after responding with a 200 to confirm receipt of the webhook. The webhook connection will timeout if the response takes too long. -
Updated 10 days ago