First API call & collections
PokerWorks has three beta first-call paths:
| Path | First proof | Credential |
|---|---|---|
| Browser-safe public read | Open an explicitly public tournament result permalink. | No bearer secret. |
| Calculation API | Call Hold'em equity with a test product key. | Server-side pw_test_.... |
| Management automation | Run the room, webhook, playground, and tournament result loop. | Server-side pw_mgmt_.... |
There is no publishable browser key. Browser, mobile, stream overlay, and embedded code must not
hold pw_mgmt_, pw_test_, or pw_live_ bearer credentials.
Browser-safe read
The first browser-safe public read is:
Code
It is safe only for results whose visibility is explicitly public. Future schedules, public standings, browser-callable room widgets, and streamer overlay snapshots remain read-first candidates until their visibility, cache, freshness, CORS/origin, rate-limit, and support rules are admitted. Room leaderboards are currently server-side Management reads, not public browser reads.
Server-side calls
Use Get started for the quickest Calculation API cURL call.
Use Automate with a service account when you want to create rooms, publish tournaments, receive webhooks, or verify tournament results from trusted server code.
Generated collections
The beta collections are generated Postman v2.1 artifacts:
They are generated from public contracts:
- Calculation API OpenAPI;
- Management API OpenAPI;
- developer webhook manifest;
Collections must be split by credential class and must not contain hand-maintained routes, scopes, event types, or examples that are absent from the public contracts.