Starting with v1.73, the AFL API returns a new validation array on the Match Statistics endpoint responses. This is designed to provide greater flexibility with your stats queries, making them easier to reuse between competitions and giving you an explanation why certain metrics aren't returned.

Overview

When fetching match statistics, there are scenarios where specific requested metrics are currently not applicable for a given match. Previously, these requests would be rejected entirely based on a single metric - frustrating if 99/100 are supported. This also made reusing queries between different competitions impractical as they needed to support the same metrics.

The new validation object explicitly outlines these issues. This object is returned on the following GET and POST endpoints:

• /v1/matches/matchId/statistics/players
• /v1/matches/matchId/statistics/squads

Validation Object Structure

The validation property is an array of ValidationDetails objects. Each object provides structured context about the specific validation warning or error.

Available Error Types​

To retrieve all possible validation error types that can be returned by the API, you can query our new metadata endpoint:

• GET /v1/metadata/validationerrortypes

Example Response Payload

Below is an example of a JSON response containing the new validation array. In this scenario, the caller has requested PLAYER_RATING for a match where it is not available (a VFL match), while the standard KICK metric resolves successfully.

{
    "squads": [
        {
            "players": [
				{
					"statistics":[
						{
							"valueDisplay":"6",
							"value":6,
							"id":56,
							"code":"KICK",
							"name":"Kick",
							"namePlural":"Kicks"
						}
					],
					"jumperNumber":41,
					"displayName":"Z.Walker",
					"fullname":"Zac Walker",
					"personId":1041619
				}
            ],
			"code":"FTS",
			"id":7306,
			"name":"Footscray Bulldogs"
        }
    ],
    "validation": [
        {
            "context": "Match",
            "reason": "MetricNotValidForMatch",
            "code": "Match_MetricNotValidForMatch",
            "details": "'PLAYER_RATING' is not valid for this match.",
            "metricCode": "PLAYER_RATING"
        }
    ],
    "matchId": 183271681
}

Testing in the Sandbox

We invite you to test these changes in the AFL API Sandbox environment.

• Sandbox URL: https://api.afl-sandbox.championdata.io

If you have any questions or require support regarding the new validation object, please contact the Champion Data Service Desk.

Starting this year, the AFL API provides access to Trial Matches to clubs via the Talent Standard/Standard Plus packages. While these matches work similarly to regular competition matches, they have some unique aspects worth detailing.

Where can I find them?​

There are two API League records that host the Trial Matches: one Male, one Female.

 {
    "id": 22,
    "name": "Trial Matches",
    "code": "TRIAL",
    "gender": "M"
  },
  {
    "id": 23,
    "name": "Trial Matches Womens",
    "code": "TRIALW",
    "gender": "F"
  }

Because Trial Matches can be played by a variety of different ages and seniority levels, a special Level Id is used to put them together - Level Id 10. This id will be used wherever Level Id is called for.

  {
      "id": 10,
      "name": "Trials",
      "code": "TRIAL",
      "classification": {
        "id": 2,
        "code": "AFLTIER2"
      }
    }

To get the full list of matches for 2026 then, for either league, is a call to the Season Fixture endpoint.

• Male: [https://api.afl.championdata.io/v1/leagues/22/levels/10/seasons/2026/fixture]
• Female: [https://api.afl.championdata.io/v1/leagues/23/levels/10/seasons/2026/fixture]

Once you have the desired Match Id, then use it as you would any other match.

What else should I know?​

While the trial matches are presented in a single league, level and season, the squads are of course not necessarily competing with each other - this contains matches across Australia. If you call the Season Ladder endpoint for example, it will return a response, but not one that makes any real sense.

Finally, the API does not currently contain past trial matches, it has started with 2026, so if you call previous seasons there's nothing yet to return. We will communicate when the past seasons are available at a later date.

We are pleased to announce that access to the AFL Sports Data Warehouse is now available for use. This article provides a brief overview of what the Warehouse contains and how you can get access to it.

What does the Warehouse contain?​

The Warehouse contains the following Leagues:

• AFL Premiership Seasons 2019 - 2025 [API League Id 1]
• AFLW Seasons 2017 - 2025 [API League Id 3]

Pre-Season Leagues (Ids 2 and 4 respectively) are currently not available but will be loaded in the near future. Likewise, Tier 2 Competitions are a priority item to be added to the Warehouse in 2026.

Can I use the Warehouse for live matches?​

The Warehouse is not updated with live match activity. Once a match has been played and marked Complete, it is updated in the Warehouse. As a result, matches in the Warehouse typically jump to the ‘Complete’ status and do not pass through the usual statuses that a match does when watched via the AFL API.

You should continue to use the AFL API for all live match data use.

How is the Warehouse laid out?​

There are currently three ‘namespaces’ of tables and views in the Warehouse:

• FIXTURES - content specific to competitions and seasons, notably each season’s fixture and all the matches within it
• REFERENCE - content that helps describe the content in each season and match. Also includes the Glossary table which provides a list of all the metrics, their descriptions and how they are calculated
• STATISTICS - match stats are stored here, both player and squad stats

Every match is in the Warehouse, accompanied by their player and squad statistics. Each stat is presented by the following dimensions:

• Period
• Logical Zone (i.e. D50, AM)
• Physical Zone (i.e. L50, RM)
• Whether the stat happened pre- or post-clearance

The Warehouse provides a set of views on the stats that roll them up into commonly queried dimension sets, so you don’t have to start each query by aggregating stats to remove the dimensions you are not interested in.

How do we get access to the Warehouse?​

1. Return the completed AFL 2026 Order Form​

Access to the Warehouse is included with the 2026 order and granted after you return the 2026 order form.

2. Already using Snowflake?​

Access to the AFL Warehouse will be via a Snowflake data share. This provides a direct connection to the Warehouse and appears as another database in the catalog for your use.

To set up the data share, please email Champion Data support with your Snowflake Account Locator. We will create the share, let you know we've done it, then the next time you refresh Snowflake the Warehouse will appear.

Finding your Account Locator​

To find the locator for an account, you can use Snowsight (Snowflake's Web App) or SQL.

Snowsight​

• Open the account selector and select your Snowflake account
• Select 'View account details'

• The Account Details dialog displays information about the account, including the account identifier and the account URL.
• You can copy the account locator from the Account Locator field.

SQL​

You can call the following function to identify the account locator for the Snowflake account you are connected to:

• Call CURRENT_ACCOUNT() to retrieve the account locator.

3. Not using Snowflake?​

Snowflake is required to access the AFL Warehouse. If you do not wish to set up an account with Snowflake, we can provide access to the Warehouse via an account created by Champion Data. This account does not provide the full capabilities that Snowflake offers and the number of credits you can use per month is capped. We encourage clubs to set up their own Snowflake account to get the best experience from the Warehouse.

Unlike other Champion Data products, we do not create individual user accounts to access the Warehouse in this way. Instead, we create an administrator account, send you the details and you use the account to make user accounts as you see fit.

To arrange set up of a Champion Data Snowflake Account, please email Champion Data support with a nominated person's email address, who will act as your Warehouse account admin.

What’s next?​

We will be publishing a set of articles, be it example queries, reports, videos or dashboards, to demonstrate how to the use the Warehouse. This will cover the following:

• Match Statistics Aggregation
• Creating Summary Views with stat columns
• Using the Metric Glossary to calculate percentage metrics
• Querying the Warehouse from Power BI/Tableau

Mini-roadmap to end of March​

These are the upcoming improvements to the roadmap through the start of the season. Towards the end of March we will publish a more comprehensive roadmap for all AFL products to the end of the season.

• MATCH.TRANSACTIONS Table - access transactions from every match from one table
• STATISTICS.FLOW Table - timecoded occurrences of metrics from every match from one table
• Elite Package content - 45 Kick and Speed of Ball Movement metrics
• Pre-Season Leagues
• Enhancing tables and views with more data
• Responding to your feedback (if we get it soon!)

Got a Question or an Issue?​

Please email Champion Data support with any questions or issues you might have with accessing the Warehouse or its contents.

The v1.63 update added timestamps to the Match Transactions endpoint, the start of the roll out of 'Time Capture' across the AFL API. Once we're finished, time capture timestamps will be available on the following Match endpoints:

• Chains (chain start and end times)
• Entries (time of Inside 50)
• Rotations (current stint start time)
• Shots (time of shot taken)
• Statistics Flow (stat occurrence time)
• Stoppages (time stoppage was started, hitout and cleared)

Time Capture aligns events to a specific frame of vision and is more precise and accurate than the existing period seconds. This has multiple benefits, from accurate metric calculation to tying events to match vision.

Before you start integrating this data into your operations, here's a few important items to note.

The 'capturedTimestamp' attribute​

Every timestamp is accompanied by whether it is a 'captured' timestamp.

When this value is TRUE, the timestamp is from time capture and can be reliably used as the time of the actual event.

When this value is FALSE, the timestamp is an estimation. It is generated by adding the Period Seconds the transaction was recorded against to the Period Start Time. These estimations are provided to give every transaction a timeframe so when the transaction set is ordered by timestamp, these transactions aren't placed at the top/bottom of the list.

Example​

The Premiership 2025 Grand Final (Id 127270401) first quarter started at 27/09/2025 4:31:38 AM UTC time. A transaction that was recorded at 30 Period Seconds and doesn't have a time capture timestamp returns an estimated timestamp of 27/09/2025 4:32:08 AM, being 30 seconds on from the start of the quarter.

Live Matches​

Time Capture timestamps are generated live during matches, but do fall behind the match by up to 5 minutes. This is generally caught up during quarter breaks and always caught up at half time. While a transaction is waiting on its time capture timestamp, its 'capturedTimestamp' value will be FALSE.

Season Support and Data Review​

Time Capture data is only available for AFL Men's. AFL Premiership 2024 and onwards is currently available via the API. We intend to support earlier seasons in the API in due course.

We are also continuing to review transactions that lack time captured timestamps to identify and fill in any gaps. Some transactions may not get accurate timestamps because the vision recorded obscures the event and as such an estimate may be used.

It's been a busy year for us on the AFL API and if you haven't been following on mid-season, here's a round up of what's been added from post-season 2024 to right now.

New API Features​

Tier 2 Competitions​

We have added the Tier 2 competitions listed in the table below to the AFL API. Tier 2 marks the use of multiple League Levels for the first time, so note that some competitions require you to use a Level Id other than 1.

All match endpoints are available to Tier 2 matches, though due to each competition's smaller data set, they return less information compared to AFL or AFLW matches. Starting with 2026, we will be providing the Tier 2 Advanced data set to selected competitions.

More information about the Tier 2 Advanced Data Set can be found here.

Match Statistics Flow Endpoint​

We added a new stats flow endpoint in August which returns all the timecoded occurrences of metric values in a match. Helpful if you want to track when we recorded Long Down the Line kicks happening, which is not easy to determine from match transactions alone.

• More info

Match Stoppages Endpoint​

Back in November 2024 we added the stoppages endpoint, which returns all the timecoded occurrences of each stoppage in a match, along with a wealth of detail, including details on the stoppage exit.

• More info

Centre Bounce Zone​

At the very end of 2024 we introduced the Centre Bounce zone to the API, providing the ability to filter match stats to those that happened at centre bounces, and adding this zone to all applicable endpoints.

• More info

Indigenous All Stars Match​

We provided the 2025 Toyota AFL Indigenous All Stars Match live from the AFL API last February. Should these matches occur again in future the API is ready to support them.

Endpoint Enhancements​

We improved a bunch of existing endpoints throughout the last year too - here's the highlights.

New Metrics​

We've added dozens of new metrics to the API this year - too many to list in detail here, so here's the links to details in each release they were added.

Starting with the 2026 season, the AFL API will providing an 'advanced' data set for select Tier 2 competitions. This is a brief explanation of what that means and how it works.

What is the Advanced Data Set?​

This data set provides some of the more advanced analytical data elements to Tier 2 matches that we already provide for AFL and AFLW matches. This is achieved by performing graphical and pressure capture on Tier 2 matches, collecting where key events occurred on the ground and how much pressure was applied to them. With this data in place, the AFL API is able to generate statistics for metrics that depend on it.

The data set provides the following additional elements:

• Over 200 metrics
• Identifying if something occurred in the DM, CB or AM zones, rather than just broadly 'midfield'
• XY Locations
• Pressure Details
• Metres Gained
• Player Durability & Availability

Which Competitions?​

The following competitions will receive the Advanced Data Set in 2026:

API Endpoints​

The following endpoints return additional data as part of the Tier 2 Advanced Data Set:

Player Durability & Availability​

This data set will be delivered via a new API endpoint - its name and structure is currently TBD.

Metrics​

The Advanced Data Set provides the following metrics:

With the 2025 season properly in flight now, it's time for a progress update on the Roadmap to July 2025.

Tier 2 Competitions​

We continue to add Tier 2 competitions to the AFL Platform. We are still broadly on track to have them implemented into the production environment by mid-year. The following competitions have been completed along with their 2024 seasons:

• VFL - League Id 5, Level Id 1
• VFLW - League Id 6, Level Id 1
• U18 Championships - League Id 8, Level Id 5
• Coates Talent League Boys - League Id 10, Level Id 5
• Coates Talent League Girls - League Id 11, Level Id 5

We prioritised these competitions because of the challenges each one presented to the AFL API. This proved effective as it highlighted a few concerns which we have addressed "behind the scenes", having zero impact on the AFL Premiership and AFLW leagues already in place. This included:

• Handling the variability in Tier 2 venues' current sponsorship names (some have them, some don't, some change frequently)
• Handling when a Champion Data capture operator enrols a player into a Tier 2 match minutes before the match starts
• Improving metric generation, or indeed bypassing it on more advanced metrics that aren't supported by Tier 2 matches
• A single cancelled match in the Coates Talent Boys League last year that resulted in both teams being awarded a draw result

What's next for Tier 2?​

Multiple Level Leagues​

We are currently adding SANFL to the API. This will be the first league that has multiple levels, as we capture U18, U16 and Reserves SANFL matches.

Here's the table of levels each league can contain. Up to this point all API calls have been based around using the same level id (primarily Id 1), now querying will involve understanding which level you are targeting.

So this will be applied to both SANFL and WAFL as follows:

• SANFL - League Id 12
  • SANFL League - Level Id 1
  • SANFL Reserves - Level Id 2
  • SANFL U16 - Level Id 3
  • SANFL U18 - Level Id 5
• WAFL - League Id 16
  • WAFL League - Level Id 1
  • WAFL Reserves - Level Id 2
  • WAFL Colts - Level Id 6

Tier 2 Live Match Ingestion​

While we have committed to delivering matches to the API after they've been played this year ("post-match"), we are currently testing live match ingestion in the same manner as Tier 1 matches as we'd prefer to ingest all matches as they happen, regardless of tier. This in of itself is no challenge, but much of the work revolves around ensuring the AFL Platform handles the additional load in live matches and that none impact one another. To this end, we've taken the decision to logically isolate Tier 1 matches from Tier 2. This will have no impact on your use of the API and will ensure that should some issue occur with a Tier 2 match, its impact to the Platform will be limited to Tier 2 only.

Advanced Data Queries (ADQ)​

We have selected Snowflake as the core technology for powering Advanced Data Queries and we have begun principal development. We have recently formed a team with a focus on data engineering and we are looking to grow the team as we scale for delivery.

First Release July 2025​

The first release of ADQ will provide a queryable dataset that replicates the capabilities of CIA's Dimensional Custom report. This will initially cover Tier 1 leagues (AFL Premiership, AFLW), then later in the year expand to include Tier 2 leagues once they are available from the AFL API.

Metric Glossary API Endpoint​

The /metadata/metrics/glossary endpoint provides detailed information about each metric, including how it is aggregated and a technical description. It is undergoing a last-minute polish to standardise terminology and will be available in the next few weeks.

Match Metric Events API Endpoint​

Work has begun on implementing a new API endpoint that returns when each instance of a metric occurred, along with which player(s) it applies to, its location and accompanying information such as pressure. Initial work revolves around looking at how to structure the API response - conventionally by period and period seconds or grouped by metric/transaction.

Head Start Report Metrics​

This quarter, we’re prioritising the implementation of the following types metrics that are currently only available through the Head Start report suite.

Contested Possession Source Metrics​

These metrics return the number of contested possessions based on the state of possession beforehand:

• Own Team Control – when your team had possession before the contest.
• Opposition Control – when the opposing team had possession.
• Neutral (Pre-Clearance) – when neither team had clear control.

Contested Possession Breakdown​

This set of metrics categorises contested possessions by the type of play:

• Ruck
• General Play – Air
• General Play – Ground
• Other Stoppage

Shot at Goal Types​

These metrics break down shots at goal by type and cover:

• Expected Points & Accuracy
• Both Set Position and during General Play

Ahead of the 2025 season we are updating the AFL API's authentication module as part of a review to improve our support processes.

As part of this update, if you are using an M2M account to communicate with the AFL API, the account's credentials (the Client ID and Client Secret) will be refreshed. This requires action on your part to ensure your applications continue to have access to the AFL API.

What needs updating?​

Once you have received your new Client Id & Secret (via a secure link sent by email), replace the existing values with the new ones.

In addition, the M2M token address has changed - update it to the following:

https://championdata-afl.au.auth0.com/oauth/token

When can I apply these changes?​

As soon as you receive them from Champion Data - they take immediate effect.

How long do I have to make the change?​

The original M2M credentials will be deactivated week commencing 10th March 2025, after the season has started.

Questions?​

Please email your questions to support@championdata.com.au.

With the AFL Premiership season done, and AFLW 2024 approaching the finish line, we thought it would be a good point to summarise everything added to the AFL API this year.

New API Features​

Match Statistic POST endpoints​

At the start of the year, we introduced the Match Statistics POST Endpoints. While they perform the same function as the GET Endpoints, they enable you to make multiple statistic queries against a match in one API call, rather than several. They are both faster and more efficient, plus they save on API calls when you're watching your usage limit.

• Players statistic POST endpoint
• Squads statistic POST endpoint

AFLW Matches​

AFLW is now formally supported by the AFL API, providing both past, live and future matches as they happen. AFLW matches work near identically to their Premiership counterparts, so you can reuse existing reports, dashboards and applications for AFLW simply by querying their match ids.

• How AFLW Works

'Last X' match statistics filter​

The match statistics endpoints can now be filtered to a time range within a period, or to the last few minutes of play in a period. This can be used to drive a match day dashboard that shows how players are doing for the past 10 minutes.

• How Last X Works
• R Package Last X Functionality

Match Transaction & Summary File Support Package Functions​

The R Package (and later this year, the Python Package) now provides functions to generate these support site files from the AFL API.

• Support Site File Replacement Functions

New Metrics​

The following metrics were added to the AFL API between March and October this year.

• ABSENCE_CENTRE_BOUNCE_LOSS_PCT

  The percentage of a players total centre bounce absences that result in a clearance to the opposition squad.

• ABSENCE_CENTRE_BOUNCE_NEUTRAL_PCT

  The percentage of a players total centre bounce absences that do not result in a clearance for that centre bounce for either team.

• ABSENCE_CENTRE_BOUNCE_WIN_PCT

  The percentage of a players total centre bounce absences that result in a clearance to the given players squad.

• ATTENDANCE_CENTRE_BOUNCE_LOSS_PCT

  The percentage of a players total centre bounce attendances that result in a clearance to the opposition squad.

• ATTENDANCE_CENTRE_BOUNCE_NEUTRAL_PCT

  The percentage of a players total centre bounce attendances that do not result in a clearance for that centre bounce for either team.

• ATTENDANCE_CENTRE_BOUNCE_WIN_PCT

  The percentage of a players total centre bounce attendances that result in a clearance to the given players squad.

• CLEARANCE_PCT

  The percentage of all stoppages that resulted in a clearance win.

• DISPOSAL_PER_TURNOVER

  Ratio of Disposals compared to Disposals that were also turnovers.

• DISPOSAL_TURNOVER

  Disposals that resulted in a turnover, where the zone is attributed to the zone of the disposal.

• GOAL_EXPECTED

  Total goals expected from a given shot (based on location, pressure, sidedness). At a transaction level this will show expected accuracy and when summed will show the expected goal.

• HANDBALL_TURNOVER

  Handballs that resulted in a turnover, where the zone is attributed to the zone of the handball.

• INSIDE_50_FORCED_ENTRY_RETURN

  Total points returned after a forced inside 50 entry and before another inside 50 or centre bounce.

• INSIDE_50_INITIAL_DIRECT_ENTRY_RETURN

  Total points returned after a direct initial inside 50 entry and before another inside 50 or centre bounce.

• INSIDE_50_INITIAL_ENTRY_RETURN

  Total points returned after an initial inside 50 entry and before another inside 50 or centre bounce.

• INSIDE_50_MID_STOPPAGE_DIRECT_ENTRY_RETURN

  Total points returned after a direct midfield stoppage inside 50 entry and before another inside 50 or centre bounce.

• INSIDE_50_MID_STOPPAGE_ENTRY_RETURN

  Total points returned after a midfield stoppage inside 50 entry and before another inside 50 or centre bounce.

• INSIDE_50_REPEAT_DIRECT_ENTRY_RETURN

  Total points returned after a direct repeat inside 50 entry and before another inside 50 or centre bounce.

• INSIDE_50_REPEAT_ENTRY_RETURN

  Total points returned after a repeat inside 50 entry and before another inside 50 or centre bounce.

• INSIDE_50_TRANSITION_DIRECT_ENTRY_RETURN

  Total points returned after a direct transition inside 50 entry and before another inside 50 or centre bounce.

• INSIDE_50_TRANSITION_ENTRY_RETURN

  Total points returned after a transition inside 50 entry and before another inside 50 or centre bounce.

• KICK_TURNOVER

  Kicks that resulted in a turnover, where the zone is attributed to the zone of the kick.

• METRES_GAINED_ASSISTED

  Total metres gained by a teammate that receives an uncontested possession from your disposal.

• METRES_GAINED_DISPOSAL

  Metres Gained via disposals. Measured from the point the original point of possession to the next possession or stoppage.

• METRES_GAINED_DISPOSAL_AVG

  The average number of meters gained per-disposal

• METRES_GAINED_HANDBALL

  Metres Gained via handballs. Measured from the point the original point of possession to the next possession or stoppage.

• METRES_GAINED_HANDBALL_AVG

  The average number of meters gained via handballs

• METRES_GAINED_KICK

  Metres Gained via kicks, measured from the point of the original possession to the next possession or stoppage.

• METRES_GAINED_KICK_AVG

  The average number of metres gained via kicks

• METRES_GAINED_NET

  Metres Gained plus Assisted Metres Gained.

• METRES_GAINED_OTHER

  Metres Gained not via disposals.

• METRES_GAINED_RETAIN

  Metres Gained where the disposal/possession was retained.

• ONE_PERCENTER

  Cumulation of knock ons, shepherds, credits, spoils and smothers.

• POINTS_ABOVE_EXPECTED

  Total points scored above the expected score.

• POSSESSION_CONTESTED_PCT

  The percentage of all possessions that are contested possessions.

• POSSESSION_UNCONTESTED_PCT

  The percentage of all possessions that are uncontested possessions.

• PRESSURE_ACT_FORCED_TURNOVER_BEHI_PCT

  The percentage of all forced turnovers that result in a behind.

• PRESSURE_ACT_FORCED_TURNOVER_GOAL_PCT

  The percentage of all forced turnovers that result in a goal.

• PRESSURE_ACT_FORCED_TURNOVER_POINTS

  Total points generated by pressure acts forcing a turnover.

• PRESSURE_ACT_FORCED_TURNOVER_SCORE_PCT

  The percentage of all forced turnovers that result in a score.

• RANKING_POINTS

  The Official Champion Data AFL Rankings system was established in 1999 and has been developed into a robust and comprehensive system for objectively measuring player performance through the use of statistical measures. The rankings are geared to reward the winning factors of a game of AFL football. They are used as the scoring measure in the Herald-Sun SuperCoach fantasy game.

• TIME_IN_POSSESSION_DISPUTE_PCT

  The percentage of total elapsed time where the ball was in play but neither team had possession.

• TIME_ON_GROUND_LOOSE

  Time in seconds that a player was loose during a game.

• TIME_ON_GROUND_LOOSE_PCT

  Percentage of time that a player was loose during a game.

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.