18, 50, 80, 100 or 150 in a resizable image path.See the same league at every size
The example uses the Premier League (league_id=583), the competition used
throughout this documentation.
50 px
80 px
100 px
150 pxURL patterns
20https://cdn.soccersapi.com/images/soccer/teams/{size}/{team_id}.png583https://cdn.soccersapi.com/images/soccer/leagues/{size}/{league_id}.png311https://cdn.soccersapi.com/images/soccer/players/{size}/{player_id}.pngOther image fields can use a fixed path, for example country flags, bookmakers, venues or TV channels. For those fields, treat the URL returned by the API as authoritative. Do not insert a size segment when the returned path does not already contain one.
Build another size
Start from the URL returned by the API:
https://cdn.soccersapi.com/images/soccer/leagues/80/583.png
Replace only the size segment:
https://cdn.soccersapi.com/images/soccer/leagues/150/583.png
Which endpoints return images
Images appear in catalogue profiles and in related entities embedded into match
responses. Common sources include leagues, teams, players, coaches,
referees, venues, bookmakers, broadcast, countries, fixtures and
livescores.
Keep a neutral fallback in the client. A valid entity can have no uploaded artwork yet, and an older fixed image URL should not be rewritten into a resizable path unless its structure supports it.