Connectivity

Connection endpoints

WebSocket over TLS 1.2/1.3 secure connection

Transaction 3.0 API	Transaction Stream
WebSocket connection to send transaction v3.0 API requests and receive responses	WebSocket connection to receive transactions over Transaction stream
Client integration environment Host: wss.dataplane-nonprod.sportradar.dev Port: 443	Client integration environment Host: wss-feedmesh.dataplane-nonprod.sportradar.dev Port: 443
Production environment Host: wss.dataplane.sportradar.com Port: 443	Production environment Host: wss-feedmesh.dataplane.sportradar.com Port: 443

Authentication

Before connecting to the above connection endpoints, the client must obtain a token. To obtain the token, a POST request must be made to https://auth.sportradar.com/oauth/token. The request must include a Content-Type header and in the body, 4 url encoded key-value pairs are required.

Note

If you are establishing both the Transaction 3.0 API and the Transaction stream WebSocket connections, you must request two separate tokens. However, the client_id and client_secret are the same for both connections.

	Attribute name	Attribute value
Header	Content-Type	application/x-www-form-urlencoded
Body - url encoded key value pair	client_id	<Sportradar provided client id>
Body - url encoded key value pair	client_secret	<Sportradar provided client secret>
Body - url encoded key value pair	audience	Transaction 3.0 API, Client integration environment: mbs-dp-non-prod-wss
		Transaction 3.0 API, Production environment: mbs-dp-production-wss
		Transaction stream, Client integration environment: mbs-dp-non-prod-feed-mesh-wss
		Transaction stream, Production environment: mbs-dp-production-feed-mesh-wss
Body - url encoded key value pair	grant_type	client_credentials

Example using cURL:

curl -L -X POST 'https://auth.sportradar.com/oauth/token' \
--header 'Content-Type: application/x-www-form-urlencoded' \
--data-urlencode 'client_id=<provided client id>' \
--data-urlencode 'client_secret=<provided client secret>' \
--data-urlencode 'audience=mbs-dp-non-prod-wss' \
--data-urlencode 'grant_type=client_credentials'

The request returns a JSON response with "access_token" field/attribute that is necessary to establish a WebSocket connection:

{
    "access_token": "GENERATED_TOKEN",
    "expires_in": 300,
    "token_type": "Bearer"
}

When establishing a connection to the WebSocket, the value of access_token must be provided in an Authorization header. Value of the header must be: Bearer GENERATED_TOKEN, where GENERATED_TOKEN must be replaced with the value obtained from the JSON response.

Example using wscat:

wscat -H "Authorization: Bearer GENERATED_TOKEN" --connect wss://wss.dataplane-nonprod.sportradar.dev

The access_token must be included in the Authorization header of all subsequent API requests. Tokens are valid for a relatively short timeframe (5 mins) and must be reused during their validity timeframe. If the token has expired, follow the procedure outlined above to generate a new one.

Note

Clients must reuse non-expired tokens. A new token should be requested only a few seconds before the existing one has expired.

Note

If you believe your credentials have been compromised or accessed without authorization, please contact your Operational Account Manager (OAM), Service Delivery Manager (SDM), or email [e-mail] and we will rotate your Client ID and/or Client Secret.

Transaction stream (subscribe message)

Once a Transaction stream WebSocket connection has been established, send the subscribe message based on the template below. Send the actual operatorid (client identification). Value of channelid should be one of the following: "all", "final", "full", "cashout", depending on the setup and the type of requested information.

{
    "operation": "subscription",
    "client": {
        "subscribe": true,
        "operatorid": "xxxx",
        "channelid": ["yyy"]
    }
}

If the subscription is successful, you will receive a message similar to the one below.

Once messages are available, you will start receiving them in the following format:

{
  "originalKey": "internalId",
  "originalTimestamp": 1764990951652,
  "transformedData": {
    "payload": {
      "field1": "value1",
      "field2": {
        "subfield1": "subvalue1",
        "subfield2": "subvalue2"
      }
    }
  }

Connections

To establish the connection, a token is required (see above). Maximum connection duration is 2h. After 2h, the connection is automatically terminated, and a new connection must be established with a new token. Each client's node should establish at least one WebSocket connection to the MTS endpoint. MTS servers will reply with a response through the same connection on which the request was received. In the event of an unexpected connection termination, the client should resend all requests for which a response was not received. For such requests, MTS will reply with an original response (the same response as it would be received if the termination of a connection did not occur).

Rate Limiting

MTS performs the client request rate limiting described below. The values are valid:

• Per client

• For all request types (operation types) combined

Requests per second	Requests per minute
500	5.000

Limitations

The maximum supported size of a WebSocket frame is 32 KB. The maximum supported size of the message payload is 128 KB. Because of the WebSocket frame-size quota of 32 KB, a message larger than 32 KB must be split into multiple frames, each 32 KB or smaller (maximum number of frames is 4). If a larger message (or larger frame size) is received, the connection is closed with code 1009.

Avoid IP-based whitelisting

Clients should avoid IP-based whitelisting for WebSocket connections to MBS Dataplane because WebSocket connections are provided through the AWS API Gateway. AWS dynamically manages the underlying infrastructure, so IPs may change without notice. Attempting to whitelist specific IPs may result in unintended connectivity failures. Any issues resulting from such configurations are the sole responsibility of the client and are considered a known risk. Instead, clients should rely on TLS-secured WebSocket (wss://) connections with MBS Dataplane. There is a valid server certificate from the TLS handshake, which clients should verify based on the Fully Qualified Domain Name (FQDN) they are connecting to: wss://wss.dataplane.sportradar.com/

By verifying the server certificate against this FQDN, clients ensure a secure and trusted connection without relying on static IPs.