The complete 2023 season of the NAB AFLW league is now available from the AFL API. This article describes how you can access AFLW 2023 matches and what API endpoints apply to them.

AFLW League​

The AFLW League has been assigned league Id 3, which you can see here when you call the Leagues endpoint.

You can call every Season endpoint using league Id 3, they all support AFLW. Currently only the 2023 and (upcoming) 2024 seasons are available from the API, so you will receive a 404 error if you call on the prior seasons.

AFLW Matches​

AFLW match data is accessed the same way as AFL Premiership matches; by looking up their match ids and calling the match endpoints.

As with the AFL Premiership, you can look up AFLW matches via the Season Fixture endpoint (enter league Id 3, level Id 1, season 2023) and get their match ids from there.

AFLW matches are supported by all the match endpoints, including the transactions endpoint if you are licensed to access it.

Sandbox AFLW Match Replay​

The Sandbox environment contains a replaying AFLW match, starting at the same times as the other matches. Note however, as AFLW match quarters are shorter than Premiership matches, the match status timing table doesn't completely align with the AFLW match.

Unsupported Metrics​

The following metrics do not support AFLW matches and are not returned via the match statistic endpoints.

GET Endpoints​

The match stat GET endpoints now provides a new filter parameter called "lastXSeconds". This parameters filters the stats so they only count transactions that occurred on or within the last 'X' seconds of the match.

If used on a live match and called periodically, the stats will go up and down based on what's happened in the last number of seconds. As it is a 'seconds' filter, enter 300 to filter the last 5 minutes, 600 for last 10.

From and To Period Seconds​

Two more parameters have been added to the endpoints alongside lastXSeconds: fromPeriodSeconds and toPeriodSeconds.

These can be used to filter statistics to a particular range of time within a quarter. They can be used independently of each other, where they will run from the start/end of the quarter, or together to focus on a mid-quarter window.

POST Endpoints​

The match stat POST endpoints also support these parameters, they can be supplied in each metic request, and in different combinations in each request. They perform the same filtering as they do for the GET Endpoints.

R Package Support

The R package's getPlayerStats and getSquadStats function also include 'lastXSeconds' parameters to be used in the same fashion as calling the API endpoints directly. It too supports using the parameters in the getPlayerStatsPOST and getSquadStatsPOST endpoints. See here for more details.

Over the past few weeks, the team have been busily working on some new time parameters to the match statistics endpoints. They are intended to filter stats to what happened in a specific time period within a quarter, or to filter to the last few minutes of activity.

fromPeriodSeconds and toPeriodSeconds can be used to analyse performance within a specific time period in a match, especially when used with a period filter so you can examine performance in the first 5 minutes of every priod.

If used on a live match (and without a period filter), lastXSeconds gets you the stats from say the last 5 or 10 minutes of play. Best used in concert with a metric filter to keep the endpoint response small and manageable.

These new parameters will be implemented on both GET and POST endpoints (illustrated here on GET) and on both squad and player stats endpoints. They will also be available via the R & Python API Support Packages.

The AFL API provides XY coordinates of several match events, returned by a variety of endpoints such as:

• Transactions endpoint
• Chains endpoint
• Shots endpoint
• Entries endpoint

When used in combination with the venue dimensions (Venue endpoint), the coordinates can be used to plot where these events occurred on a graph.