Overview
The American Football Tournament Simulations feed provides traditional team metadata and tournament-level probability outputs. Team data includes name, conference, division, code, club details, area, and team type. Prediction data includes probabilities for outcomes such as winning a tournament, qualifying for knockout phases, wins, losses, reaching playoffs, and related tournament progression outcomes.
The feed is designed for tournament calendar or team-specific simulation use cases where clients need structured probability outputs alongside team identity and competition context.
Problem Statement & Use Cases
This API solves the business problem of turning tournament simulation outputs into queryable, structured data for American Football applications. It helps products compare teams, forecast tournament progression, and expose playoff or tournament-outcome probabilities in a consistent API format.
| Use Case |
Description |
| Playoff odds dashboards |
Display each team's likelihood of reaching the playoffs, qualifying for knockout phases, or advancing through a tournament. |
| Tournament winner projections |
Power visualizations showing the probability of each team winning a tournament or competition. |
| Simulation-driven editorial tools |
Support articles, broadcast graphics, and matchup previews with probability-based tournament outcome context. |
| Forecasting and modeling pipelines |
Ingest team-level prediction outputs into downstream analytics models, ranking systems, or fan-facing prediction products. |
Compliance & Guidelines
Authentication and API Security
To comply with Stats Perform API security and best-practice requirements, refer to the Stats Perform FAQs, API Overview, and Authentication Guide.
Authentication uses the OAuth method to fetch data.
Polling Frequency
Do not exceed the rate confirmed by Stats Perform. Contact a Stats Perform representative for higher rate limits or clarification.
| Feed |
Polling Frequency |
| Tournament Simulations (TM11) |
Once every 24 hours |
Request Formatting Rules
All URLs are case-sensitive. URL strings must contain the correct case, operators, and required parameters, or the API returns an error.
| Rule |
Requirement |
| Query string start |
Begin the query parameter string with ? immediately after the feed name. |
| Parameter separator |
Separate query parameters with &. |
| Multiple values: AND |
Use & for multiple values where the API treats them as AND. |
| Multiple values: OR |
Use , only if the parameter supports OR-style multiple values. |
| NOT operator |
Use ! only if the parameter supports negation. |
| Underscore-prefixed parameters |
Include the required _ prefix for parameters such as _fmt and _clbk. |
| Placeholder braces |
Remove placeholder curly braces {} from production API calls. They are documentation examples only. |
| Case sensitivity |
Preserve exact URL, parameter, and operator case. |
| Base URL reference |
The base URL format is {protocol}://{requestDomain}/{feedResource}. |
JSONP Requirements
If _fmt=jsonp is used, it must be combined with the callback parameter _clbk.
| Constraint |
Requirement |
Reason |
| JSONP callback |
Use _fmt=jsonp together with _clbk. |
JSONP requires a callback wrapper function. |
| Fixed callback value |
Use a fixed _clbk value whenever possible. |
Random callback names can reduce cacheability and violate API best-practice logic. |
| JavaScript frameworks |
Override framework-generated random callback names, including defaults from common frameworks such as jQuery. |
Some frameworks generate random JSONP function names unless explicitly configured. |
Endpoints
Base URL
https://api.statsperform.com
Feed Resource
/sdapi/v1/footballdata/tournamentsimulations
Get Tournament Simulations by Query Parameters
GET /sdapi/v1/footballdata/tournamentsimulations?{queryParameters}
| Usage |
Feed |
| Get Tournament Simulations data according to specified parameter values. |
/sdapi/v1/footballdata/tournamentsimulations?{queryParameters} |
Get Tournament Simulations by Tournament Calendar Inline Path URL
GET /sdapi/v1/footballdata/tournamentsimulations/{tmclUUID}?_fmt={format}
| Usage |
Feed |
| Get Tournament Simulations list by tournament calendar UUID inline path URL. |
/sdapi/v1/footballdata/tournamentsimulations/{tmclUUID}?_fmt={format} |
Example Request Pattern
GET https://api.statsperform.com/sdapi/v1/footballdata/tournamentsimulations?{queryParameters}
Query Parameters
This feed uses Global query parameters and the feed-specific query parameters listed below.
The /tournamentsimulations feed must be queried by a specific tournament calendar UUID or team UUID, and additional query parameters can be combined in a request when supported.
Feed-Specific Query Parameter Combinations
| Query Parameter Combination |
Description |
Example Request |
tmcl |
Get Tournament Simulations list by tournament calendar UUID. |
GET https://api.statsperform.com/sdapi/v1/footballdata/tournamentsimulations?tmcl={tmclUUID}&_fmt=xml |
{tmclUUID} path parameter |
Get Tournament Simulations list by tournament calendar UUID inline path URL. |
GET https://api.statsperform.com/sdapi/v1/footballdata/tournamentsimulations/{tmclUUID}?_fmt=xml |
statsId |
Get Tournament Simulations list by Stats ID. |
GET https://api.statsperform.com/sdapi/v1/footballdata/tournamentsimulations?statsId={statsId}&_fmt=xml |
Parameter Definitions
| Parameter |
Required |
Description |
Accepted Values / Format |
Notes |
_fmt |
No |
Response data format. |
{dataFormat}, such as xml, json, or jsonp. |
Global query parameter. Required in examples. |
_clbk |
Conditional |
JSONP callback function name. |
Fixed callback function name. |
Required when _fmt=jsonp. |
tmcl |
Conditional |
Filters Tournament Simulations by tournament calendar UUID. |
String; alphanumeric UUID |
Use when querying by tournament calendar through the query string. |
{tmclUUID} |
Conditional |
Tournament calendar UUID passed as an inline path parameter. |
String; alphanumeric UUID |
Used in the inline path URL method. |
statsId |
Conditional |
Filters Tournament Simulations by unique Stats ID. |
String |
The source example labels this as statsId = id and shows statsID; preserve the parameter casing required by the target API implementation. |
Entity Filtering Constraints
| Constraint |
Requirement |
| Required entity scope |
Query by a specific tournament calendar UUID or team UUID. |
| Documented tournament calendar methods |
Use either tmcl={tmclUUID} or /tournamentsimulations/{tmclUUID}. |
| Stats ID access |
Use the Stats ID query parameter when querying by Stats Perform identifier. |
| Placeholder removal |
Remove {} placeholder braces from production calls. |
| Global parameters |
Global query parameters can be combined with feed-specific parameters when supported. |
Output Schema
The feed response fields are documented using XML element names. JSON responses contain similar fields, but XML-only schema attributes or XML-only wrapper nodes may be omitted or represented differently.
`<tournament
Simulations>`
| Property |
Value |
| Nesting |
tournamentSimulations |
| Description |
Required root element of the fields related to tournament simulations. |
| Attribute |
Required |
Description |
Values |
xmlns:footballdata |
Yes |
XML schema reference. Returned for XML only. |
http://www.performgroup.com/schema/footballdata |
<competition>
| Property |
Value |
| Nesting |
tournamentSimulations/competition |
| Description |
Required root element of the related fields for the competition. |
| Attribute |
Required |
Description |
Values |
id |
Yes |
Unique ID of the competition. |
String; alphanumeric UUID |
name |
Yes |
Name of the competition. |
String |
`<tournament
Calendar>`
| Property |
Value |
| Nesting |
tournamentSimulations/tournamentCalendar |
| Description |
Required root element of the related fields for the tournament calendar. |
| Attribute |
Required |
Description |
Values |
id |
Yes |
Unique ID of the tournament calendar. |
String; alphanumeric UUID |
statsId |
No |
Unique Stats ID of the tournament. |
String |
startDate |
Yes |
Start date in UTC of the tournament calendar. |
Date in format YYYY-MM-DDZ |
endDate |
Yes |
End date in UTC of the tournament calendar. |
Date in format YYYY-MM-DDZ |
<predictions>
| Property |
Value |
| Nesting |
tournamentSimulations/predictions |
| Description |
Required root element of the related fields for predictions. |
| Attribute |
Required |
Description |
Values |
type |
Yes |
League type for predictions. |
String |
lastUpdated |
Yes |
UTC date and time when the information or record was last updated. |
Date/Time in format YYYY-MM-DDThh:mm:ssZ |
<team>
| Property |
Value |
| Nesting |
tournamentSimulations/predictions/team |
| Description |
Required root element of the related fields for a team. |
| Attribute |
Required |
Description |
Values |
id |
Yes |
Unique ID of a team. |
String; alphanumeric UUID |
statsId |
No |
Unique Stats ID of a team. |
String |
name |
Yes |
Unique name of the team. |
String |
conference |
Yes |
Name of the conference. |
String |
division |
Yes |
Name of the division. |
String |
shortName |
Yes |
Short name of the team. |
String |
clubName |
Yes |
Club name of the team. |
String |
code |
Yes |
Three-character code used for the team name, often used on TV scoreboards. |
String |
type |
No |
Type of team. |
String; one of club, national |
teamType |
No |
Team type. |
String; one of default, women, youth |
areaId |
No |
Unique Area UUID of the team. |
String; alphanumeric UUID |
area |
No |
Area name to which the team belongs. |
String |
city |
No |
City name to which the team belongs. |
String |
<predicted>
| Property |
Value |
| Nesting |
tournamentSimulations/predictions/team/predicted |
| Description |
Required root element of the related fields for prediction types. |
| Attribute |
Required |
Description |
Values |
type |
Yes |
Type of prediction being made. |
String |
value |
Yes |
Percentage value for the prediction type. |
String |
Prediction type values are not enumerated in the source text. The feed overview describes probability outputs for winning a tournament, qualifying for knockout phases, wins, losses, reaching playoffs, and similar tournament progression outcomes.
