Sports and path prefixes

Every path starts with a sport prefix. Use one of the eleven below, exactly as written.

GET https://sports.highlightly.net/{sport}/matches

Sport prefixes

Prefix Documented by
/football Football API
/american-football NFL & NCAAF API
/nba NBA & NCAAB API
/baseball MLB & NCAA API
/nhl NHL & NCAAH API
/cricket Cricket API
/basketball Basketball API
/hockey Hockey API
/rugby Rugby API
/volleyball Volleyball API
/handball Handball API

Which basketball or hockey prefix to use

Basketball and hockey each have two prefixes, covering different competitions.

If you want Use
The NBA and 35+ NCAA Division I conferences /nba
340+ basketball leagues worldwide /basketball
The NHL and 10+ NCAA Division I conferences /nhl
170+ hockey leagues in 30+ countries /hockey

Pick the one whose competitions you cover.

/american-football covers the NFL and NCAA FBS, and /baseball covers MLB and NCAA Division I. Each of those sports has one prefix.

Putting a path together

Take the endpoint from the sport's own documentation and add the prefix.

Sport's own API Through All Sports
https://soccer.highlightly.net/matches https://sports.highlightly.net/football/matches
https://american-football.highlightly.net/standings https://sports.highlightly.net/american-football/standings
https://cricket.highlightly.net/players/{id} https://sports.highlightly.net/cricket/players/{id}

Parameters and the response do not change. Only the base URL and the prefix do, and on RapidAPI the key and the x-rapidapi-host header too, which Authentication covers.

Which endpoints exist for a given sport is in endpoint coverage.