Open Tournament Summary
  • Overview
  • Guiding Principles
  • JSON Object
  • Storage Format
  • Standardized Tournament Summary
    • The Specification
    • spec_version
    • site_name
    • network_name
    • internal_version
    • tournament_number
    • tournament_name
    • start_date_utc
    • end_date_utc
    • currency
    • buyin_amount
    • fee_amount
    • bounty_fee_amount
    • bounty_value_amount
    • initial_stack
    • type
    • flags
    • speed
    • prize_pool
    • hero_player_name
    • player_count
    • tournament_finishes_and_winnings
    • rebuy_cost
    • addon_cost
    • tournament_rebuys
  • speed object
    • <speed_object>
    • type
    • round_time
  • Tournament Finish Object
    • <tournament_finish_obj>
    • player_name
    • finish_position
    • still_playing
    • prize
    • ticket_value
  • TOURNAMENT REBUY OBJECT
    • <tournament_rebuy_obj>
    • player_name
    • rebuys
    • addons
  • String Formats
    • version_string
  • Examples
    • Sample Sit N' Go
    • More coming soon.
  • Contact Us
    • Change Request Process
    • Support
  • CHANGE LOG
    • Change Log
Powered by GitBook
On this page

Was this helpful?

Storage Format

How the JSON is stored on the user's computer.

PreviousJSON ObjectNextThe Specification

Last updated 5 years ago

Was this helpful?

File and File Name Format:

  • All tournament summaries MUST be stored in plain text files.

  • All tournament summary files MUST have an .OTS file extension.

  • Filenames MUST use only ASCII characters.

Other than the above requirements, hand history filenames can be named anything. We recommend including at least the tournament name in the filename.

Tournament Summary Groupings per File

A tournament summary should be written to the tournament player's local computer as soon as the player busts from a tournament and there should be one per file. All of the information for the tournament, that is relevant to the tournament player should be available at that time.

If multiple tournament summaries are requested by a user at a later date then multiple tournament summaries can be included in a single file. When multiple tournament summaries are included in a single file, each MUST be separated by one blank line such as:

{"ots":<standardized_tournament_summary_object_1>}

{"ots":<standardized_tournament_summary_object_2>}

{"ots":<standardized_tournament_summary_object_3>}

If multiple tournament summaries are included in a single file, the resulting file will not be considered "valid" JSON. However, for this standard, it is considered acceptable.

tournament summary JSON object
tournament summary JSON object