Pinnacle

Sports betting API for iGaming with fixtures, odds, lines, and parlay pricing.

Detail	Value
Category	iGaming
Base URL	https://api.pinnacle.com
Authentication	Bearer Token
Endpoints	10
Connector key	pinnacle-api

Using Pinnacle in a workflow

1. Go to Connections and click New Connection.
2. Pick Pinnacle 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 /v1/sports	List sports
GET /v1/fixtures	Get fixtures
GET /v1/fixtures/special	Special fixtures (props)
GET /v1/odds	Current odds
GET /v1/odds/special	Special odds
GET /v1/odds/parlay	Parlay odds
GET /v1/line	Check line price
GET /v1/line/special	Special line
GET /v1/line/parlay	Parlay line
GET /v2/odds	Odds v2

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

GET /v1/sports

List sports

Detail	Value
Operation ID	igaming.listSports
Method	GET
Path	/v1/sports

Parameters

No parameters.

Using this endpoint in a workflow

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

GET /v1/fixtures

Get fixtures

Detail	Value
Operation ID	igaming.getFixtures
Method	GET
Path	/v1/fixtures

Parameters

Name	Location	Type	Required
sportId	query	integer	No
leagueIds	query	string	No

Using this endpoint in a workflow

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

GET /v1/fixtures/special

Special fixtures (props)

Detail	Value
Operation ID	igaming.getSpecialFixtures
Method	GET
Path	/v1/fixtures/special

Parameters

Name	Location	Type	Required
sportId	query	integer	No

Using this endpoint in a workflow

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

GET /v1/odds

Current odds

Detail	Value
Operation ID	igaming.getOdds
Method	GET
Path	/v1/odds

Parameters

Name	Location	Type	Required
sportId	query	integer	No
leagueIds	query	string	No

Using this endpoint in a workflow

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

GET /v1/odds/special

Special odds

Detail	Value
Operation ID	igaming.getSpecialOdds
Method	GET
Path	/v1/odds/special

Parameters

Name	Location	Type	Required
sportId	query	integer	No

Using this endpoint in a workflow

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

GET /v1/odds/parlay

Parlay odds

Detail	Value
Operation ID	igaming.getParlayOdds
Method	GET
Path	/v1/odds/parlay

Parameters

Name	Location	Type	Required
sportId	query	integer	No

Using this endpoint in a workflow

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

GET /v1/line

Check line price

Detail	Value
Operation ID	igaming.getLine
Method	GET
Path	/v1/line

Parameters

Name	Location	Type	Required
sportId	query	integer	No
eventId	query	integer	No
periodNumber	query	integer	No

Using this endpoint in a workflow

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

GET /v1/line/special

Special line

Detail	Value
Operation ID	igaming.getSpecialLine
Method	GET
Path	/v1/line/special

Parameters

Name	Location	Type	Required
specialId	query	integer	No

Using this endpoint in a workflow

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

GET /v1/line/parlay

Parlay line

Detail	Value
Operation ID	igaming.getParlayLine
Method	GET
Path	/v1/line/parlay

Parameters

No parameters.

Using this endpoint in a workflow

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

GET /v2/odds

Odds v2

Detail	Value
Operation ID	igaming.getOddsV2
Method	GET
Path	/v2/odds

Parameters

Name	Location	Type	Required
sportId	query	integer	No
leagueIds	query	string	No

Using this endpoint in a workflow

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