Genius Sports

Official sports data platform — fixtures, results, and in-running live event feeds across football, basketball, volleyball, and more. OAuth2 + subscription key.

Detail	Value
Category	iGaming
Base URL	https://fixtures.api.geniussports.com
Authentication	OAuth2 Client Credentials
Endpoints	6
Connector key	genius-sports

Using Genius Sports in a workflow

1. Go to Connections and click New Connection.
2. Pick Genius Sports 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 /v2/sports	List sports covered by Fixtures API
GET /v2/competitions	List competitions
GET /v2/seasons	List seasons
GET /v2/fixtures	List fixtures (filterable by sport, competition, season, date range)
GET /v2/fixtures/{fixtureId}	Get a single fixture by ID
GET /v2/persons	List persons (players/officials)

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

GET /v2/sports

List sports covered by Fixtures API

Detail	Value
Operation ID	fixtures.listSports
Method	GET
Path	/v2/sports

Parameters

No parameters.

Using this endpoint in a workflow

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

GET /v2/competitions

List competitions

Detail	Value
Operation ID	fixtures.listCompetitions
Method	GET
Path	/v2/competitions

Parameters

Name	Location	Type	Required
sportId	query	string	No

Using this endpoint in a workflow

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

GET /v2/seasons

List seasons

Detail	Value
Operation ID	fixtures.listSeasons
Method	GET
Path	/v2/seasons

Parameters

Name	Location	Type	Required
competitionId	query	string	No

Using this endpoint in a workflow

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

GET /v2/fixtures

List fixtures (filterable by sport, competition, season, date range)

Detail	Value
Operation ID	fixtures.listFixtures
Method	GET
Path	/v2/fixtures

Parameters

No parameters.

Using this endpoint in a workflow

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

GET /v2/fixtures/{fixtureId}

Get a single fixture by ID

Detail	Value
Operation ID	fixtures.getFixture
Method	GET
Path	/v2/fixtures/{fixtureId}

Parameters

Name	Location	Type	Required
fixtureId	path	string	Yes

Using this endpoint in a workflow

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

GET /v2/persons

List persons (players/officials)

Detail	Value
Operation ID	fixtures.listPersons
Method	GET
Path	/v2/persons

Parameters

Name	Location	Type	Required
competitionId	query	string	No

Using this endpoint in a workflow

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