S
S
Standardized 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>
bet_type
bet_cap
Player Object
<player_obj>
id
seat
name
display
starting_stack
player_bounty
Round Object
<round_obj>
id
street
cards
actions
Action Object
<action_obj>
action_number
player_id
action
amount
is_allin
cards
Pot Object
<pot_obj>
number
amount
rake
player_wins
Player Wins Object
<player_wins>
player_id
win_amount
contributed_rake
Tournament Info Object
<tournament_info_obj>
tournament_number
name
start_date_utc
currency
buyin_amount
fee_amount
bounty_fee_amount
initial_stack
type
flags
speed
Tournament Rebuy Object
<tournament_rebuy_obj>
player_id
rebuy_action
amount
chips
Tournament Bounty Object
<tournament_bounty_obj>
player_id
bounty_won
defeated_player_id
Speed Object
<speed_obj>
type
round_time
String Formats
version_string
card_string
Examples
Coming soon
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
1yr ago
Copy link