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?

Overview

NextGuiding Principles

Last updated 1 year ago

Was this helpful?

A tournament summary is an outline of all tournament information such as prize pools, players, place of finish and winnings. Much of this information is only available at the conclusion of a tournament. Without a tournament summary, tournament players are not able to accurately track their winnings.

This specification is intended to be an open format that any poker site or network is free to use to ensure that they are providing complete tournament data to their players and the tournament summaries can be consumed via any tool of the customer's choice.

Online Poker Operators

If the specification does not meet your needs for a particular use case, please see the to learn how to submit your recommended changes for review and inclusion into the specification. The specification is versioned to allow for continual improvements.

Third Party Developers

We strongly encourage every third party developer to support consumption of tournament summaries that follow the specification. If you believe that certain information is potentially missing or could be a benefit to be included in the tournament summary, please see the to learn how to submit your recommended changes for review and potential inclusion into the specification. The specification is versioned to allow for continual improvements.

Change Request Process
Change Request Process