Bet Builders
The event id to get a bet builder for. If not set then the top count recommended events
of the given user will be picked and bet builders for them will be generated.
sr:match:23150637How many bet builders to produce in total.
1Example: 1Optional upper limit to the amount of bet builders to generate per event. Since the number of bet builders to generate per event is dynamically calculated based on their confidence (so more bet builders are generated for highly recommended events), this parameter can be used to apply a limit, for example if one wants only one bet builder per event regardless of their personalization score. If not set, it will be ignored.
1The minimum event's starting datetime. If not explicitly set it defaults to now.
Considers events starting after the from timestamp plus the given minutes/hours/days.
If not set defaults to 0 minutes.
The value must be in range [-7d - 7d].
0Example: -3hPattern: ^[+-]?[0-9]+([.][0-9]+)?[smhd]?$Considers events starting till the from timestamp plus the given
minutes/hours/days. If not set defaults to one day (24 hours).
The value must be in range [-7d - 7d].
2dExample: 2dPattern: ^[+-]?[0-9]+([.][0-9]+)?[smhd]?$The bet builder length.
2Example: 2Optional filtering on the events and markets to consider. The event related filters are ignored
in case the event_id parameter is provided. It expects a string adhering
to the filtering format, as described in the filtering section, e.g. market_status:eq:OPEN.
If set to true, the odds of the bet builder will be calculated and included in the response. Only applicable if configured for your token.
falseIf set to true, ensures that player props and team-level markets
in each bet builder are aligned to the same team.
Team-neutral markets like totals (over/under) are always included.
Defaults to false, where no such check is performed.
falseIf set to true, ensures that any player-specific selection in each
bet builder is for the same player, while the remaining selections are
aligned to that player's team (when they are team-specific).
Team-neutral markets like totals (over/under) are always included.
Defaults to false, where no such check is performed.
falseIf set to true, returns bet builders that only include player
markets. Defaults to false.
falseThe user to get recommended bet builder for.
If true, calculates the bet builder's length dynamically based on user's preferences.
Note that if set to true then it ignores the length parameter. Defaults to false.
falseExample: trueThe columns to sort the results by. It expects a string adhering to
the ordering format, as described in the ordering section, e.g.
+league_confidence,-sport_confidence.
Optional selection of the object fields to retrieve. It expects a comma
separated list of strings, as described in the field selection section,
e.g. event_id,event_type.
["event_id","event_type","begin","country","country_id","league","league_id","sport","sport_id","participants","participant_ids","status","confidence","selection_id","bet_offer_id","market","market_id","market_type","market_type_id","uof_external_id","outcome","outcome_id","period","period_id","quote","quote_group","count","confidence"]Possible values: The operator to use for querying data. Notice that this is applied only if your account has access to multiple operators. In a different case the assigned operator to your account is used and the value of this field is ignored.
The bookmaker id to use for querying data. Notice that this is applied only
if your account has access to multiple operators. In a different case
the assigned operator to your account is used and the value of this
field is ignored. Note that this parameter is used together with the
sub_bookmaker_id parameter.
The sub-bookmaker id to use for querying data. Notice that this is applied only
if your account has access to multiple operators. In a different case
the assigned operator to your account is used and the value of this
field is ignored. Note that this parameter is used together with the
bookmaker_id parameter.
List of event types to consider when generating recommendations. One or more types can be provided. Available options are:
match: Standard matches to be considered.seasonal: Seasonal events to be considered.forced_events: Handpicked events to be considered regardless of their start_time.
match,forced_eventsPossible values: The location of the page where the request takes place.
inplay_widgetComma separated list of keywords. If given, this input will be used
as user demographics data for the recommendations, e.g country:gr,city:ath.
Custom client header, the value should be the name of the group the user belongs to
Authentication method to be used, supported values [vaix, iam]. Defaults to vaix
OK
API response
The status of the request
Bad Request
Unauthorized
Forbidden
Not Acceptable
Request Entity Too Large
Unprocessable Content
Too Early
Internal Server Error
GET /api/sports/bet_builders/recommended?user=text HTTP/1.1
Host: api.vaix.ai
Authorization: Bearer YOUR_SECRET_TOKEN
x-vaix-client-id: text
Accept: */*
{
"data": [
{
"begin": "2026-01-01T00:00:00.000Z",
"bet_builders": [
{
"odds": 1,
"selections": [
{
"bet_offer_id": "text",
"count": 1,
"market": "text",
"market_id": 1,
"market_type": "text",
"market_type_id": 1,
"outcome": "text",
"outcome_id": 1,
"period": "text",
"period_id": 1,
"quote": 1,
"quote_group": "text",
"selection_id": "text",
"side": "text",
"uof_external_id": "text"
}
]
}
],
"confidence": 1,
"country": "text",
"country_id": "text",
"event_id": "text",
"event_type": "text",
"league": "text",
"league_id": "text",
"participant_ids": [
"text"
],
"participants": [
"text"
],
"sport": "text",
"sport_id": "text",
"status": "text"
}
],
"status": "success"
}Comma separated list of selection ids that must all belong to the same event. Returned bet builders will contain all of these selections.
c495ac571a7e4ecf2014abd597d2c1aaHow many bet builders to return.
1Example: 5The user to get recommended bet builder for.
The importance of user market preferences when combined with the event weight (popular/trending markets of the event).
0.95The bet builder length.
2Example: 2Optional filtering on the markets to consider. It expects a string adhering
to the filtering format, as described in the filtering section, e.g. market_status:eq:OPEN.
The minimum confidence score for all selections to be considered.
Any confidence lower than this will be shifted to min_confidence.
0.05The power to apply to the confidence scores. This is used to re-balance the confidence scores of the selections. Lower power means stronger re-balancing, bringing the confidence scores closer to each other.
0.6If set to true, ensures that player props and team-level markets
in each bet builder are aligned to the same team.
Team-neutral markets like totals (over/under) are always included.
Defaults to false, where no such check is performed.
falseIf set to true, ensures that any player-specific selection in each
bet builder is for the same player, while the remaining selections are
aligned to that player's team (when they are team-specific).
Team-neutral markets like totals (over/under) are always included.
Defaults to false, where no such check is performed.
falseIf set to true, returns bet builders that only include player
markets. Defaults to false.
falseOptional selection of the object fields to retrieve. It expects a comma
separated list of strings, as described in the field selection section,
e.g. event_id,event_type.
["event_id","event_type","begin","country","country_id","league","league_id","sport","sport_id","participants","participant_ids","status","confidence","selection_id","bet_offer_id","market","market_id","market_type","market_type_id","uof_external_id","outcome","outcome_id","period","period_id","quote","quote_group","count","confidence"]Possible values: The operator to use for querying data. Notice that this is applied only if your account has access to multiple operators. In a different case the assigned operator to your account is used and the value of this field is ignored.
The bookmaker id to use for querying data. Notice that this is applied only
if your account has access to multiple operators. In a different case
the assigned operator to your account is used and the value of this
field is ignored. Note that this parameter is used together with the
sub_bookmaker_id parameter.
The sub-bookmaker id to use for querying data. Notice that this is applied only
if your account has access to multiple operators. In a different case
the assigned operator to your account is used and the value of this
field is ignored. Note that this parameter is used together with the
bookmaker_id parameter.
Custom client header, the value should be the name of the group the user belongs to
Authentication method to be used, supported values [vaix, iam]. Defaults to vaix
OK
API response
The status of the request
Bad Request
Unauthorized
Forbidden
Not Acceptable
Request Entity Too Large
Unprocessable Content
Too Early
Internal Server Error
GET /api/sports/bet_builders/extended?selection_ids=text&user=text HTTP/1.1
Host: api.vaix.ai
Authorization: Bearer YOUR_SECRET_TOKEN
x-vaix-client-id: text
Accept: */*
{
"data": [
{
"begin": "2026-01-01T00:00:00.000Z",
"bet_builders": [
{
"odds": 1,
"selections": [
{
"bet_offer_id": "text",
"count": 1,
"market": "text",
"market_id": 1,
"market_type": "text",
"market_type_id": 1,
"outcome": "text",
"outcome_id": 1,
"period": "text",
"period_id": 1,
"quote": 1,
"quote_group": "text",
"selection_id": "text",
"side": "text",
"uof_external_id": "text"
}
]
}
],
"country": "text",
"country_id": "text",
"event_id": "text",
"event_type": "text",
"league": "text",
"league_id": "text",
"participant_ids": [
"text"
],
"participants": [
"text"
],
"sport": "text",
"sport_id": "text",
"status": "text"
}
],
"status": "success"
}Last updated
Was this helpful?