Choose your API path
PokerWorks APIs are organized by trust model, but developers arrive with outcomes in mind. Start with the outcome you want, then use the docs path and credentials for that surface.
Run a PokerDeck poker room
Use the Management API when you want to create a room, publish tournaments, wire webhooks, verify tournament results, or automate support evidence from trusted server code.
Start with PokerDeck poker rooms, then use Automate with a service account and the Management API Reference.
Automate operations
Use a service account when CI, a back-office workflow, or an approved agent needs to manage projects, product keys, rooms, webhooks, usage, billing, or audit evidence.
Start with Service accounts & management tokens.
Build a branded poker site
Use PokerWorks as the hosted social-poker platform while your site owns the surrounding front end. Your server creates rooms, tournaments, and short-lived embed sessions; the browser receives only the documented short-lived runtime credential for that launch flow.
Start with Embed a club lobby, then add Webhooks and Tournament results & verification.
Automate tournament outcomes
Use bounded tournament resources, tournament.completed webhooks, and tournament result
verification reads when you need Discord announcements, Google Sheets exports, public result pages,
or support evidence after a tournament finishes.
Start with Recipes.
Build room widgets or leaderboards
Room member lists and tournament entry reads are Management API projections for trusted servers. Room leaderboards are also available as trusted-server Management reads. Standings beyond that published board pack, aggregate stats, and browser-callable widget-safe summaries remain a reserved read-first journey. For beta, build widgets from your trusted server using the admitted reads, webhooks, tournament result verification reads, and your own visibility rules. Do not embed management tokens or product keys in browser, mobile, stream overlay, or third-party widget code.
Future room widgets will need privacy, freshness, visibility, erasure, and object-authorization rules before they become public endpoints.
Build tools, widgets, or AI helpers
Use the Calculation API when you need stateless poker math: equity, ICM deals, payouts, blind structures, starting stacks, and safe explanations around those results.
Start with Get started or Calculation API overview.
Explore certified clients, bots, or arenas
Custom gameplay clients, bot seats, realtime table protocol, and arena-style integrations are not self-serve beta APIs. They need a separate certified Game Server / Table Protocol posture, including server-enforced legal actions, information-set controls, fair-play telemetry, and player protection.
Beta rule
The API reference documents implemented endpoints only. If an outcome is listed as reserved, do not infer an endpoint shape from the product vocabulary. It must pass the platform admission process, including authority, privacy, fair-play, abuse, support, and lifecycle checks, before it becomes a public route, schema, webhook, SDK method, CLI command, or MCP tool.
Common naming boundaries
- Room is the customer-facing PokerDeck poker room resource. Internal runtime tenancy is not a public API noun.
- Tournament is the host-facing bounded poker object in beta. A published tournament can materialize a runtime tournament or Sit & Go instance; recurrence, series, occurrences, and runtime instances remain separate internal or reserved layers until admitted.
- Lobby, ring game, waitlist, table activity, and player session are either runtime/read companions, internal product concepts, or reserved future resources until their player-identity and gameplay authority rules are admitted. Tournament entries are admitted as a read-only Management API projection only.
- Calculation covers stateless compute and explanations. It must not blur into live action advice, HUD/RTA, solver-like recommendations, or bot-driving output for a human seat.
Start here
- To operate a PokerDeck room, start with PokerDeck poker rooms.
- To automate server-side work, start with Automate with a service account.
- To make a quick first call, start with Get started.
- To inspect implemented endpoints, use the API reference hub.