Goalise
Get StartedAPI ReferenceUse CasesChangelogSupport
Get StartedAPI ReferenceUse CasesChangelogSupport

Use Cases for Goalise Football API v3

The Goalise Football API provides a wide range of football data-live scores, team and player stats, match predictions, and more. Here are 7 practical use cases that demonstrate how you can integrate the API into your projects.

Every example below answers inside the v3 envelope - read the payload from response, and pagination when the endpoint returns a list.

1. Real-Time Match Data

Scenario:
Develop a live scoreboard for displaying ongoing football matches.

How to Use:

  • Endpoint: GET /matches
  • Parameters: Optional filters like league_id, team_id, or date; live=all for everything in progress; timezone to render start_date in the reader's zone

Example Request:

curl -X GET "https://api.goalise.com/api/v3/matches?league_id=39&season=2024" \
  -H "Authorization: Bearer YOUR_API_TOKEN"

Use Case:
Integrate this data into a web or mobile app to show users up-to-the-minute match updates. Both teams and the venue come back as objects, so a fixture row renders from a single call. Add ?expand=events,statistics when the screen needs what happened inside the match - check has_events and has_statistics first.

2. Team and Player Statistics Dashboard

Scenario:
Display detailed team and player performance statistics.

How to Use:

  • Endpoints:
    • GET /team-statistics
    • GET /player-statistics

Example Request:

curl -X GET "https://api.goalise.com/api/v3/team-statistics?team_id=1&league_id=61&season=2023" \
  -H "Authorization: Bearer YOUR_API_TOKEN"

Use Case:
Provide fans with insights into team strengths, weaknesses, and player form throughout the season. /player-statistics is paginated in v3, so walk pagination.page_count when you render a whole squad.

3. League Standings and Fixtures Viewer

Scenario:
Let users track their favorite leagues-standings and upcoming fixtures.

How to Use:

  • Endpoints:
    • GET /league-standing?league_id=xxx&season=yyyy
    • GET /matches?league_id=xxx&season=yyyy

Example Request:

curl -X GET "https://api.goalise.com/api/v3/league-standing?league_id=618&season=2023" \
  -H "Authorization: Bearer YOUR_API_TOKEN"

Use Case:
Embed a league table or fixture list into your site or application to increase user engagement. Each row already names its team; ?expand=team raises those references to full team objects if the table shows more than a crest and a name.

4. Match Prediction Feature

Scenario:
Offer match predictions for upcoming matches.

How to Use:

  • Endpoint: GET /predictions
  • Parameters: match_id (required)

Example Request:

curl -X GET "https://api.goalise.com/api/v3/predictions?match_id=43212" \
  -H "Authorization: Bearer YOUR_API_TOKEN"

Use Case:
Display probability-based predictions to add value for fantasy football players or betting platforms. Every team named in the call - the favourite and the two form blocks included - is an object, so you can render the comparison without resolving provider ids yourself.

5. Historical Match Data between 2 teams (Head to head)

Scenario:
Analyze or visualize historical match results and statistics between 2 teams.

How to Use:

  • Endpoint: GET /head-to-head
  • Parameters: team_id1, team_id2, optional league_id, season, timezone, page

Example Request:

curl -X GET "https://api.goalise.com/api/v3/head-to-head?team_id1=33&team_id2=44" \
  -H "Authorization: Bearer YOUR_API_TOKEN"

Use Case:
Pull historical matches between 2 teams for data analytics projects, blog content, or performance evaluation. The answer is paginated in v3, so a long rivalry arrives in pages rather than one oversized payload.

6. Match Highlights Feed

Scenario:
Show video highlights next to a finished match, or build a clips feed for a league.

How to Use:

  • Endpoint: GET /highlights
  • Parameters: at least one of match_id, league_id, team_id, date_from / date_to; optional category, type and page

Example Request:

curl -X GET "https://api.goalise.com/api/v3/highlights?match_id=1035037" \
  -H "Authorization: Bearer YOUR_API_TOKEN"

Use Case:
Embed official clips with the embedUrl of each item to keep users on your match pages after the final whistle. The fixture inside each clip is a full match object with both teams, and the id filters come back resolved in meta.filters. Every clip carries the provider's geo rules in restriction, so check allowedCountries and blockedCountries against your viewer before playing it. Clips are VERIFIED by default; request type=UNVERIFIED only if you can handle user uploads that have no embed url.

7. Name Search and Autocomplete

Scenario:
Let users type "Arsenal" instead of hunting for a numeric ID.

How to Use:

  • Endpoint: GET /search
  • Parameters: query (required, 2 characters or more), optional type and limit

Example Request:

curl -X GET "https://api.goalise.com/api/v3/search?query=arsenal&type=team&limit=5" \
  -H "Authorization: Bearer YOUR_API_TOKEN"

Use Case:
Power a search box or autocomplete, then feed the returned id straight into /matches, /team-statistics or /highlights. Omit type to search teams, leagues and players at once - handy for a single global search field.

Bonus: Watching Your Allowance

Scenario:
Show a reader how much of their plan is left, or back off before you hit a 429.

How to Use:

  • Endpoint: GET /quota

Example Request:

curl -X GET "https://api.goalise.com/api/v3/quota" \
  -H "Authorization: Bearer YOUR_API_TOKEN"

Use Case:
Every response already carries the three windows in its X-Rate-*-minute/hour/day headers, so read those in normal operation. /quota is for the moments when you need the numbers without making a call that spends one.

Want more ideas or help with implementation? Feel free to reach out!