Bet Recommendations API
Overview
The Bet Recommendations API provides real-time, AI-powered bet recommendations that power personalised player experiences across sportsbook platforms.
It supports:
-
Player-level personalisation for existing users
-
Site-level recommendations for new or low-activity users
These endpoints are typically consumed by your frontend, CMS, or CRM systems to drive onboarding, engagement, retention, and reactivation journeys.
For an overview of recommendation types and how bet recommendations work, see:
Bet Recommendations - How It Works
Before You Start
Before integrating the API, ensure:
-
You have an active Bet Recommendations subscription
-
Player session and transaction data is available and you have completed Data Transfer
-
Your backend or CMS can authenticate and call REST APIs
For an integration overview, see: Bet Recommendations - Integration
How It Works
Recommendations are generated using a combination of machine learning models that analyse player behaviour and preferences. These models continuously update based on new activity to ensure recommendations remain relevant and effective over time.
For a deeper explanation of the models and logic:
How it Works Guide
How to Use the API
API endpoints are categorised as follows:
Recommendations
-
Single bet recommendations -
/recommended_for_you_singles -
Accumulator recommendations -
/recommended_for_you_accas -
Bet builder recommendations -
/recommended_for_you_bet_builders -
In-play recommendations -
/in_play_recommendations
Preferences
-
Sports preferences -
/preferences_sports -
Tournament preferences -
/preferences_tournaments -
Market preferences -
/preferences_markets
Enhancements
-
Enhancements/Promotions -
/enhancements_promos
This approach gives you full control over placement and layout across your frontend.
The API handles player state automatically. Existing players receive personalised recommendations, while new or low-activity players are served optimised, site-level content without requiring separate logic.
For more detail on how recommendations are produced, see:
Bet Recommendations - How It Works
Integration Patterns
In practice, most operators integrate the API directly into their frontend to personalise key areas such as the homepage, event and competition pages. Recommendations are often used to power “next bet” suggestions or discovery-focused sections that encourage players to explore beyond their usual behaviour.
The same outputs can also be extended into CRM channels, including email, push notifications, and reactivation campaigns, allowing you to maintain consistent personalisation across both on-site and outbound experiences.
Where you already manage your own content collections, preferences endpoints can be used to personalise ordering rather than replacing content entirely. This is particularly useful for optimising existing content areas without changing their structure.
Fallbacks and Player States
Fallback behaviour is built into the API to ensure a consistent experience across all players.
If a player has limited or no activity, the system automatically returns recommendations optimised for conversion based on site-wide performance. In some cases, endpoints may return redirect responses, so your implementation should be able to handle these or fall back to site-level endpoints where appropriate.
More detail on player behaviour and fallback logic:
Bet Recommendations FAQ
