Appearance
PandaScore
Esports data API with live matches, leagues, tournaments, and real-time odds.
| Detail | Value |
|---|---|
| Category | iGaming |
| Base URL | https://api.pandascore.co |
| Authentication | Bearer Token |
| Endpoints | 10 |
| Connector key | pandascore |
Using PandaScore in a workflow
- Go to Connections and click New Connection.
- Pick PandaScore 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 /leagues | List leagues |
GET /leagues/{id}/matches | League matches |
GET /leagues/{id}/tournaments | League tournaments |
GET /matches | All matches |
GET /matches/running | Live matches |
GET /matches/upcoming | Upcoming matches |
GET /matches/past | Completed matches |
GET /tournaments/{id}/rosters | Tournament rosters |
GET /lives | Real-time live data |
GET /incidents | Data change feed |
Each endpoint is documented in full below. Use the outline on the right to jump to one.
GET /leagues
List leagues
| Detail | Value |
|---|---|
| Operation ID | esports.listLeagues |
| Method | GET |
| Path | /leagues |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your PandaScore connection from the Connection dropdown.
- In the Operation dropdown, select
esports.listLeagues. - 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 PandaScore API reference.
GET /leagues/{id}/matches
League matches
| Detail | Value |
|---|---|
| Operation ID | esports.getLeagueMatches |
| Method | GET |
| Path | /leagues/{id}/matches |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
id | path | string | Yes |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your PandaScore connection from the Connection dropdown.
- In the Operation dropdown, select
esports.getLeagueMatches. - 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 PandaScore API reference.
GET /leagues/{id}/tournaments
League tournaments
| Detail | Value |
|---|---|
| Operation ID | esports.getLeagueTournaments |
| Method | GET |
| Path | /leagues/{id}/tournaments |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
id | path | string | Yes |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your PandaScore connection from the Connection dropdown.
- In the Operation dropdown, select
esports.getLeagueTournaments. - 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 PandaScore API reference.
GET /matches
All matches
| Detail | Value |
|---|---|
| Operation ID | esports.listMatches |
| Method | GET |
| Path | /matches |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your PandaScore connection from the Connection dropdown.
- In the Operation dropdown, select
esports.listMatches. - 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 PandaScore API reference.
GET /matches/running
Live matches
| Detail | Value |
|---|---|
| Operation ID | esports.getLiveMatches |
| Method | GET |
| Path | /matches/running |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your PandaScore connection from the Connection dropdown.
- In the Operation dropdown, select
esports.getLiveMatches. - 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 PandaScore API reference.
GET /matches/upcoming
Upcoming matches
| Detail | Value |
|---|---|
| Operation ID | esports.getUpcomingMatches |
| Method | GET |
| Path | /matches/upcoming |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your PandaScore connection from the Connection dropdown.
- In the Operation dropdown, select
esports.getUpcomingMatches. - 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 PandaScore API reference.
GET /matches/past
Completed matches
| Detail | Value |
|---|---|
| Operation ID | esports.getPastMatches |
| Method | GET |
| Path | /matches/past |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your PandaScore connection from the Connection dropdown.
- In the Operation dropdown, select
esports.getPastMatches. - 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 PandaScore API reference.
GET /tournaments/{id}/rosters
Tournament rosters
| Detail | Value |
|---|---|
| Operation ID | esports.getTournamentRosters |
| Method | GET |
| Path | /tournaments/{id}/rosters |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
id | path | string | Yes |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your PandaScore connection from the Connection dropdown.
- In the Operation dropdown, select
esports.getTournamentRosters. - 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 PandaScore API reference.
GET /lives
Real-time live data
| Detail | Value |
|---|---|
| Operation ID | esports.getLiveData |
| Method | GET |
| Path | /lives |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your PandaScore connection from the Connection dropdown.
- In the Operation dropdown, select
esports.getLiveData. - 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 PandaScore API reference.
GET /incidents
Data change feed
| Detail | Value |
|---|---|
| Operation ID | esports.getIncidents |
| Method | GET |
| Path | /incidents |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your PandaScore connection from the Connection dropdown.
- In the Operation dropdown, select
esports.getIncidents. - 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 PandaScore API reference.