Selections
Comma separated list of selection ids for which to return similar selections.
c495ac571a7e4ecf2014abd597d2c1aaNumber of selections to return.
5Example: 5Optional filtering on the events and markets to consider for the returned selections.
It expects a string adhering to the filtering format, as described in the filtering section,
e.g. sport:eq:Soccer;market:eq:1X2.
sport:eq:Soccer;market:eq:1X2Possible values: 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: 0Pattern: ^[+-]?[0-9]+([.][0-9]+)?[smhd]?$Considers events starting till the from timestamp plus the given
minutes/hours/days. If not set defaults to 2 days.
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).
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","uof_external_id","bet_offer_id","market","market_id","market_type","market_type_id","outcome","outcome_id","period","period_id","quote","quote_group","side","count","distance","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_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
The user id.
Number of selections to return for each event.
1Example: 1Number of events to return.
5Example: 5Optional filtering on the events and markets to consider for the returned selections.
It expects a string adhering to the filtering format, as described in the filtering section,
e.g. sport:eq:Soccer;market:eq:1X2.
sport:eq:Soccer;market:eq:1X2Possible values: 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: 0Pattern: ^[+-]?[0-9]+([.][0-9]+)?[smhd]?$Considers events starting till the from timestamp plus the given
minutes/hours/days. If not set defaults to 2 days.
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).
The event ids to get selections for. If not set, the most recommended events for the user will be automatically picked.
sr:match:23150637Optional 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","uof_external_id","bet_offer_id","market","market_id","market_type","market_type_id","outcome","outcome_id","period","period_id","quote","quote_group","side","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: Applies a limit to a group of items. For more information, head to
Limiting -> Group Limiting section of the docs.
country:5,country_id:2.
The columns to sort the results by. It expects a string adhering to
the ordering format, as described in the ordering section, e.g.
+event_confidence,-league_confidence.
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.
Optional re ordering of the results based on one or more metrics.
Expected format is a comma separated list of keywords where each value
should be a float in the range [0,1]. e.g. popular:0.3,trending:0.2.
For more information head to the ordering documentation section.
Number of items to use when reordering items with reorder_by parameter. This
parameter is meaningful only when reorder_by is also set. If not set, then count
will be used as population.
5A 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:3Possible 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
Number of selections to return.
5Example: 5Comma separated list of event ids for which to return selections.
sr:match:20521307,sr:match:20521317Optional filtering on the events and markets to consider for the returned selections.
It expects a string adhering to the filtering format, as described in the filtering section,
e.g. sport:eq:Soccer;market:eq:1X2.
sport:eq:Soccer;market:eq:1X2Possible values: 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: 0Pattern: ^[+-]?[0-9]+([.][0-9]+)?[smhd]?$Considers events starting till the from timestamp plus the given
minutes/hours/days. If not set defaults to 2 days.
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).
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","uof_external_id","bet_offer_id","market","market_id","market_type","market_type_id","outcome","outcome_id","period","period_id","quote","quote_group","side","count"]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_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
Comma separated list of the selection ids to sort.
c495ac571a7e4ecf2014abd597d2c1aaThe user id.
Comma separated list of keywords. If given, this input will be used
as user demographics data for the recommendations, e.g country:gr,city:ath.
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","uof_external_id","bet_offer_id","market","market_id","market_type","market_type_id","outcome","outcome_id","period","period_id","quote","quote_group","side","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.
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
Number of selections to return.
5Example: 5Comma separated list of event ids for which to return trending selections.
sr:match:27913362,sr:match:26142132Optional filtering on the events and markets to consider for the returned selections.
It expects a string adhering to the filtering format, as described in the filtering section,
e.g. sport:eq:Soccer;market:eq:1X2.
sport:eq:Soccer;market:eq:1X2Possible values: 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: 0Pattern: ^[+-]?[0-9]+([.][0-9]+)?[smhd]?$Considers events starting till the from timestamp plus the given
minutes/hours/days. If not set defaults to 2 days.
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).
Used to return results aggregated in the given market category. Instead of returning selections, this option allows to rank the markets on the given aggregation type level. By default no aggregation will take place. Available options are:
market_type_and_market: Return selections aggregated on market type and market.market_type: Return selections aggregated on market type.market: Return selections aggregated on market.
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","uof_external_id","bet_offer_id","market","market_id","market_type","market_type_id","outcome","outcome_id","period","period_id","quote","quote_group","side","score"]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_widgetConsiders bets placed after the current timestamp minus the given
minutes/hours/days. If not set defaults to 2 days.
The value must be in range [1m - 7d].
2dExample: 3hPattern: ^[+-]?[0-9]+([.][0-9]+)?[smhd]?$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
Last updated
Was this helpful?