Create operator configuration

Creates a new regional operator configuration. Requires the MANAGE_ODDS_OPERATOR permission. Returns 409 if a configuration with the given id already exists.

Body Params
string
required

Operator config identifier, which is also the odds operator this config serves. Required. Must match an operator present in the odds data; an unknown value returns 400. On PUT it must match the {id} path parameter, which is the authoritative identifier; a mismatch returns 400.

string
required

Display name

string
required

Domain identifier used in the operators filter

string

Responsible gambling disclaimer text

branding
object

Brand colours

assets
array of objects

Logo and image assets

assets
market_urls
object

Market URL map. Keys are matched exactly and are case-sensitive; an unknown key returns 400. Use default as the fallback for any market not explicitly listed. Omitting the field entirely clears all URL config. Three reserved keys: event and competition hold the operator's event and competition page templates and are resolved server-side; betslip holds the betslip template and is returned to the client unresolved.

Accepted keys — default, plus:

PredictionMarket: FT_1X2, HT_1X2, BOTH_TEAMS_SCORE, DOUBLE_CHANCE, HT_FT, OVER_GOALS, OVER_GOALS_0_5, OVER_GOALS_1_5, OVER_GOALS_2_5, OVER_GOALS_3_5, OVER_GOALS_4_5, OVER_GOALS_5_5, OVER_GOALS_6_5, OVER_CORNERS, OVER_CORNERS_6_5, OVER_CORNERS_7_5, OVER_CORNERS_8_5, OVER_CORNERS_9_5, OVER_CORNERS_10_5, OVER_CORNERS_11_5, OVER_CORNERS_12_5, OVER_CORNERS_13_5, CORNERS_MATCH, RED_CARD_MATCH, PENALTY_MATCH, CORRECT_SCORE, CORRECT_SCORE_HT, CORRECT_SCORE_ADVANCED, PLAYER_SCORE, PLAYER_SCORE_FIRST_GOAL, PLAYER_SCORE_TWICE, PLAYER_SCORE_HATTRICK, PLAYER_YELLOW_CARD, PLAYER_RED_CARD, PLAYER_PERFORMANCE

Football: DRAW_NO_BET, ASIAN_HANDICAP, HT_HANDICAP, HT_ASIAN_HANDICAP, OVER_GOALS, OVER_GOALS_1, OVER_GOALS_2, OVER_GOALS_3, OVER_GOALS_4, OVER_GOALS_5, OVER_GOALS_6, OVER_GOALS_7, OVER_GOALS_7_5, OVER_GOALS_8_5, OVER_GOALS_9_5, OVER_GOALS_10_5, HT_OVER_GOALS, HT_OVER_GOALS_0_5, HT_OVER_GOALS_1_5, HT_OVER_GOALS_2_5, HT_OVER_GOALS_3_5, HT_OVER_GOALS_4_5, HT_OVER_GOALS_5_5, HT_OVER_GOALS_6_5, OVER_CORNERS_14_5, OVER_CORNERS_15_5, OVER_CORNERS_16_5, OVER_CORNERS_17_5, TEAM_SCORE_SECOND_GOAL, TEAM_SCORE_THIRD_GOAL, TEAM_SCORE_FOURTH_GOAL, TEAM_SCORE_FIFTH_GOAL, TEAM_SCORE_SIXTH_GOAL

Basketball: WINNER_OT, HANDICAP_OT, OVER_POINTS_OT

Ice hockey: WINNER_OT_PEN, HANDICAP_OT_PEN, OVER_GOALS_OT_PEN, P1_OVER_GOALS, P2_OVER_GOALS, P3_OVER_GOALS

Tennis: WINNER, SET_WINNER, GAME_WINNER, GAME_HANDICAP, OVER_GAMES, OVER_SETS

American football: WINNER_OT, HANDICAP_OT, OVER_POINTS_OT (same codes as basketball)

Note: OVER_GOALS_2_5 (over 2.5 goals) and OVER_GOALS_2 are different markets — the _N_5 and _N families are not interchangeable.

Note: there is no TEAM_SCORE_FIRST_GOAL — the team-scores-Nth-goal family starts at TEAM_SCORE_SECOND_GOAL. For a player scoring the first goal use PLAYER_SCORE_FIRST_GOAL.

url_settings
object

Optional URL template settings: slug separator, selection id separator and sport slugs

Responses

Language
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json