External Content - Description

MTS supports consuming and accepting bets which include external content (also often referred to as non-SR content), i.e. content (betting events, outcomes, odds, etc.) provided by sources other than Sportradar. This allows clients with their own feed providers to combine different feed content in a single ticket that MTS processes. MTS provides risk management only for Sportradar content.

In this case, an end-customer can combine selections from different feeds in the same ticket.

Different options for combining selections in a ticket are as follows:

  • Pure Sportradar content selections (only Sportradar content selections appear in the bet),

  • Mixed content selections (Sportradar and external (non-Sportradar) content selections appear in the bet),

  • Pure non-Sportradar content selections (only external content selections appear in the bet). \

Note

  • Support of external (non-Sportradar) content is turned off by default. To enable it, a client must contact the MTS Operational Account Manager (or an MTS Client Integration Engineer during the integration process).

  • In the case of mixed-content bets, risk management will be provided only for Sportradar content.

Cash-out is only possible without any validations, the only check being that the maximum payout is not breached.

Rules for composing Event, Outcome and ExpSettleTime fields

In a Ticket placement request, fields of the Selections object (where selections "type":"external") should be composed according to the below rules:

    • The value of Event field must start with "ext:match:", followed by an anonymised and unique integer identifying the event (defined by the client) (e.g. "event" : "ext:match:736977").

    • The value of Outcome field should start with either "ext-pre:" (pre-match selection) or "ext-live:" (live selection), followed by the value of OperatorId field (client ID) and anonymised selection ID (defined by the client) in format :sXX, where X is a digit (eg. "outcome": "ext-pre:9985:s77"). Regex: (ext-live|ext-pre):([^\:]+)\:(s\d{1,2})

    • The value of ExpSettleTime field should be set to the expected settlement time (in the client's system) for the selection

Note

All open tickets with the “expSettleTime” value older than 30 days will be settled as lost. After two months, tickets will be archived. In the case of multiple selections, the highest value is considered.

Last updated

Was this helpful?