O
O
Open Hand History
Search…
Overview
Guiding Principles
JSON Object
Storage Format
Standardized Hand History JSON
The Specification
spec_version
site_name
network_name
internal_version
tournament
tournament_info
game_number
start_date_utc
table_name
table_handle
table_skin
game_type
bet_limit
table_size
currency
dealer_seat
small_blind_amount
big_blind_amount
ante_amount
hero_player_id
flags
players
rounds
pots
tournament_rebuys
tournament_bounties
Bet Limit Object
<bet_limit_obj>
Player Object
<player_obj>
Round Object
<round_obj>
Action Object
<action_obj>
Pot Object
<pot_obj>
jackpot
Player Wins Object
<player_wins>
cashout_amount
cashout_fee
bonus_amount
Tournament Info Object
<tournament_info_obj>
Tournament Rebuy Object
<tournament_rebuy_obj>
Tournament Bounty Object
<tournament_bounty_obj>
Speed Object
<speed_obj>
String Formats
version_string
card_string
Examples
Holdem cash hand (iPoker)
Holdem cash hand (PokerStars)
Omaha cash hand (WPN)
Omaha hi/lo cash hand (PokerStars)
Holdem cash hand (888)
Holdem tournament hand (888)
Holdem tournament hand (PokerStars)
Holdem tournament hand (iPoker)
Contact Us
Change Request Process
Support
CHANGE LOG
Change Log
Powered By GitBook
JSON Object
Why we chose JSON.
Every standardized hand history MUST be in a self contained JSON <standardized_hand_history> 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 development libraries across all programming languages.
​
​
Previous
Guiding Principles
Next
Storage Format
Last modified 2yr ago
Copy link