Approved integrations
Public-safe reads can be low-friction. Account access, player-capable clients, gameplay control, and bulk private exports cannot.
PokerWorks treats these as approved or gated programs until their scopes, consent, review, revocation, data-rights, support, and abuse controls are explicit:
- approved-app OAuth;
- connected clients and player-capable embeds;
- certified custom clients;
- bot credentials and Game Server API / Table Protocol;
- bulk exports and report jobs;
- high-integrity room integrations for leaderboard, sponsor/prize, bot arena, research, or training-assisted tiers.
The beta Management API remains server-side with service-account tokens. PokerWorks does not expose a publishable browser key for management or player-capable access.
What this means for builders
Use public reads, webhooks, result/proof, widgets, recipes, and server-side Management calls that are documented today. Treat OAuth apps, connected clients, Table Protocol, and bulk exports as reserved until an approved program is published.
The canonical policy lives in
docs/architecture/approved-integration-admission-policy.md.