Skip to main content
New API version, base URL https://data.anysport.io/v1/soccer

Step 1 — Get an API Key

  1. Go to dashboard.anysport.io and sign up for an account.
  2. After verifying your email, you’ll be automatically redirected to the dashboard.
  3. Your API key is shown on the dashboard home page — copy it.

Step 2 — Authentication method

Pass the API key in the HTTP request header apikey. This is the only supported method — passing the key as a query parameter is not supported, and the legacy X-API-Key header name is no longer used. See Authentication for details.

Step 3 — Make your first request

query today’s fixtures:
Example response Using the standard response envelope success / data / meta / traceId; full field descriptions in Matches:

Step 4 — Discover in-progress matches and get live scores

The new /livescore endpoint queries a single match by match_id, so you first need to “discover” a match before fetching its score — this is a two-step process: 1) Query today’s fixtures using relative dates, and check the status value to determine which matches are in progress (see Recent Matches for details):
A status of a plain numeric minute value or HT means the match is in progress; note down that match’s match_id. 2) Use the retrieved match_id to query the live score (see Live Score for details):
To check whether a match has finished, always use phase == "finished" (this endpoint does not return a status field). For more granular, event-by-event data (goalscorers, yellow cards, corners, etc.), use Live Match Stats instead.

Next steps

  • For the complete authentication rules (header name, error codes), see Authentication.
  • Check the Endpoint Index: all 19 endpoints are organized by category — “Base Data → Fixtures & Matchups → Live Feeds → System/Metadata” — with a recommended integration order.
  • Need multi-language display? First call Localization to get the currently available lang values, then pass the lang parameter to each endpoint.
  • Want to integrate odds markets? Use Pre-Match Odds for pre-match odds and In-play Odds for live in-play markets.
  • For cross-cutting rules such as common error codes, ID prefix conventions, and *_label localization field rules, see the “Common Reference” section at the bottom of the index page.