The Odds API

Aggregated betting odds from multiple bookmakers across global sports markets.

Detail	Value
Category	iGaming
Base URL	`https://api.the-odds-api.com`
Authentication	API Key (Query)
Endpoints	8
Connector key	`the-odds-api`

Using The Odds API in a workflow

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

Available endpoints

Endpoint	Summary
`GET /v4/sports/`	List in-season sports
`GET /v4/sports/{sport}/odds/`	Odds for a sport
`GET /v4/sports/{sport}/scores/`	Live/recent scores
`GET /v4/sports/{sport}/events`	List events
`GET /v4/sports/{sport}/events/{eventId}/odds`	Event odds
`GET /v4/sports/{sport}/participants`	Teams/players
`GET /v4/historical/sports/{sport}/odds/`	Historical odds
`GET /v4/historical/sports/{sport}/events`	Historical events

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

GET /v4/sports/

List in-season sports

Detail	Value
Operation ID	`odds.listSports`
Method	`GET`
Path	`/v4/sports/`

Parameters

No parameters.

Using this endpoint in a workflow

Add an API Call node to your workflow.
Pick your The Odds API connection from the Connection dropdown.
In the Operation dropdown, select odds.listSports.
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 The Odds API API reference.

GET /v4/sports/{sport}/odds/

Odds for a sport

Detail	Value
Operation ID	`odds.getOdds`
Method	`GET`
Path	`/v4/sports/{sport}/odds/`

Parameters

Name	Location	Type	Required
`sport`	path	string	Yes

Using this endpoint in a workflow

Add an API Call node to your workflow.
Pick your The Odds API connection from the Connection dropdown.
In the Operation dropdown, select odds.getOdds.
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 The Odds API API reference.

GET /v4/sports/{sport}/scores/

Live/recent scores

Detail	Value
Operation ID	`odds.getScores`
Method	`GET`
Path	`/v4/sports/{sport}/scores/`

Parameters

Name	Location	Type	Required
`sport`	path	string	Yes

Using this endpoint in a workflow

Add an API Call node to your workflow.
Pick your The Odds API connection from the Connection dropdown.
In the Operation dropdown, select odds.getScores.
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 The Odds API API reference.

GET /v4/sports/{sport}/events

List events

Detail	Value
Operation ID	`odds.listEvents`
Method	`GET`
Path	`/v4/sports/{sport}/events`

Parameters

Name	Location	Type	Required
`sport`	path	string	Yes

Using this endpoint in a workflow

Add an API Call node to your workflow.
Pick your The Odds API connection from the Connection dropdown.
In the Operation dropdown, select odds.listEvents.
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 The Odds API API reference.

GET /v4/sports/{sport}/events/{eventId}/odds

Event odds

Detail	Value
Operation ID	`odds.getEventOdds`
Method	`GET`
Path	`/v4/sports/{sport}/events/{eventId}/odds`

Parameters

Name	Location	Type	Required
`sport`	path	string	Yes
`eventId`	path	string	Yes

Using this endpoint in a workflow

Add an API Call node to your workflow.
Pick your The Odds API connection from the Connection dropdown.
In the Operation dropdown, select odds.getEventOdds.
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 The Odds API API reference.

GET /v4/sports/{sport}/participants

Teams/players

Detail	Value
Operation ID	`odds.listParticipants`
Method	`GET`
Path	`/v4/sports/{sport}/participants`

Parameters

Name	Location	Type	Required
`sport`	path	string	Yes

Using this endpoint in a workflow

Add an API Call node to your workflow.
Pick your The Odds API connection from the Connection dropdown.
In the Operation dropdown, select odds.listParticipants.
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 The Odds API API reference.

GET /v4/historical/sports/{sport}/odds/

Historical odds

Detail	Value
Operation ID	`odds.getHistoricalOdds`
Method	`GET`
Path	`/v4/historical/sports/{sport}/odds/`

Parameters

Name	Location	Type	Required
`sport`	path	string	Yes

Using this endpoint in a workflow

Add an API Call node to your workflow.
Pick your The Odds API connection from the Connection dropdown.
In the Operation dropdown, select odds.getHistoricalOdds.
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 The Odds API API reference.

GET /v4/historical/sports/{sport}/events

Historical events

Detail	Value
Operation ID	`odds.getHistoricalEvents`
Method	`GET`
Path	`/v4/historical/sports/{sport}/events`

Parameters

Name	Location	Type	Required
`sport`	path	string	Yes

Using this endpoint in a workflow

Add an API Call node to your workflow.
Pick your The Odds API connection from the Connection dropdown.
In the Operation dropdown, select odds.getHistoricalEvents.
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 The Odds API API reference.

The Odds API ​

Using The Odds API in a workflow ​

Available endpoints ​

GET /v4/sports/ ​

Parameters ​

Using this endpoint in a workflow ​

What it returns ​

GET /v4/sports/{sport}/odds/ ​

Parameters ​

Using this endpoint in a workflow ​

What it returns ​

GET /v4/sports/{sport}/scores/ ​

Parameters ​

Using this endpoint in a workflow ​

What it returns ​

GET /v4/sports/{sport}/events ​

Parameters ​

Using this endpoint in a workflow ​

What it returns ​

GET /v4/sports/{sport}/events/{eventId}/odds ​

Parameters ​

Using this endpoint in a workflow ​

What it returns ​

GET /v4/sports/{sport}/participants ​

Parameters ​

Using this endpoint in a workflow ​

What it returns ​

GET /v4/historical/sports/{sport}/odds/ ​

Parameters ​

Using this endpoint in a workflow ​

What it returns ​

GET /v4/historical/sports/{sport}/events ​

Parameters ​

Using this endpoint in a workflow ​

What it returns ​

The Odds API

Using The Odds API in a workflow

Available endpoints

GET /v4/sports/

Parameters

Using this endpoint in a workflow

What it returns

GET /v4/sports/{sport}/odds/

Parameters

Using this endpoint in a workflow

What it returns

GET /v4/sports/{sport}/scores/

Parameters

Using this endpoint in a workflow

What it returns

GET /v4/sports/{sport}/events

Parameters

Using this endpoint in a workflow

What it returns

GET /v4/sports/{sport}/events/{eventId}/odds

Parameters

Using this endpoint in a workflow

What it returns

GET /v4/sports/{sport}/participants

Parameters

Using this endpoint in a workflow

What it returns

GET /v4/historical/sports/{sport}/odds/

Parameters

Using this endpoint in a workflow

What it returns

GET /v4/historical/sports/{sport}/events

Parameters

Using this endpoint in a workflow

What it returns