A Tournament object describes a tournament for which a single result is published. A Tournament consists of a number of Match objects, a number of Registration objects, and other optional information.

Tournament object

name String The tournament's name.
short_name String An abbreviated version of the tournament's name. If omitted, assume the same as the name.
tournament_site TournamentSite Where this tournament happened; see below.
scoring_rules ScoringRules Validation rules for scoring matches in this tournament; see below.
start_date String The tournament's start date, as an ISO 8601-formatted string in the tournament's local time zone.
end_date String The tournament's end date, as an ISO 8601-formatted string in the tournament's local time zone.
registrations Array Registration The organizations registered to play in this tournament.
phases Array `Phase` The phases of play in this tournament.
rankings Array Ranking The rankings used at this tournament.
level String Level of tournament: "middle_school", "high_school", "college", "open", "trash", or "other"
difficulty String Difficulty of tournament within respective level: "novice", "regular", "nationals"
question_set String Free-form string of question set(s) used at this tournament.
info String Free-form string of other information relevant to tournament.

TournamentSite object

name String The tournament site's name (e.g. "Hyatt Regency O'Hare").
place String The location of the tournament. Free-form; the purpose is to enable people to find the site. An example might be "9300 Bryn Mawr Avenue, Rosemont, Illinois".
latitude Number The latitude of the tournament's site (for geolocation).
longitude Number The longitude of the tournament's site (for geolocation).

ScoringRules object

name String The name for this set of scoring rules.
teams_per_match Number The number of teams that participates in each match. If omitted, assume 2.
maximum_players_per_team Number The maximum number of players that may be active at once, per team, in a match. If omitted, assume 4.
regulation_tossup_count Number The standard number of tossups heard in a match. If omitted, assume 20.
maximum_regulation_tossup_count Number The maximum number of tossups heard in a match that does not go into overtime. (Different from regulation_tossup_count for tournaments that used timed matches.) If omitted, assume 20.
minimum_overtime_question_count Number The smallest possible number of overtime tossups or tossup-bonus cycles (as determined by overtime_includes_bonuses). If overtime is sudden death from the beginning, this will be 1, and that is the value assumed if this field is omitted.
overtime_includes_bonuses Boolean Are bonuses used in overtime? If omitted, assume false.
total_divisor Number The largest integer that is guaranteed to be a factor of a valid final score for one team in one match. If omitted, assume 5. If present, must be a positive integer.
maximum_bonus_score Number The maximum possible score on a single bonus. Omitting this means there are no bonuses. If present and bonus_divisor is present, must be divisible by bonus_divisor.
bonus_divisor Number The largest integer that is guaranteed to be a factor of a valid score on a single bonus. If omitted but maximum_bonus_score is present, assume 10. If present, must be a positive integer.
minimum_parts_per_bonus Number The smallest number of parts that may exist in one bonus. If omitted but maximum_bonus_score is present, assume 3. If present, this must be a positive integer. If maximum_parts_per_bonus is present, this must be less than or equal to maximum_parts_per_bonus.
maximum_parts_per_bonus Number The greatest number of parts that may exist in one bonus. If omitted but maximum_bonus_score is present, assume 3. If present, this must be a positive integer. If minimum_parts_per_bonus is present, this must be greater than or equal to minimum_parts_per_bonus.
points_per_bonus_part Number The number of points earned for a correct answer to one bonus part. Omitting this while specifying maximum_bonus_score means that the number of points needn't be the same for all bonus parts. If present, this must be a positive integer. If bonus_divisor and this are both present, they must be consistent.
bonuses_bounce_back Boolean true if the non-controlling team has an opportunity to answer parts of a bonus that the controlling team did not answer correctly; false if not. If omitted but maximum_bonus_score is present, assume false.
lightning_count_per_team Number The number of lightning rounds received by each team in each game. If omitted, assume 0.
maximum_lightning_score Number The maximum possible score on a single lightning round. If omitted but lightning_count_per_team is present and positive, assume 100.
lightning_divisor Number The largest integer that is guaranteed to be a factor of a valid score on a single lightning round. If omitted but lightning_count_per_team is present and positive, assume 10. If present, must be a positive integer.
lightnings_bounce_back Boolean true if the non-controlling team has an opportunity to answer parts of a lightning round that the controlling team did not answer correctly; false if not. If omitted but lightning_count_per_team is present and positive, assume true.
answer_types Array AnswerType The different answer types possible in this tournament.