Betradar - the betting arm of Sportradar
Betradar - the betting arm of Sportradar
Please find below all the documentation needed for our RGS+ integration
Documentation
| Document | Comment |
|---|---|
| The Gaming Platform back office allows customers to operate the Gaming Platform and also to access reports on usage. | |
| The gaming platform frontend is provided as an iframe. The iframe url accepts a set of parameters that specify configuration options. During the integration phase, you will receive the following parameters that you will use for the frontend integration. | |
| Document describes the wallet integration process for the Sportradar Gaming Platform. Hereto referred to as The Platform. | |
| This document descirbes the REST wallet integration. | |
| This is a document which can be used to assist with the RGS+ integration. |
F.A.Q. (by customers)
What IP addresses do customers need to whitelist for connections from Gaming Platform?
The Gaming Platform establishes connections to the client's system from any IP of the below IP range:
...
eu-central-1a.kubernetes 18.194.70.202
eu-central-1b.kubernetes 3.120.204.52
eu-central-1c.kubernetes 3.120.226.49
Do you have examples of requests and responses used in the SOAP calls?
In order to check for examples of request and responses used in SOAP wallet communication, the software SoapUI might come in handy during the wallet integration.
It is open source that allows you to mock a webservice from our WSDL and then you will see examples for all requests end responses. You may want to check the following URL for further details: https://www.soapui.org/soap-mocking/service-mocking-overview.html
Overview
Content Tools