Recipes
Recipes
Recipes show what you can build with PokerWorks, not just which endpoints exist. Each recipe starts with the customer outcome, then names the required Console setup, scopes, environment, security notes, and current availability.
Launch recipes
| Recipe | Status | Uses |
|---|---|---|
| Embed a club lobby | Closed-beta runnable — approval required | Embed products, spectator embed sessions, allowed origins, maintained starter |
| Discord tournament announcements | Closed-beta runnable | Webhook endpoint, tournament.completed, signed delivery |
| Google Sheets results export | Closed-beta runnable | Webhook endpoint, tournament.completed, signed delivery, Google Sheets append |
| Streamer overlay | Design preview | Public-safe read surface, hosted table state, support bundle |
Recipe template
Every maintained recipe should include:
- Outcome — the practical thing a club, creator, operator, or developer is trying to do.
- Audience — who should use the recipe and who should not.
- Status — runnable, closed beta, first-party-only, or design preview.
- Console setup — project, environment, origins, service account, product key, or webhook endpoint.
- Scopes — management scopes for
pw_mgmt_…tokens and product scopes forpw_test_…/pw_live_…keys. - Steps — the shortest path to a working proof.
- Security notes — where tokens live, which secrets are reveal-once, and what must stay server-side.
- Support bundle — ids to copy when asking for help.
- Limitations — anything not available yet, without hiding it behind optimistic copy.
What not to copy
Do not use recipes to expose first-party-only seams. PokerDeck BFF routes, Drop In anonymous cookies, quick-game host cookies, and raw gameplay action routes are not public developer contracts. If a recipe needs one of those seams, mark that step as first-party-only or wait for the public contract.