Sportradar

Real-time sports data, odds comparison, and win probabilities across global competitions.

Detail	Value
Category	iGaming
Base URL	https://api.sportradar.com
Authentication	API Key (Query)
Endpoints	9
Connector key	sportradar

Using Sportradar in a workflow

1. Go to Connections and click New Connection.
2. Pick Sportradar from the marketplace.
3. Enter your credentials (see Authentication above for what's expected).
4. In a workflow, drop an API Call node and select this connection.
5. Pick the operation you need from the Operation dropdown. The full list is below.

Available endpoints

Endpoint	Summary
GET /oddscomparison-prematch/trial/v2/sports	List all sports
GET /oddscomparison-prematch/trial/v2/{lang}/sport_events/{id}/markets.json	Pre-match odds
GET /oddscomparison-live-odds/trial/v2/{lang}/sport_events/{id}/markets.json	Live odds
GET /oddscomparison-prematch/trial/v2/competitions	List competitions
GET /oddscomparison-prematch/trial/v2/daily-sport-event-schedule	Daily schedule
GET /oddscomparison-prematch/trial/v2/books	List bookmakers
GET /probabilities/trial/v1/{lang}/sport_events/{id}/probabilities.json	Win probabilities
GET /soccer/trial/v4/{lang}/competitions.json	Soccer competitions
GET /soccer/trial/v4/{lang}/competitors/{id}/profile.json	Team profile

Each endpoint is documented in full below. Use the outline on the right to jump to one.

GET /oddscomparison-prematch/trial/v2/sports

List all sports

Detail	Value
Operation ID	sports.listSports
Method	GET
Path	/oddscomparison-prematch/trial/v2/sports

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Sportradar connection from the Connection dropdown.
3. In the Operation dropdown, select sports.listSports.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Sportradar API reference.

GET /oddscomparison-prematch/trial/v2/{lang}/sport_events/{id}/markets.json

Pre-match odds

Detail	Value
Operation ID	sports.getPrematchOdds
Method	GET
Path	/oddscomparison-prematch/trial/v2/{lang}/sport_events/{id}/markets.json

Parameters

Name	Location	Type	Required
lang	path	string	Yes
id	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Sportradar connection from the Connection dropdown.
3. In the Operation dropdown, select sports.getPrematchOdds.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked: fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Sportradar API reference.

GET /oddscomparison-live-odds/trial/v2/{lang}/sport_events/{id}/markets.json

Live odds

Detail	Value
Operation ID	sports.getLiveOdds
Method	GET
Path	/oddscomparison-live-odds/trial/v2/{lang}/sport_events/{id}/markets.json

Parameters

Name	Location	Type	Required
lang	path	string	Yes
id	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Sportradar connection from the Connection dropdown.
3. In the Operation dropdown, select sports.getLiveOdds.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked: fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Sportradar API reference.

GET /oddscomparison-prematch/trial/v2/competitions

List competitions

Detail	Value
Operation ID	sports.listCompetitions
Method	GET
Path	/oddscomparison-prematch/trial/v2/competitions

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Sportradar connection from the Connection dropdown.
3. In the Operation dropdown, select sports.listCompetitions.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Sportradar API reference.

GET /oddscomparison-prematch/trial/v2/daily-sport-event-schedule

Daily schedule

Detail	Value
Operation ID	sports.getDailySchedule
Method	GET
Path	/oddscomparison-prematch/trial/v2/daily-sport-event-schedule

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Sportradar connection from the Connection dropdown.
3. In the Operation dropdown, select sports.getDailySchedule.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Sportradar API reference.

GET /oddscomparison-prematch/trial/v2/books

List bookmakers

Detail	Value
Operation ID	sports.listBookmakers
Method	GET
Path	/oddscomparison-prematch/trial/v2/books

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Sportradar connection from the Connection dropdown.
3. In the Operation dropdown, select sports.listBookmakers.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Sportradar API reference.

GET /probabilities/trial/v1/{lang}/sport_events/{id}/probabilities.json

Win probabilities

Detail	Value
Operation ID	sports.getWinProbabilities
Method	GET
Path	/probabilities/trial/v1/{lang}/sport_events/{id}/probabilities.json

Parameters

Name	Location	Type	Required
lang	path	string	Yes
id	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Sportradar connection from the Connection dropdown.
3. In the Operation dropdown, select sports.getWinProbabilities.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked: fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Sportradar API reference.

GET /soccer/trial/v4/{lang}/competitions.json

Soccer competitions

Detail	Value
Operation ID	sports.getSoccerCompetitions
Method	GET
Path	/soccer/trial/v4/{lang}/competitions.json

Parameters

Name	Location	Type	Required
lang	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Sportradar connection from the Connection dropdown.
3. In the Operation dropdown, select sports.getSoccerCompetitions.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked: fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Sportradar API reference.

GET /soccer/trial/v4/{lang}/competitors/{id}/profile.json

Team profile

Detail	Value
Operation ID	sports.getTeamProfile
Method	GET
Path	/soccer/trial/v4/{lang}/competitors/{id}/profile.json

Parameters

Name	Location	Type	Required
lang	path	string	Yes
id	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Sportradar connection from the Connection dropdown.
3. In the Operation dropdown, select sports.getTeamProfile.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked: fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Sportradar API reference.