Recent Matches - AnySport

The relative-date version of Matches: use from_days/to_days to express “how many days from today” instead of requiring the client to calculate absolute dates yourself — ideal for scenarios like “fixtures for the next week” or “recent results” that use a relative time window. The output field structure is identical to endpoint 10. This is also the recommended entry point for discovering “not started/in progress” matches and obtaining a match_id for use with Live Score, Live Match Stats, and Live Odds.

Endpoint

GET /v1/soccer/matches/window

Queries matches within from_days to to_days days from today (UTC dates, inclusive of both ends), saving the client from calculating dates itself: from_days=0&to_days=7 = the next week, from_days=-3&to_days=0 = the last 3 days (including today). This is also the recommended entry point for discovering “not started / in progress” matches (interpret the status form after fetching).

Parameters

Parameter	Type	Required	Default	Description
`from_days`	int	No	0	Window start (day offset relative to today; can be negative = past)
`to_days`	int	No	7	Window end (day offset relative to today); must be ≥ `from_days`, maximum span 90 days, otherwise 400
`league_id`	string	No		Filter by league (`asl_`); since a date constraint is already present, `season` is not required
`team_id`	string	No		Filter by team (`ast_`)
`status`	string	No		Status filter (same rules as fixtures list; `FT` excludes matches decided by extra time/penalties)
`lang`	string	No	en	`en` / `zh-CN`; invalid values silently fall back to the default language — see `GET /languages` (19) for available values
`page` / `limit`	int	No	1 / 50	Pagination, limit range 1–100

Response fields (data: array)

Identical to the fixtures list (GET /matches) (internally, this is just a from/to query on /matches):

Field	Type	Description
`match_id`	string	Match ID (`as_` prefix, consistent across all endpoints)
`date`	string	Kickoff date `YYYY-MM-DD` (UTC, ISO)
`time`	string	Kickoff time `HH:mm` (UTC)
`status`	string	Textual status (`FT`/`AET`/`Not Started`…) / `HH:MM` kickoff time / plain numeric minute, may be an empty string
`status_label`	string	Localized text for the match status (e.g. `完场` for zh-CN); the original `status` value is unchanged, sent when `lang` is a non-default language and localized text exists for that value. Not every value has localized text; when there is no corresponding text this field is omitted, so clients must handle that gracefully (`HH:MM`/plain numeric minute forms never have a label)
`league`	string	League name
`league_id`	string	League ID (`asl_`)
`season`	string	Season
`home`	object	Home team `{ name, team_id }`
`away`	object	Away team `{ name, team_id }`
`ht_score`	string	Half-time score (returned for completed matches, no spaces)
`ft_score`	string	Regular 90-minute score (returned for completed matches)
`et_score`	string	Cumulative score at the end of extra time (returned only for matches that went to extra time)
`penalty_score`	string	Penalty shootout score (returned only for matches decided by penalties)
`venue`	string	Venue (may be empty)

*_label convention: when lang is a non-default language, status retains its original value, and a parallel localized label status_label is added (only textual statuses can have localized text). Not every value has localized text; when there is no corresponding text this field is omitted, so clients must handle that gracefully. Team names/league names (home/away/league) are not yet localized by lang.

Interpreting the status form: not started = HH:MM / Not Started / TBA / empty string; in progress = plain numeric minute / HT (plus the less common ET/P/Break Time). Any match_id you obtain can be used directly with livescore and situation.

Enum reference

The status string (three forms): 1). Textual status:

Value	Meaning
`Not Started`	Not started: not yet begun
`TBA`	Not started: time to be announced
“ (empty string)	Not started: unscheduled/unmarked, treated as not started
`HT`	In progress: half-time break
`ET`	In progress: extra time in progress (included in the official value list, low frequency in historical data)
`P`	In progress: penalty shootout in progress (included in the official value list, low frequency in historical data)
`Break Time`	In progress: break between extra-time halves, or between extra time and the penalty shootout (included in the official value list)
`FT`	Finished: end of regulation time (Full Time, most common)
`AET`	Finished: ended after extra time (After Extra Time)
`Pen.`	Finished: decided by penalty shootout (Penalties)
`Awarded`	Finished: awarded loss/win (technical loss — forfeiture, eligibility issues, or other administrative rulings)
`WO`	Finished: forfeit/win by default (Walkover, included in the official value list, low frequency in historical data)
`Postp.`	Postponed: postponed
`Delayed`	Postponed: kickoff delayed (included in the official value list, low frequency in historical data)
`Cancl.` / `Cancelled`	Cancelled: cancelled
`Abandoned` / `Aban.`	Interrupted: match abandoned
`Susp.`	Interrupted: suspended (interrupted after kickoff, included in the official value list, low frequency in historical data)
`Int.`	Interrupted: interrupted (included in the official value list, low frequency in historical data)

2). HH:MM form (e.g. 15:00, 19:45): not started, the value is the UTC kickoff time (matches the time field). 3). Plain numeric form (e.g. 9, 45, 88): in progress, the value is the current match minute.

Request examples

# World Cup fixtures for the next week
GET /v1/soccer/matches/window?from_days=0&to_days=7&league_id=asl_62db9cfc3ebf4b87a44570b16668b23e

# Matches finished in regular time (FT) in the last 3 days
GET /v1/soccer/matches/window?from_days=-3&to_days=0&status=FT

Response example

same structure as the match endpoint

{
  "success": true,
  "data": [
    {
      "match_id": "as_37f0da0520bb4e9a9588f80994cefc5b",
      "date": "2026-07-15",
      "time": "19:00",
      "status": "19:00",
      "league": "World Cup",
      "league_id": "asl_62db9cfc3ebf4b87a44570b16668b23e",
      "season": "2026",
      "home": {
        "name": "England",
        "team_id": "ast_13e4e7eccd7640de91c13cffcf0c3ff2"
      },
      "away": {
        "name": "Argentina",
        "team_id": "ast_9137ee449e3b40a68149ca319373adaf"
      },
      "venue": ""
    }
  ],
  "meta": {
    "total": 1,
    "page": 1,
    "limit": 50,
    "total_pages": 1,
    "timestamp": "2026-07-13T19:18:24.076830600Z"
  },
  "traceId": "f11f21f6-0b68-438d-94b7-c8622470176f"
}

Error example

from_days > to_days (or the window span exceeds 90 days) → HTTP 400, error.code INVALID_PARAMS

GET /v1/soccer/matches/window?from_days=5&to_days=0

​Endpoint

​Parameters

​Response fields (data: array)

​Enum reference

​Request examples

​Response example

​Error example

Endpoint

Parameters

Response fields (data: array)

Enum reference

Request examples

Response example

Error example