OneHazel Docs

Appearance

For LLMsView as Markdown·

API-Football ​

Comprehensive football data with fixtures, standings, odds, predictions, and player stats.

DetailValue
CategoryiGaming
Base URLhttps://v3.football.api-sports.io
AuthenticationAPI Key
Endpoints12
Connector keyapi-football

Using API-Football in a workflow ​

  1. Go to Connections and click New Connection.
  2. Pick API-Football 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 ​

EndpointSummary
GET /countriesList countries
GET /leaguesList leagues
GET /teamsGet teams
GET /standingsLeague standings
GET /fixturesGet fixtures
GET /fixtures/eventsMatch events (goals, cards)
GET /fixtures/statisticsMatch statistics
GET /fixtures/lineupsMatch lineups
GET /playersPlayer statistics
GET /oddsBetting odds
GET /predictionsMatch predictions
GET /injuriesPlayer injuries

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

GET /countries ​

List countries

DetailValue
Operation IDfootball.listCountries
MethodGET
Path/countries

Parameters ​

No parameters.

Using this endpoint in a workflow ​

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

GET /leagues ​

List leagues

DetailValue
Operation IDfootball.listLeagues
MethodGET
Path/leagues

Parameters ​

No parameters.

Using this endpoint in a workflow ​

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

GET /teams ​

Get teams

DetailValue
Operation IDfootball.getTeams
MethodGET
Path/teams

Parameters ​

No parameters.

Using this endpoint in a workflow ​

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

GET /standings ​

League standings

DetailValue
Operation IDfootball.getStandings
MethodGET
Path/standings

Parameters ​

No parameters.

Using this endpoint in a workflow ​

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

GET /fixtures ​

Get fixtures

DetailValue
Operation IDfootball.getFixtures
MethodGET
Path/fixtures

Parameters ​

No parameters.

Using this endpoint in a workflow ​

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

GET /fixtures/events ​

Match events (goals, cards)

DetailValue
Operation IDfootball.getMatchEvents
MethodGET
Path/fixtures/events

Parameters ​

No parameters.

Using this endpoint in a workflow ​

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

GET /fixtures/statistics ​

Match statistics

DetailValue
Operation IDfootball.getMatchStatistics
MethodGET
Path/fixtures/statistics

Parameters ​

No parameters.

Using this endpoint in a workflow ​

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

GET /fixtures/lineups ​

Match lineups

DetailValue
Operation IDfootball.getMatchLineups
MethodGET
Path/fixtures/lineups

Parameters ​

No parameters.

Using this endpoint in a workflow ​

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

GET /players ​

Player statistics

DetailValue
Operation IDfootball.getPlayerStatistics
MethodGET
Path/players

Parameters ​

No parameters.

Using this endpoint in a workflow ​

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

GET /odds ​

Betting odds

DetailValue
Operation IDfootball.getBettingOdds
MethodGET
Path/odds

Parameters ​

No parameters.

Using this endpoint in a workflow ​

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

GET /predictions ​

Match predictions

DetailValue
Operation IDfootball.getMatchPredictions
MethodGET
Path/predictions

Parameters ​

No parameters.

Using this endpoint in a workflow ​

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

GET /injuries ​

Player injuries

DetailValue
Operation IDfootball.getPlayerInjuries
MethodGET
Path/injuries

Parameters ​

No parameters.

Using this endpoint in a workflow ​

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