Bet Recommendations - Integration
Accessing and integrating with Future Anthem's Bet Recommendations
Overview
Future Anthem’s Bet Recommendations API provides sportsbook operators with a flexible, scalable solution for delivering personalised bet recommendations to players in real-time. The product leverages machine learning models to analyse historical player activity, betting markets and upcoming events to generate relevant, context-aware recommendations.
API Integration
API integration is the preferred and most common method for delivering personalised bet recommendations efficiently.
The Bet Recommendations API enables direct, real-time access to AI-driven bet recommendations for each player. Recommendations are generated dynamically based on the players recent activity and available upcoming sports events.
Endpoint Overview
- Request Structure: https://mlasserve-sportbets.wh.future-anthem-lz-pr.com/recommended_for_you_singles
- Method: GET
- Authentication: x-api-key header
A typical request example:
curl -X 'GET' \
'https://mlasserve-sportbets.future-anthem-lz-pr.com/recommended_for_you_singles?user_id=player123' \
-H 'accept: application/json' \
-H 'x-api-key: AbCdEfGhIJkLmNoPqRsTuVwXyZ123456=='
This retrieves the recommended for you single bet recommendations for the specified player.
Request Parameters
| Parameter | Type | Location | Required | Description | Example |
| user_id | String | Query | ✅ | Unique identifier for the player | player123 |
| sport | String | Query | ❌ | Filter by sport | football |
| event_id | String | Query | ❌ | Filter by specific event ID | 123456789 |
| x-api-key | String | Header | ✅ | API key used for authentication | AbCdEfGhIJkLmNoPqRsTuVwXyZ123456== |
Response Structure
Each API response contains a player object (metadata about the player) and at present singles array (the recommended single bets).
Player Object
| Field | Type | Description | Example |
| player_id | String | Unique identifier for the player | player123 |
| country | String | Players country | UK |
| site | String | Operator site or brand | sportssite.com |
| control_group | String | Indicates if the player is in the control or target group | False |
Recommendation for Single Bets Object
| Field | Type | Description | Example |
| id | String | Unique identifier for the recommendation | single_foot_001 |
| sport | String | Sport type | football |
| recommendation_type | String | Type of recommendation | single |
| leg | Array | List of legs making up the recommendation | [...] |
| leg.sport_key_id | String | Sport ID | 1 |
| leg.league_key_id | String | League or competition ID | 101 |
| leg.event_id | String | Event ID | 123456789 |
| leg.market_key_id | String | Market ID | 998877665 |
| leg.outcome_key_id | String | Selection ID | 009008007 |
| leg.event_time | Integer | Event start time in UNIX epoch seconds | 1762632000 |
Example Response
Note: For demo purposes, the below response ID's have been replaced with readable values and the recommendations have been limited to 3.
{
"player": {
"player_id": "player123",
"country": "UK",
"site": "sportssite.com",
"control_group": "False"
},
"singles": [
{
"id": "single_foot_001",
"sport": "football",
"recommendation_type": "single",
"leg": [
{
"sport_key_id": "Football",
"league_key_id": "English Premier League ",
"event_id": "Arsenal vs Everton",
"market_key_id": "First Goalscorer",
"outcome_key_id": "Eberechi Eze",
"event_time": 1762632000
}
]
},
{
"id": "single_foot_002",
"sport": "football",
"recommendation_type": "single",
"leg": [
{
"sport_key_id": "Football",
"league_key_id": "English Premier League",
"event_id": "Tottenham vs Newcastle",
"market_key_id": "Both Teams To Score",
"outcome_key_id": "Yes",
"event_time": 1762635600
}
]
},
{
"id": "single_foot_003",
"sport": "football",
"recommendation_type": "single",
"leg": [
{
"sport_key_id": "Football",
"league_key_id": "Spanish La Liga",
"event_id": "Villareal vs Barcelona",
"market_key_id": "Correct Score",
"outcome_key_id": "2-0 Barcelona",
"event_time": 1762639200
}
]
}
]
}
Other Integration Methods
In addition to direct API integration, bet recommendations can also be delivered using alternative methods to fit operational or technical constraints:
- File Export: Personalised bet recommendations can be exported as CSV files, containing player IDs and recommended event, market and outcome IDs
- SFTP Delivery: Exports can be securely transferred to operator servers via SFTP for ingestion into downstream systems
- CRM or CMS Integration: Recommendations can be pushed directly into CRM or front-end content systems to support personalised messaging, promotions and in-app recommendations
Data Requirements
To ensure optimal recommendation accuracy and freshness, the model relies on recent player betting activity. Operators should provide regular updates of player bet transactions and outcomes.
For detailed instructions on how to integrate your data with Amplifier AI, refer to our data integration guide.