Casino Games
Optional filtering of the games to retrieve. Can contain filters
related to game, user, game properties or game statistics.
It expects a string adhering to the filtering format, as described
in the filtering section, e.g. enabled:eq:1.
enabled:eq:1Possible 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.
+game_name,-game_studio.
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.
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. game_id,game_name.
game_idPossible values: The page to retrieve. Notice that if set the random access pagination mechanism will be used. If not set the pagination mechanism default to the keyset mode.
The number of items ot include in each page.
100The cursor to get data from. It should be retrieved from the pagination
section of a previous response in case of keyset pagination.
This value will be ignored if the page parameter has been provided
and random access pagination will be used instead.
Notice that the the cursor is cryptographically signed and verified, make sure to set the exact value it was returned.
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 game id for which we seek frequently combined games.
MERGEyeofHorusThe user to get recommendations for.
0The number of last games that user played to exclude from recommendations.
This functionality works as expected only if the user parameter is given.
0The number of last games that user clicked to exclude from recommendations.
This functionality works as expected only if the user parameter is given.
0Number of games to return.
100Example: 5Optional dynamic filtering of the items to retrieve. If any dynamic filter is set,
the filter's value will be dynamically calculated and used. Notice that for user
related filters, the user query parameter must be provided. For example,
dynamic_filters=user_country will return data related only to the user's specific country.
Optional filtering of the games to retrieve. Can contain filters
related to game, user, game properties or game statistics.
It expects a string adhering to the filtering format, as described
in the filtering section, e.g. enabled:eq:1.
enabled:eq:1Possible 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.
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. game_id,game_name.
game_id,confidencePossible 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 to get recommendations for.
0The number of last games that user played to exclude from recommendations.
This functionality works as expected only if the user parameter is given.
0The number of last games that user clicked to exclude from recommendations.
This functionality works as expected only if the user parameter is given.
0Number of games to return.
100Example: 5Optional filtering of the games to retrieve. Can contain filters
related to game, user, game properties or game statistics.
It expects a string adhering to the filtering format, as described
in the filtering section, e.g. enabled:eq:1.
enabled:eq:1Possible values: Optional dynamic filtering of the items to retrieve. If any dynamic filter is set,
the filter's value will be dynamically calculated and used. Notice that for user
related filters, the user query parameter must be provided. For example,
dynamic_filters=user_country will return data related only to the user's specific country.
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. recommended:0.3.
For more information head to the ordering documentation section.
Optional filtering of the results based on the ranking of the given entities.
It expects a string adhering to the ranking format, as described in the
ranking filtering section, e.g. game_studio_recommended:1.
When user related filters are defined they get applied only if one of the following conditions are met:
ignore_user_filter_threshold=true- The count of game sessions when applying those filters is statistically significant.
falseApplies a limit to a group of items. For more information, head to
Limiting -> Group Limiting section of the docs.
game_studio:5,category:2.
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.
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. game_id,game_name.
game_id,confidencePossible 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
Optional filtering of the games to retrieve. Can contain filters
related to game, user, game properties or game statistics.
It expects a string adhering to the filtering format, as described
in the filtering section, e.g. enabled:eq:1.
enabled:eq:1Possible values: How many days before to search for new games. Defaults to 60.
60Number of games to return.
100Example: 5The user to get recommendations for.
0The number of last games that user played to exclude from recommendations.
This functionality works as expected only if the user parameter is given.
0The number of last games that user clicked to exclude from recommendations.
This functionality works as expected only if the user parameter is given.
0Optional dynamic filtering of the items to retrieve. If any dynamic filter is set,
the filter's value will be dynamically calculated and used. Notice that for user
related filters, the user query parameter must be provided. For example,
dynamic_filters=user_country will return data related only to the user's specific country.
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.
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. game_id,game_name.
game_id,confidencePossible values: The location of the page where the request takes place.
inplay_widgetOptional 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. recommended:0.3,popular:0.2.
For more information head to the ordering documentation section.
Optional filtering of the results based on the ranking of the given entities.
It expects a string adhering to the ranking format, as described in the
ranking filtering section, e.g. game_studio_recommended:1.
Applies a limit to a group of items. For more information, head to
Limiting -> Group Limiting section of the docs.
game_studio:5,category:2.
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 user to get recommendations for.
0The number of last games that user played to exclude from recommendations.
This functionality works as expected only if the user parameter is given.
0The number of last games that user clicked to exclude from recommendations.
This functionality works as expected only if the user parameter is given.
0Number of games to return.
100Example: 5Optional filtering of the games to retrieve. Can contain filters
related to game, user, game properties or game statistics.
It expects a string adhering to the filtering format, as described
in the filtering section, e.g. enabled:eq:1.
enabled:eq:1Possible values: When user related filters are defined they get applied only if one of the following conditions are met:
ignore_user_filter_threshold=true- The count of game sessions when applying those filters is statistically significant.
falseOptional 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. recommended:0.3.
For more information head to the ordering documentation section.
Optional filtering of the results based on the ranking of the given entities.
It expects a string adhering to the ranking format, as described in the
ranking filtering section, e.g. game_studio_recommended:1.
Applies a limit to a group of items. For more information, head to
Limiting -> Group Limiting section of the docs.
game_studio:5,category:2.
Optional dynamic filtering of the items to retrieve. If any dynamic filter is set,
the filter's value will be dynamically calculated and used. Notice that for user
related filters, the user query parameter must be provided. For example,
dynamic_filters=user_country will return data related only to the user's specific country.
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.
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. game_id,game_name.
game_id,confidencePossible 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 to get recommendations for.
0The number of last games that user played to exclude from recommendations.
This functionality works as expected only if the user parameter is given.
0The number of last games that user clicked to exclude from recommendations.
This functionality works as expected only if the user parameter is given.
0Number of games to return.
100Example: 5Optional filtering of the games to retrieve. Can contain filters
related to game, user, game properties or game statistics.
It expects a string adhering to the filtering format, as described
in the filtering section, e.g. enabled:eq:1.
enabled:eq:1Possible values: Optional dynamic filtering of the items to retrieve. If any dynamic filter is set,
the filter's value will be dynamically calculated and used. Notice that for user
related filters, the user query parameter must be provided. For example,
dynamic_filters=user_country will return data related only to the user's specific country.
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.
Optional filtering of the results based on the ranking of the given entities.
It expects a string adhering to the ranking format, as described in the
ranking filtering section, e.g. game_studio_recommended:1.
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.
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. game_id,game_name.
game_id,confidencePossible 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 game ids for which to return similar games. If multiple games are provided the games returned are going to be the ones with the shortest average distance to all of the provided games.
The user to get recommendations for.
0The number of last games that user played to exclude from recommendations.
This functionality works as expected only if the user parameter is given.
0The number of last games that user clicked to exclude from recommendations.
This functionality works as expected only if the user parameter is given.
0Number of games to return.
100Example: 5Optional filtering of the games to retrieve. Can contain filters
related to game, user, game properties or game statistics.
It expects a string adhering to the filtering format, as described
in the filtering section, e.g. enabled:eq:1.
enabled:eq:1Possible values: Optional dynamic filtering of the items to retrieve. If any dynamic filter is set,
the filter's value will be dynamically calculated and used. Notice that for user
related filters, the user query parameter must be provided. For example,
dynamic_filters=user_country will return data related only to the user's specific country.
If it's true include input items in response. By default is set to false.
falseThe 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.
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. game_id,game_name.
game_id,confidencePossible 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 to get recommendations for.
0The number of last games that user played to exclude from recommendations.
This functionality works as expected only if the user parameter is given.
0The number of last games that user clicked to exclude from recommendations.
This functionality works as expected only if the user parameter is given.
0Number of games to return.
100Example: 5Optional filtering of the games to retrieve. Can contain filters
related to game, user, game properties or game statistics.
It expects a string adhering to the filtering format, as described
in the filtering section, e.g. enabled:eq:1.
enabled:eq:1Possible values: 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. recommended:0.3.
For more information head to the ordering documentation section.
Optional filtering of the results based on the ranking of the given entities.
It expects a string adhering to the ranking format, as described in the
ranking filtering section, e.g. game_studio_recommended:1.
When user related filters are defined they get applied only if one of the following conditions are met:
ignore_user_filter_threshold=true- The count of game sessions when applying those filters is statistically significant.
falseOptional dynamic filtering of the items to retrieve. If any dynamic filter is set,
the filter's value will be dynamically calculated and used. Notice that for user
related filters, the user query parameter must be provided. For example,
dynamic_filters=user_country will return data related only to the user's specific country.
Applies a limit to a group of items. For more information, head to
Limiting -> Group Limiting section of the docs.
game_studio:5,category:2.
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.
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. game_id,game_name.
game_id,confidencePossible values: The location of the page where the request takes place.
inplay_widgetConsiders game sessions played 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?