--- title: |- FIS data exchange XML protocol for Snowboard and Freestyle version: "1.3" date: 2026-09-10 documentName: Snowboard and Freestyle Result XML Description documentType: XML Protocol Description author: FIS IT theme: dark toc: true tocDepth: 3 cover: true chapterNumbering: true headerTitle: Snowboard and Freestyle Result XML Description footerDateFormat: YYYY-MM-DD --- # 1. Table of contents - [2. Introduction](#2-introduction) - [2.1. Sending XML results to FIS](#21-sending-xml-results-to-fis) - [2.2. Support](#22-support) - [3. XML structure](#3-xml-structure) - [3.1. The `` element](#31-the-fisresults-element) - [3.2. The `` element](#32-the-raceheader-element) - [3.2.1. The `` element within ``](#321-the-type-element-within-raceheader) - [3.2.2. The `` element within ``](#322-the-racedate-element-within-raceheader) - [3.2.3. Example of a simple `` element](#323-example-of-a-simple-raceheader-element) - [3.3. The `` element](#33-the-sb_race-element) - [3.3.1. The `` element](#331-the-sb_raceinfo-element) - [3.3.2. The `` element](#332-the-jury-element) - [3.3.3. The `` element](#333-the-finalformat-element) - [3.3.4. The `` element](#334-the-qualificationformat-element) - [3.3.5. The `` element](#335-the-sb_classified-element) - [3.3.6. The `` element](#336-the-sb_notclassified-element) - [3.3.7. The `` and `` element](#337-the-sb_ranked-and-sb_notranked-element) - [3.3.8. The `` element](#338-the-competitor-element) - [3.3.9. The `` element](#339-the-team-element) - [3.3.10. The `` element](#3310-the-sb_result-element) - [4. Examples](#4-examples) - [4.1. Results for individual Snowboard Park & Pipe event](#41-results-for-individual-snowboard-park-pipe-event) - [4.2. Results for individual Freestyle Ski Cross event](#42-results-for-individual-freestyle-ski-cross-event) - [4.3. Results for Snowboard Parallel Team event](#43-results-for-snowboard-parallel-team-event) - [4.4. Results for Snowboard Cross Team Event](#44-results-for-snowboard-cross-team-event) - [4.5. Results for Freestyle Aerials Team event](#45-results-for-freestyle-aerials-team-event) - [4.6. Sending start list for a Snowboard Park & Pipe event](#46-sending-start-list-for-a-snowboard-park-pipe-event) - [5. Change log](#5-change-log) - [5.1. Version 1.3, 10.09.2026](#51-version-13-10092026) - [5.2. Version 1.2, 19.06.2023](#52-version-12-19062023) - [5.3. Version 1.1, 07.09.2022](#53-version-11-07092022) - [5.4. Version 1.0, 21.07.2022](#54-version-10-21072022) # 2. Introduction For competition results to be included in the FIS database and to be considered for FIS points, results must be provided via XML file in the format described in this document. A very basic example of the XML file: ```xml 2022 6222 SUI SS WC 2022 3 15 1 5 550050 DOE Joe M SUI ``` This document describes the XML format for both Snowboard and Freestyle as the only major difference between these disciplines is the prefix for most XML tags – SB or FS. The example above is a valid XML for Snowboard results, but would be valid also for Freestyle if the ”`FS_`“ prefix is used, e.g. `FS_race`, `FS_classified`. All the examples in this document will use the “`SB_`” prefix unless the example defines Freestyle specific information. ## 2.1. Sending XML results to FIS Results in the correct XML format must be sent as an e-mail attachment to [results@fis-ski.com](mailto:results@fis-ski.com). Once received and processed an e-mail response will be sent informing of successful result processing or of any errors in case if processing failed. ## 2.2. Support For support requests, questions and feedbacks please contact FIS IT department at [it@fis-ski.com](mailto:it@fis-ski.com). When contacting support regarding a specific event, please indicate the race codex and discipline. # 3. XML structure ## 3.1. The `` element XML file will always have root `` element that it will contain two child elements - all the race defining information within `` and results with optional race details within `` or `` depending on the discipline. The element accepts no attributes and has these possible child elements: | Element | Data | Description | Required | |----------------|---------|---------------------------------------------------------------------------------------------------------------------------------------------|----------| | `` | element | Contains competition defining information – season code, codex, gender etc. | yes | | `` | element | Contains competition results, information about not-ranked competitors and optional details about the race – e.g., weather, judges, course. | yes | ## 3.2. The `` element The `` element defines the global properties of a race, importantly – season code, codex, race date and gender. Whenever XML results file is being processed, this data is used to find the race in the FIS database. The element has two required attributes: | Attribute | Data | Description | Required | |-----------|--------|--------------------------------------------------------------------------------------|----------| | `Gender` | string | Gender of the race with possible values – M (men), W (women), A (mixed team). | yes | | `Sector` | string | Discipline code of the race with possible values – FS (freestyle) or SB (snowboard). | yes | Possible child elements: | Element | Data | Description | Required | |----------------|---------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------| | `` | integer | Season code of the competition, as in FIS calendar. | yes | | `` | integer | The unique identification number for each competition with the discipline, as in FIS calendar. | yes | | `` | string | The three letter FIS code for the organizing nation, as in FIS calendar | yes | | `` | String | Event abbreviation of the competition, as in FIS calendar:
BA - Big Air
MO - Moguls
SS - Slopestyle
SX - Ski Cross
HP - Halfpipe
DM - Dual Moguls
DMT - Dual Moguls Team
AE - Aerials
AET - Aerials Team
SXT - Ski Cross Team
XT - Ski-Snowboard Team Cross
PGS – Parallel Giant Slalom
PSL – Parallel Slalom
GS – Giant Slalom
SL – Slalom
SBX – Snowboard Cross
BXT – Snowboard Cross Team
PRT – Parallel Team | yes | | `` | string | The FIS abbreviation for the category of competition specific to the event, as in FIS calendar | yes | | `` | element | Used to define the date of the competition (see 3.2.2). Must match the value defined in FIS calendar. | yes | | `` | string | Type of data – used to indicate whether the data contains results or start list. Example of possible values:
startlist – start list of the competition
partial – partial results
unofficial – unofficial results
official – official results
If not provided, it will consider the file to contain official results. It accepts the optional `Run` attribute (see 3.2.1) | no | | `` | string | Last phase completed after which the results are being sent for. Example of possible values:
final
smallfinal
semifinal
quarterfinal
eightfinal
sixteenfinal
thirtytwofinal
sixtyfourfinal
qualification
preheat
seeding
This value can be used to indicate that the event is not fully completed, by specifying something other than “final” for results. | no | | `` | string | Name of event as published in FIS calendar | no | | `` | string | Resort, town, etc. of competition venue | no | ### 3.2.1. The `` element within `` The `` element accepts multiple values as strings (startlist, partial, unofficial, official) and one attribute: | Attribute | Data | Description | Required | |-----------|---------|----------------------------------------------------|----------| | `Run` | integer | Run number for which the data is sent – e.g. 1, 2. | no | ### 3.2.2. The `` element within `` The `` element accepts three child elements: | Element | Data | Description | Required | |-----------|---------|--------------------------|----------| | `` | integer | Year of the competition | yes | | `` | integer | Month of the competition | yes | | `` | integer | Day of the competition | yes | Example of the `` element: ```xml 2022 3 15 ``` ### 3.2.3. Example of a simple `` element ```xml 2022 6222 SUI SS WC 2022 3 15 ``` ## 3.3. The `` element The `` element defines the competition specific information (jury, course etc.) along with the results of the competition. The element accepts three child elements: | Element | Data | Description | Required | |----------------------|---------|---------------------------------------------------------------------------|--------------------| | `` | element | Contains information about the competition – jury, course, format etc. | yes, for Ski Cross | | `` | element | Contains information about the ranked competitors. | yes | | `` | element | Contains information on competitors that were not ranked – e.g. DNS, DNF. | no | ### 3.3.1. The `` element The `` accepts multiple child elements: | Element | Data | Description | Required | |-------------------------|---------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------| | `` | integer | FIS list number which is used for the preparation of the start list and for calculation of FIS point penalty based on the results. | no | | `` | decimal | Applied penalty for the competition results. This may differ from the calculated penalty in case the calculated penalty is lower than the minimum allowed for the category of competition or above the maximum for the category of competition | no | | `` | decimal | Calculated penalty for the competition results. | no | | `` | string | Timing or scoring by company | no | | `` | string | Data processing by company | no | | `` | string | Name of software company | no | | `` | string | Name of timing or scoring software | no | | `` | string | Version of the timing or scoring software | no | | `` | element | Definition of the jury members (see 3.3.2) | yes | | `` | element | Definition of the final format (see 3.3.3) | yes, for Ski Cross | | `` | element | Definition of the qualification format (see 3.3.4) | yes, for Ski Cross | ### 3.3.2. The `` element The `` element is used to define a jury member. It accepts one attribute: | Attribute | Data | Description | Required | |------------|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------| | `Function` | enum | Function of the jury member with one of the available values:
HeadJudge
ChiefCompetition
RaceDirector
ContestDirector
TechnicalDelegate
StartReferee
FinishReferee
ChiefOfFinish
Referee | yes | The element accepts these child elements: | Element | Data | Description | Required | |---------------|--------|------------------------------------|----------| | `` | string | Last name of the jury member | yes | | `` | string | First name of the jury member | yes | | `` | string | FIS nation code of the jury member | yes | Example of the `` element: ```xml DOHN Joe USA ``` ### 3.3.3. The `` element The `` element withing `` is used to define details about the format competition was held in and is currently only required for Ski Cross events: | Attribute | Data | Description | Required | |-----------|------|-------------------------------------------------------------------------------------------------------------------------------------------------|----------| | `Perheat` | int | Maximum number of competitors per heat in the final phase | yes | | `Phase` | enum | The starting round of the finals phase:
final
semifinal
quarterfinal
eightfinal
sixteenfinal
thirtytwofinal
sixtyfourfinal | yes | ### 3.3.4. The `` element The `` element within `` is used to define the qualification phase format and type: | Attribute | Data | Description | Required | |-----------|------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------| | `Format` | enum | Format identifier:
qualification
seeding
qualification-heat
three-heat
round-robin | yes | | `Type` | enum | The subtype of a format:
For qualification or seeding formats:
single-run
two-run
two-run-cutoff
jam-session
For round robin format:
single-panel
double-panel | no | ### 3.3.5. The `` element The `` element is used to send the results or start list. In case of results, this should contain only the athletes that have been ranked in the competition. The element accepts one or multiple `` child elements: | Element | Data | Description | Required | |---------------|---------|---------------------------------------------------------------------------------------------|----------| | `` | element | Contains information on a valid competitor or team in the results or start list (see 3.3.7) | yes | ### 3.3.6. The `` element The `` element is used to send information on competitors that were not ranked in a competition, e.g. DNS, DNF, NPS etc. The element accepts one or multiple `` child elements: | Element | Data | Description | Required | |------------------|---------|-------------------------------------------------------------------------------------|----------| | `` | element | Contains information on a competitor or team that was not ranked in the competition | yes | ### 3.3.7. The `` and `` element The `` and `` elements can be validate differently depending on whether the XML file type in the `` (see 3.2.1) is defined as start list or results. Also, the amount and type of information required can be different depending on whether the `` is a direct child of `/` or it is used to define individual result as part of a team as a direct child of ``. The element accepts attributes: | Attribute | Data | Description | Required | |-----------|------|----------------------------------------------------------------------------------------------------------------------------------------------------------|----------| | `Status` | enum | For `` only one possible value – QLF. For `` this should be set to the IRM of competitor in the final phase of the competition. | yes | The element accepts child elements: | Element | Data | Description | Required | |----------------|---------|--------------------------------------------------|-----------------------------------------------------------------------------------------| | `` | integer | Competitors rank in the competition | yes, for results when `` is direct child of `` | | `` | integer | Competitors order in the start list | yes, for start list when `` is direct child of `` | | `` | integer | The competitor’s starting bib from the first run | yes | | `` | element | Details of the competitor (see 3.3.8) | yes, for individual competition or when `` is direct child of `` | | `` | element | Details of the team (see 3.3.9) | yes, for team competition and when `` is a direct child of `` | | `` | element | Details of the result | no | ### 3.3.8. The `` element The `` element is used to define information about an individual competitor, and it accepts multiple child elements: | Element | Data | Description | Required | |-----------------|---------|------------------------------------|----------| | `` | integer | FIS code, as in the FIS database | yes | | `` | string | Last name, as in the FIS database | yes | | `` | string | First name, as in the FIS database | no | | `` | string | FIS nation code | yes | | `` | enum | Gender – M (men), W (women) | no | | `` | integer | Birth year | no | | `` | string | Club name | no |
Example of a `` element: ```xml 2534887 APPLE USA ``` ### 3.3.9. The `` element The `` element is used to define information about a team: | Element | Data | Description | Required | |--------------|---------|-----------------------------------|----------| | `` | integer | FIS code, as in the FIS database | yes | | `` | string | Team name, as in the FIS database | yes | | `` | string | Competitor’s FIS nation code | yes | Example of a `` element: ```xml 2533431 SWITZERLAND SUI ``` ### 3.3.10. The `` element Like ``, also `` required data will depend on whether the element is sent as part of a team (``). The element accepts attributes only when sent as a descendant of ``: | Attribute | Data | Description | Required | |-----------|------|------------------------------------------|-----------------------------------------| | `Run` | int | Run number for which the result is sent | yes, when sent as part of a team result | | `Heat` | int | Heat number for which the result is sent | no | The `` element accepts child elements: | Element | Data | Description | Required | |----------------|---------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------| | `` | enum | Phase reached with possible values:
final
smallfinal
semifinal
quarterfinal
eightfinal
sixteenfinal
thirtytwofinal
sixtyfourfinal
qualification
preheat
seeding | yes, for team result | | `` | enum | Color of competitors bib (Cross events) or course (Parallel events). Possible values:
red
blue
green
white
yellow
black | no | | `` | decimal | Race points calculated for the competition result | no | | `` | decimal | Total score of the competition (or run, when sent as part of a team result) | no | | `` | time | Total time (which has value in terms of ranking). For example – for Cross events this has to be the achieved qualification time which will be used for FIS points calculation.
Format - HH:MM:SS.dd | yes, for Cross events | Example of a simple `` element as descendant of `` and ``: ```xml 1 14 2535331 DOE John USA final 100.22 ``` # 4. Examples ## 4.1. Results for individual Snowboard Park & Pipe event ```xml 2022 6058 SUI BA WC 23 10 2021 Chur Chur 1 17 9510288 BOESIGER Jonas M SUI 1995 162.00 36 9300953 HASEGAWA Taiga M JPN 2005 ``` ## 4.2. Results for individual Freestyle Ski Cross event ```xml 2022 8094 CHN SX OWG Men's Ski Cross Beijing (CHN) 18 2 2022 1 7 2531493 REGEZ Ryan M SUI 1993 1:12.44 ``` ## 4.3. Results for Snowboard Parallel Team event ```xml 2022 6333 GER PRT WC official Mixed Team Parallel Slalom Berchtesgaden 20 3 2022 1 2 9200224 Germany 9 GER 21 9200092 BAUMEISTER Stefan M GER 1993 2 Blue final 22 9205058 HOFMEISTER Ramona Theresia W GER 1996 2 Blue final ``` ## 4.4. Results for Snowboard Cross Team Event ```xml 2022 6079 CHN BXT OWG official Mixed Team Snowboard Cross Genting Snow Park, Beijing 12 2 2022 1 5 9531340 United States of America 1 USA 51 9530138 BAUMGARTNER Nick M USA 1981 2 green final 52 7310636 JACOBELLIs Lindsey W USA 1985 2 green final ``` ## 4.5. Results for Freestyle Aerials Team event ```xml 2022 8084 CHN AET OWG 10 2 2022 Beijing 1 2 2533348 UNITED STATES OF AMERICA USA 21 2526863 CALDWELL USA final 88.86 22 2530617 LILLIS USA final 135.00 23 2532461 SCHOENEFELD USA final 114.48 338.34 ``` ## 4.6. Sending start list for a Snowboard Park & Pipe event ```xml 2022 6273 CZE SS QUA startlist 18 3 2022 Spindleruv Mlyn 1 5 9531163 Winkelmann Luke USA 2000 qualification 1 2 9531369 Henricksen Dusty USA 2003 qualification ``` # 5. Change log ## 5.1. Version 1.3, 10.09.2026 | Section | Description | |---------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | General | Converted the document to Markdown as the document base
Corrected the domain of the FIS email addresses and made them links
Aligned the spelling of "organizing" with the other FIS XML descriptions | ## 5.2. Version 1.2, 19.06.2023 | Section | Description | |----------|------------------------------------------------------------------------------------------------| | Examples | Update `` description to include examples also for Snowboard events in chapter 3.2 | ## 5.3. Version 1.1, 07.09.2022 | Section | Description | |----------|------------------------------------------------------------| | Examples | Update Park & Pipe start list example to include `` | ## 5.4. Version 1.0, 21.07.2022 | Section | Description | |---------|-----------------| | Global | Initial version |