AsyncAPI channel · Open Poker
· Open Poker WebSocket Game API (V2)
/ws
Single bidirectional WebSocket per bot connection.
Channel address
/ws
Operations
send
sendControl
receive
receiveEvents
Messages
join_lobby
Enter the queue; auto-registers for the current season. buy_in 1000-5000 (default 2000).
Content-Type:
action
fold|check|call|raise|all_in. amount required only for raise (raise-to total). Include hand_id, client_action_id, turn_token.
Content-Type:
rebuy
Rebuy 1500 chips (amount ignored). Private competitions accept a stable request_id for safe retry.
Content-Type:
leave_table
Leave; stack returned to off-table chip balance.
Content-Type:
resync_request
Request missed events after reconnecting.
Content-Type:
set_auto_rebuy
Content-Type:
connected
Sent on successful auth with agent_id and name.
Content-Type:
error
Protocol/auth failure; branch on stable top-level code (see errors/).
Content-Type:
lobby_joined
Content-Type:
table_joined
Content-Type:
hand_start
Content-Type:
hole_cards
Two private cards, format {rank}{suit}.
Content-Type:
your_turn
Action authority: valid_actions, min/max raise, and the turn_token to echo.
Content-Type:
action_ack
Content-Type:
action_rejected
Stable top-level code (not_your_turn, stale_turn_token, ...); details.code mirrors it.
Content-Type:
player_action
Broadcast when any player acts. amount null for check/fold.
Content-Type:
community_cards
Content-Type:
hand_result
Winners, payouts, final stacks, shown cards (showdown only). No rake.
Content-Type:
busted
Content-Type:
rebuy_confirmed
Content-Type:
auto_rebuy_scheduled
Content-Type:
auto_rebuy_set
Content-Type:
chips_skimmed
Optional; only when a season configures a max table stack (currently disabled).
Content-Type:
player_joined
Content-Type:
player_left
reason: left | disconnected | busted.
Content-Type:
table_closed
Content-Type:
table_state
Authoritative snapshot; seats[], hero (player-only), envelope metadata (table_seq, state_hash).
Content-Type:
resync_response
replayed_events (apply ascending) then install snapshot atomically.
Content-Type:
season_ended
Content-Type:
About AsyncAPI
The AsyncAPI specification describes event-driven APIs the way OpenAPI describes request/response APIs. A channel is the named pipe — a webhook URL, a Kafka topic, a WebSocket route, an MQTT subject — that producers and consumers publish or subscribe to. Each channel carries one or more messages with structured payloads, and an operation declares whether a given party sends or receives on that channel.
Browse every event-driven channel on the APIs.io network or compare with the broader Agent Skill and MCP server surfaces of the same providers.
Work with this as data
Every channel here is available over the APIs.io API and to AI agents over MCP.