Accessing the API

If your integration is API-based, a service account needs to be provisioned instead of a user account. The provisioning request must be initiated through your Sportradar contact. Upon completion, you will receive the client_id and client_secret, which are used to authenticate via OAuth2 and access the Insight Tech APIs. For security reasons, these credentials should be stored securely and used according to your internal authentication policies.

Environments

You will receive separate credentials and endpoints for each environment:

Environment	API Base URL
Integration	https://api.insighttechservices-nonprod.sportradar.dev/ci
Production	https://api.insighttechservices.sportradar.com

Start all development and testing in the integration environment before switching to production.

API Authentication

All Insight Tech Services APIs use OAuth 2.0 Client Credentials for secure, server-to-server authentication.

OAuth Token Request

Send a POST request to the Auth0 token endpoint using your credentials:

Field		Integration	Production
URL		https://auth.sportradar.com/oauth/token	https://auth.sportradar.com/oauth/token
Header	Content-Type	application/x-www-form-urlencoded	application/x-www-form-urlencoded
Data	client_id	Received in the encrypted file.	Received in the encrypted file.
	client_secret	Received in the encrypted file.	Received in the encrypted file.
	audience	mts-insight-tech-non-prod	mts-insight-tech
	grant_type	client_credentials	client_credentials

Example Request

curl -X POST 'https://auth.sportradar.com/oauth/token' \
--header 'Content-Type: application/x-www-form-urlencoded' \
--data-urlencode 'client_id=YOUR_CLIENT_ID' \
--data-urlencode 'client_secret=YOUR_CLIENT_SECRET' \
--data-urlencode 'audience=mts-insight-tech' \
--data-urlencode 'grant_type=client_credentials'

Example response

{
    "access_token": "wk19ahxiOiJSUzI1NiIsInR5cCI6IkpXVCIsI...",
    "expires_in": 300,
    "token_type": Bearer"
}

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. Your application should refresh them automatically.

Note

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

What you need to start

To begin integration, ensure you have the following:

• Provisioned credentials (client_id, client_secret)

• Public/private key pair for decryption

• Access to integration API endpoints

• Understanding of supported models (see Model Catalogue)

• OAuth token setup

• An integration plan using ticket-inform, ticket-placement