Betslips
The minimum event's starting datetime.
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: -2hPattern: ^[+-]?[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]?$DEPRECATED: Considers events starting till the from timestamp plus the given
hours. If not set defaults to one day (24 hours).
How many betslips to return.
1Example: 1List including the number of selections each betslip should contain. Can be a number (e.g. 5) or a range (e.g. 2-4).
2-6Example: 2-10Pattern: ^(?<from>\d+)(-(?<to>\d+))?$If true, calculates the betslip's length dynamically based on user's preferences.
If the generated length is outside the provided length range, it will be shifted to
the closest boundary. For example, if the length range is [3-5] and the calculated
length is 2, then it will be shifted to 3. Defaults to false.
falseExample: trueThe max payout each betslip should have. Notice that the returned betslip
might be of less than the requested length if the max_payout is exceeded.
The minimum payout each betslip should have. Notice that the returned betslip
might be of more than the requested length for the min_payout condition to be met.
If true, ensures that all participants will appear only once in the betslip.
Defaults to false.
falseThe user to get recommended betslips for.
Optional filtering on the events and markets to consider for producing
the betslips. It expects a string adhering to the filtering format, as
described in the filtering section, e.g. sport:eq:Soccer;market:eq:1X2.
Excludes the top n popular selections from the results.
0Applies a limit to a group of items. For more information, head to
Limiting -> Group Limiting section of the docs.
country:5,country_id:2.
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","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","side","count"]Possible values: The columns to sort the results by. It expects a string adhering to
the ordering format, as described in the ordering section, e.g.
+begin,-league.
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.
A string in the format 'field:value', where 'field' is a supported field and 'value' is a positive integer. Used for configuration, filtering, or limiting based on field values.
sport_id:1Possible values: 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 Entity
Too Early
Internal Server Error
The minimum event's starting datetime.
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: -2hPattern: ^[+-]?[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]?$DEPRECATED: Considers events starting till the from timestamp plus the given
hours. If not set defaults to one day (24 hours).
How many betslips to return.
1Example: 1List including the number of selections each betslip should contain. Can be a number (e.g. 5) or a range (e.g. 2-4).
2-6Example: 2-10Pattern: ^(?<from>\d+)(-(?<to>\d+))?$The max payout each betslip should have.
The minimum payout each betslip should have.
If true, ensures that all participants will appear only once in the betslip.
Defaults to false.
falseOptional filtering on the events and markets to consider for producing
the betslips. It expects a string adhering to the filtering format, as
described in the filtering section, e.g. sport:eq:Soccer;market:eq:1X2.
The user to get recommended betslips for.
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","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","side","count"]Possible values: The columns to sort the results by. It expects a string adhering to
the ordering format, as described in the ordering section, e.g.
+begin,-league.
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.
The location of the page where the request takes place.
inplay_widgetCustom 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 Entity
Too Early
Internal Server Error
Last updated
Was this helpful?