The Betfair API offers three login flows for developers, depending on the use case for your application.
Please see the documentation for full technical information regarding how to implement each login method.
Login Type | Use Case | Method | Pros | Cons | Recommendation |
---|---|---|---|---|---|
Non-interactive Login | Applications running autonomously (e.g bots). | Non-interactive endpoint with SSL certificate. | Secure for automation. Recommended for bots. | Requires certificate setup. | ✅ Use if your app runs without user interaction (e.g., bots, scheduled tasks). |
Interactive Login – API Login | Applications needing a simple integration with minimal development time. | API login endpoint (username + password, or username + password + 2FA if enabled). | Easiest to implement. Good for most apps. | Less flexible for handling edge cases compared to the embedded login page. | ✅ Use if you want quick setup and don’t need T&Cs or jurisdiction workflows. |
Interactive Login – Desktop App | Applications used interactively by a wide range of users. | Embedded Betfair login pages. | Handles workflows like T&Cs updates and jurisdiction checks. More flexible for 3rd party apps. | Requires embedding Betfair’s login page. More development effort compared to API login. | ✅ Use if your app is for many users and must handle extra workflows securely. |
Comments
0 comments
Article is closed for comments.