JSON Web Token (JWT)

Some widget use cases require validated data integrity from your backend to prevent misuse by end-users or malicious actors. Create and sign a JSON Web Token (JWT) with a public/private key pair, then pass that token to widgets as a property.

Signing Algorithm

JWT tokens must be signed with RS256 (RSA signature with SHA-256).

#Prerequisites

Tools

OpenSSL toolkit
JWT library for your language (e.g. jsonwebtoken)

Backend

Server-side environment (Node.js, Python, Java, C#, …)
Ability to sign tokens securely

Sportradar Access

Account representative for public key setup
Product credentials when needed (VS API key, Bet Concierge brand ID)

#Implementation Overview

The following diagram illustrates the JWT authentication flow:

#Generate RSA Keys

Create a 2048-bit RSA key pair with OpenSSL.

Send rsa-public.pem to Sportradar so tokens can be validated.

#Sign Tokens Server-Side

Build the payload with required claims and sign with your private key (RS256).

Deliver the token from your backend and set it on widget initialization.

#Step 1: Generate RSA Key Pair

Generate a pair of RSA keys using the OpenSSL toolkit:

bash

# Generate private key (2048-bit RSA)
openssl genrsa -out rsa-private.pem 2048

# Extract public key from private key
openssl rsa -in rsa-private.pem \
  -pubout \
  -outform PEM \
  -out rsa-public.pem

#`rsa-private.pem`

Keep this secure on your backend server and use it to sign tokens.

#`rsa-public.pem`

Send this file to Sportradar for token validation setup.

Optional: Verify the Generated Keys

bash

# View private key
openssl rsa -in rsa-private.pem -text -noout

# View public key
openssl rsa -in rsa-public.pem -pubin -text -noout

Example public key format (rsa-public.pem):

plaintext

-----BEGIN PUBLIC KEY-----
MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA...
...
-----END PUBLIC KEY-----

Security Best Practices

Never expose your private key (rsa-private.pem) in client-side code, version control, or logs
Never share private keys with third parties
Store private keys in secure key management systems or environment variables
Never generate or sign JWT tokens in client-side JavaScript
Rotate keys periodically
Generate separate key pairs for each environment (dev, staging, production)

Non-Production Environments

If you need development or non-production JWTs, tell client setup which environment the public key is for (, , or ), and put the same value in the claim on JWTs signed with that key. Production-only flows can omit ; it defaults to production behavior.

#Step 2: Create JWT Tokens for Users

Every logged-in user requires their own unique JWT.

Generate On-Demand

Create a new token for each page request.

Cache With TTL

Generate once and cache on your backend until near expiration.

#The Token Object

JSON Web Token (JWT) is an open standard (RFC 7519) that defines a compact and self-contained way for securely transmitting information between parties as a JSON object. This information can be verified and trusted because it is digitally signed.

Learn more about JWT structure.

#Header

Algorithm and token type

#Payload

Claims (identity, scope, product data)

#Signature

RS256 signature over header + payload

json

{
  "header": {
    "alg": "RS256",
    "typ": "JWT"
  },
  "payload": {
    "iss": "your-organization",
    "sub": "user123",
    "scope": "vs",
    "iat": 1681718850

#Required Base Claims

All JWT tokens must include these standard claims:

javascript

{
    iss: '<organization>',
    sub: '<id>',
    scope: 'av' | 'vs' | 'sb' | 'av vs sb',
    iat: 1681718850
}

#Product-Specific Claims

Add product claims only for the scopes you enable.

#Step 3: Sign the Token

Sign your JWT using the RS256 algorithm with your private key. Most JWT libraries support RS256 signing.

#Parameters

payload object required

Token payload containing all required claims (see claim descriptions above).

privateKey string required

Your RSA private key in PEM format.

algorithm string required

Must be RS256 (RSA signature with SHA-256).

#Returns

Returns a signed JWT token string that can be used to authenticate with Sportradar widgets and products.

Token Security

Generate tokens server-side only
Create unique tokens for each user session
Never share tokens between users
Tokens are valid for 16 hours maximum (or until exp if specified)
Shorter token lifespans improve security

Example Token Output

plaintext

eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiJ1c2VyMTIzIiwic2NvcGUiOiJ2cyIsImlhdCI6MTY4MTcxODg1MCwiYXBpS2V5Ijoidi3NfbGl2ZV9hYmMxMjN4eXo3ODkiLCJ1c2VySWQiOiJ1c2VyMTIzIiwiZGlzcGxheU5hbWUiOiJKb2huIERvZSIsInVzZXJUeXBlIjoiTm9ybWFsIn0.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c...

Example With Multiple Scopes (Node.js)

javascript

import jwt from "jsonwebtoken";

const token = jwt.sign(
  {
    sub: "user_12345",
    scope: "av vs", // Audio/video + Virtual Stadium
    // iat is added automatically
  },
  process.env.PRIVATE_SIGNING_KEY,
  { algorithm: "RS256" },
);

#Step 4: Pass JWT to Widgets

Deliver the signed JWT from your backend to your frontend application, then pass it to the widget during initialization.

#Key Rotation

Rotate signing keys without service interruption:

#Generate a New Key Pair

Create a new RSA key pair using the same process as Step 1.

#Submit the Public Key

Send the new public key to your Sportradar representative.

#Wait for Confirmation

Sportradar adds the new key to your configuration and notifies you. Both old and new keys work during the transition.

#Switch Your Backend

Start signing with the new private key, then inform Sportradar when migration is complete so the old public key can be removed.

Signing Algorithm

JWT tokens must be signed with RS256 (RSA signature with SHA-256).

#Prerequisites

Tools

OpenSSL toolkit
JWT library for your language (e.g. jsonwebtoken)

Backend

Server-side environment (Node.js, Python, Java, C#, …)
Ability to sign tokens securely

Sportradar Access

Account representative for public key setup
Product credentials when needed (VS API key, Bet Concierge brand ID)

#Implementation Overview

The following diagram illustrates the JWT authentication flow:

#Generate RSA Keys

Create a 2048-bit RSA key pair with OpenSSL.

Send rsa-public.pem to Sportradar so tokens can be validated.

#Sign Tokens Server-Side

Build the payload with required claims and sign with your private key (RS256).

Deliver the token from your backend and set it on widget initialization.

#Step 1: Generate RSA Key Pair

Generate a pair of RSA keys using the OpenSSL toolkit:

bash

# Generate private key (2048-bit RSA)
openssl genrsa -out rsa-private.pem 2048

# Extract public key from private key
openssl rsa -in rsa-private.pem \
  -pubout \
  -outform PEM \
  -out rsa-public.pem

#`rsa-private.pem`

Keep this secure on your backend server and use it to sign tokens.

#`rsa-public.pem`

Send this file to Sportradar for token validation setup.

Optional: Verify the Generated Keys

bash

# View private key
openssl rsa -in rsa-private.pem -text -noout

# View public key
openssl rsa -in rsa-public.pem -pubin -text -noout

Example public key format (rsa-public.pem):

plaintext

-----BEGIN PUBLIC KEY-----
MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA...
...
-----END PUBLIC KEY-----

Security Best Practices

Never expose your private key (rsa-private.pem) in client-side code, version control, or logs
Never share private keys with third parties
Store private keys in secure key management systems or environment variables
Never generate or sign JWT tokens in client-side JavaScript
Rotate keys periodically
Generate separate key pairs for each environment (dev, staging, production)

Non-Production Environments

#Step 2: Create JWT Tokens for Users

Every logged-in user requires their own unique JWT.

Generate On-Demand

Create a new token for each page request.

Cache With TTL

Generate once and cache on your backend until near expiration.

#The Token Object

Learn more about JWT structure.

#Header

Algorithm and token type

#Payload

Claims (identity, scope, product data)

#Signature

RS256 signature over header + payload

json

{
  "header": {
    "alg": "RS256",
    "typ": "JWT"
  },
  "payload": {
    "iss": "your-organization",
    "sub": "user123",
    "scope": "vs",
    "iat": 1681718850

#Required Base Claims

All JWT tokens must include these standard claims:

javascript

{
    iss: '<organization>',
    sub: '<id>',
    scope: 'av' | 'vs' | 'sb' | 'av vs sb',
    iat: 1681718850
}

#Product-Specific Claims

Add product claims only for the scopes you enable.

#Step 3: Sign the Token

Sign your JWT using the RS256 algorithm with your private key. Most JWT libraries support RS256 signing.

#Parameters

payload object required

Token payload containing all required claims (see claim descriptions above).

privateKey string required

Your RSA private key in PEM format.

algorithm string required

Must be RS256 (RSA signature with SHA-256).

#Returns

Returns a signed JWT token string that can be used to authenticate with Sportradar widgets and products.

Token Security

Generate tokens server-side only
Create unique tokens for each user session
Never share tokens between users
Tokens are valid for 16 hours maximum (or until exp if specified)
Shorter token lifespans improve security

Example Token Output

plaintext

eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiJ1c2VyMTIzIiwic2NvcGUiOiJ2cyIsImlhdCI6MTY4MTcxODg1MCwiYXBpS2V5Ijoidi3NfbGl2ZV9hYmMxMjN4eXo3ODkiLCJ1c2VySWQiOiJ1c2VyMTIzIiwiZGlzcGxheU5hbWUiOiJKb2huIERvZSIsInVzZXJUeXBlIjoiTm9ybWFsIn0.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c...

Example With Multiple Scopes (Node.js)

javascript

import jwt from "jsonwebtoken";

const token = jwt.sign(
  {
    sub: "user_12345",
    scope: "av vs", // Audio/video + Virtual Stadium
    // iat is added automatically
  },
  process.env.PRIVATE_SIGNING_KEY,
  { algorithm: "RS256" },
);

#Step 4: Pass JWT to Widgets

Deliver the signed JWT from your backend to your frontend application, then pass it to the widget during initialization.

#Key Rotation

Rotate signing keys without service interruption:

#Generate a New Key Pair

Create a new RSA key pair using the same process as Step 1.

#Submit the Public Key

Send the new public key to your Sportradar representative.

#Wait for Confirmation

Sportradar adds the new key to your configuration and notifies you. Both old and new keys work during the transition.

#Switch Your Backend

Start signing with the new private key, then inform Sportradar when migration is complete so the old public key can be removed.

Claim	Type	Description	Example
`iss`	string	Issuer identifier — identifies the principal that issued the JWT. Typically your organization or application identifier.	`'your-organization'`
`sub`	string	Unique end-user identifier. Use your system's user ID or a salted hash if you prefer not to expose actual IDs.	`'user_12345'` or `'a3f5b2c8d1e4'`
`scope`	string	Space-separated permissions for this user. Controls access to specific features. `av` - Enables audio/video stream access in Live Match Tracker. `vs` - Virtual Stadium access. `sb` - Bet Concierge access	`'av vs'` for LMT audio/video and Virtual Stadium (space-separated)
`iat`	number	Token issued-at timestamp in seconds since Unix epoch (UTC). Default validity: 16 hours. Most JWT libraries add this automatically.	`1681718850`
`exp`	number (optional)	Expiration timestamp in seconds since Unix epoch (UTC). If omitted, defaults to 16 hours after `iat`.	`1681776450`
`env`	string (optional)	Which environment the signing key is for: `prod`, `nonprod`, or `dev`. Set when you use a non-production key (for example a development-only key pair); tell client setup the same when you submit that key's public key. Omit or leave empty for your production key—then behavior matches `prod`.	`'dev'`

Claim	Type	Description	Example
`apiKey`	string	Your Virtual Stadium API key (provided during onboarding)	`'vs_api_key_abc123'`
`displayName`	string	Public name shown to other users in the Virtual Stadium interface	`'JohnDoe'` or `'Player123'`
`userType`	string	User access level: `'Normal'` or `'VIP'`. VIP users have highlighted chat messages.	`'VIP'`

JSON Web Token (JWT)

#Prerequisites

Tools

Backend

Sportradar Access

#Implementation Overview

#Generate RSA Keys

#Share the Public Key

#Sign Tokens Server-Side

#Pass JWT to the Widget

#Step 1: Generate RSA Key Pair

#rsa-private.pem

#rsa-public.pem

#Step 2: Create JWT Tokens for Users

Generate On-Demand

Cache With TTL

#The Token Object

#Header

#Payload

#Signature

#Required Base Claims

#Product-Specific Claims

#Step 3: Sign the Token

#Parameters

#Returns

#Step 4: Pass JWT to Widgets

#Key Rotation

#Generate a New Key Pair

#Submit the Public Key

#Wait for Confirmation

#Switch Your Backend

#Prerequisites

Tools

Backend

Sportradar Access

#Implementation Overview

#Generate RSA Keys

#Share the Public Key

#Sign Tokens Server-Side

#Pass JWT to the Widget

#Step 1: Generate RSA Key Pair

#rsa-private.pem

#rsa-public.pem

#Step 2: Create JWT Tokens for Users

Generate On-Demand

Cache With TTL

#The Token Object

#Header

#Payload

#Signature

#Required Base Claims

#Product-Specific Claims

#Step 3: Sign the Token

#Parameters

#Returns

#Step 4: Pass JWT to Widgets

#Key Rotation

#Generate a New Key Pair

#Submit the Public Key

#Wait for Confirmation

#Switch Your Backend

#`rsa-private.pem`

#`rsa-public.pem`

#`rsa-private.pem`

#`rsa-public.pem`