Betfair

Betting exchange API for market data, live prices, order placement, and P&L tracking.

Detail	Value
Category	iGaming
Base URL	https://api.betfair.com/exchange
Authentication	API Key
Endpoints	10
Connector key	betfair

Using Betfair in a workflow

1. Go to Connections and click New Connection.
2. Pick Betfair 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
POST /betting/rest/v1.0/listEventTypes/	List event types (sports)
POST /betting/rest/v1.0/listEvents/	List events
POST /betting/rest/v1.0/listCompetitions/	List competitions
POST /betting/rest/v1.0/listMarketCatalogue/	Market catalogue
POST /betting/rest/v1.0/listMarketBook/	Live market prices
POST /betting/rest/v1.0/placeOrders/	Place bets
POST /betting/rest/v1.0/cancelOrders/	Cancel bets
POST /betting/rest/v1.0/listCurrentOrders/	Current orders
POST /betting/rest/v1.0/listClearedOrders/	Settled orders
POST /betting/rest/v1.0/listMarketProfitAndLoss/	P&L

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

POST /betting/rest/v1.0/listEventTypes/

List event types (sports)

Detail	Value
Operation ID	betting.listEventTypes
Method	POST
Path	/betting/rest/v1.0/listEventTypes/

Parameters

No parameters.

Request Body

Field	Type
filter	object

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Betfair connection from the Connection dropdown.
3. In the Operation dropdown, select betting.listEventTypes.
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 Betfair API reference.

POST /betting/rest/v1.0/listEvents/

List events

Detail	Value
Operation ID	betting.listEvents
Method	POST
Path	/betting/rest/v1.0/listEvents/

Parameters

No parameters.

Request Body

Field	Type
filter	object

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Betfair connection from the Connection dropdown.
3. In the Operation dropdown, select betting.listEvents.
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 Betfair API reference.

POST /betting/rest/v1.0/listCompetitions/

List competitions

Detail	Value
Operation ID	betting.listCompetitions
Method	POST
Path	/betting/rest/v1.0/listCompetitions/

Parameters

No parameters.

Request Body

Field	Type
filter	object

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Betfair connection from the Connection dropdown.
3. In the Operation dropdown, select betting.listCompetitions.
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 Betfair API reference.

POST /betting/rest/v1.0/listMarketCatalogue/

Market catalogue

Detail	Value
Operation ID	betting.listMarketCatalogue
Method	POST
Path	/betting/rest/v1.0/listMarketCatalogue/

Parameters

No parameters.

Request Body

Field	Type
filter	object
maxResults	integer
marketProjection	array

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Betfair connection from the Connection dropdown.
3. In the Operation dropdown, select betting.listMarketCatalogue.
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 Betfair API reference.

POST /betting/rest/v1.0/listMarketBook/

Live market prices

Detail	Value
Operation ID	betting.listMarketBook
Method	POST
Path	/betting/rest/v1.0/listMarketBook/

Parameters

No parameters.

Request Body

Field	Type
marketIds	array
priceProjection	object

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Betfair connection from the Connection dropdown.
3. In the Operation dropdown, select betting.listMarketBook.
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 Betfair API reference.

POST /betting/rest/v1.0/placeOrders/

Place bets

Detail	Value
Operation ID	betting.placeOrders
Method	POST
Path	/betting/rest/v1.0/placeOrders/

Parameters

No parameters.

Request Body

Field	Type
marketId	string
instructions	array

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Betfair connection from the Connection dropdown.
3. In the Operation dropdown, select betting.placeOrders.
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 Betfair API reference.

POST /betting/rest/v1.0/cancelOrders/

Cancel bets

Detail	Value
Operation ID	betting.cancelOrders
Method	POST
Path	/betting/rest/v1.0/cancelOrders/

Parameters

No parameters.

Request Body

Field	Type
marketId	string
instructions	array

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Betfair connection from the Connection dropdown.
3. In the Operation dropdown, select betting.cancelOrders.
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 Betfair API reference.

POST /betting/rest/v1.0/listCurrentOrders/

Current orders

Detail	Value
Operation ID	betting.listCurrentOrders
Method	POST
Path	/betting/rest/v1.0/listCurrentOrders/

Parameters

No parameters.

Request Body

Field	Type
orderBy	string

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Betfair connection from the Connection dropdown.
3. In the Operation dropdown, select betting.listCurrentOrders.
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 Betfair API reference.

POST /betting/rest/v1.0/listClearedOrders/

Settled orders

Detail	Value
Operation ID	betting.listClearedOrders
Method	POST
Path	/betting/rest/v1.0/listClearedOrders/

Parameters

No parameters.

Request Body

Field	Type
betStatus	string
settledDateRange	object

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Betfair connection from the Connection dropdown.
3. In the Operation dropdown, select betting.listClearedOrders.
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 Betfair API reference.

POST /betting/rest/v1.0/listMarketProfitAndLoss/

P&L

Detail	Value
Operation ID	betting.listMarketProfitAndLoss
Method	POST
Path	/betting/rest/v1.0/listMarketProfitAndLoss/

Parameters

No parameters.

Request Body

Field	Type
marketIds	array

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Betfair connection from the Connection dropdown.
3. In the Operation dropdown, select betting.listMarketProfitAndLoss.
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 Betfair API reference.