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?

JSON Object

Why we chose JSON.

Every standardized tournament summary MUST contain one standardized tournament summary JSON object.

We chose JSON due to it meeting the following needs:

  • It is plain text and accessible.

  • It is understandable by any person without requiring third party software (other than a text editor).

  • It is structured and the structure can be standardized and documented.

  • It is an efficient structured format.

  • JSON enjoys wide adoption and therefore has development libraries across all programming languages.

PreviousGuiding PrinciplesNextStorage Format

Last updated 5 years ago

Was this helpful?