Skip to main content
GET
/
games
/
fixtures
Upcoming Games
curl --request GET \
  --url https://v1.basketball.sportsapipro.com/games/fixtures \
  --header 'x-api-key: <api-key>'

​
Overview

To fetch detailed information about a specific competitor (team/club), use the fixtures or results endpoints with the competitor ID. The /stats endpoint may return empty data for some competitors, so using fixtures/results endpoints is more reliable.
The /stats endpoint may return empty data for some competitors. Always use the fixtures or results endpoints as the primary source for competitor details, with stats as supplementary data.

​
Step 1: Fetch Competitor Data via Fixtures

GET https://v1.football.sportsapipro.com/games/fixtures?competitors={competitorId}
This returns upcoming matches for the competitor along with competitor metadata in the competitors array.

​
Step 2: Fallback to Results if No Fixtures

If the competitor has no upcoming fixtures, use the results endpoint: 
GET https://v1.football.sportsapipro.com/games/results?competitors={competitorId}

​
Parameters

ParameterTypeDescription
competitorsnumberCompetitor ID to fetch details for
showOddsbooleanInclude betting odds (optional)
timezoneNamestringTimezone for date/time values (auto-resolved, or specify e.g., America/New_York)
All startTime fields in game data use ISO 8601 format with a dynamic timezone offset based on the resolved or specified timezone.

​
Request

curl -X GET "https://v1.football.sportsapipro.com/games/fixtures?competitors=2112" \
  -H "x-api-key: YOUR_API_KEY"

​
Response

The competitors array in the response contains competitor details: 
{
  "competitors": [
    {
      "id": 2112,
      "countryId": 190,
      "sportId": 1,
      "name": "Slovan Bratislava",
      "longName": "ŠK Slovan Bratislava",
      "shortName": "Sl. Bratislava",
      "symbolicName": "SLO",
      "nameForURL": "slovan-bratislava",
      "type": 1,
      "popularityRank": 8234,
      "imageVersion": 2,
      "color": "#0066CC",
      "awayColor": "#FFFFFF",
      "mainCompetitionId": 128,
      "hasSquad": true,
      "hasTransfers": false
    }
  ],
  "games": [
    // Array of upcoming fixtures
  ]
}

​
Important Notes

  1. Always filter by ID: The competitors array may contain additional related teams (opponents). Always filter by the specific competitor ID you’re looking for.
  2. Use fixtures first: Fixtures endpoint is preferred as it includes upcoming matches. Fall back to results if no fixtures are available.
  3. Country lookup: Use the countryId to look up the country name from the /countries endpoint or the countries array in the response.

​
Competitor Fields

FieldTypeDescription
idnumberUnique competitor identifier
countryIdnumberID of the country the competitor belongs to
sportIdnumberID of the sport (1 = Football)
namestringFull competitor name
longNamestringExtended official name
shortNamestringAbbreviated display name
symbolicNamestring3-letter code (e.g., “SLO”, “BAR”)
nameForURLstringURL-friendly name for SEO
typenumberCompetitor type (1 = club, 2 = national team)
popularityRanknumberPopularity score (higher = more popular)
imageVersionnumberVersion number for logo assets
colorstringPrimary brand color in hex format
awayColorstringAway kit/secondary color in hex format
mainCompetitionIdnumberPrimary competition ID
hasSquadbooleanWhether squad data is available
hasTransfersbooleanWhether transfer data is available

​
SEO-Friendly URLs

For SEO purposes, use the nameForURL field to construct URLs: 
/sports/competitor/{nameForURL}-{id}
Example: 
/sports/competitor/slovan-bratislava-2112
The route extracts the ID from the last segment of the slug (after the final hyphen) to fetch the competitor data.

Authorizations

​
x-api-key
string
header
required

Your SportsAPI Pro API key

Query Parameters

​
competitions
integer

Filter by competition ID

Example:

132

​
date
string<date>

Filter by date (YYYY-MM-DD)

Example:

"2026-01-26"

Response

200

Fixtures retrieved successfully