How the API works
The PokerWorks API origin is:
Code
PokerWorks APIs use /api/v1/** as the public versioned root. Calculation API routes live under
/api/v1/calculations/**, with usage and health reads at /api/v1/usage and /api/v1/health.
Management API routes live under /api/v1/management/**; the management segment marks the
service-account control plane. The public contracts and docs are the authority for external
clients.
API families
- Calculation API — product-key (
pw_test_/pw_live_) calculation endpoints under/api/v1/calculations/**, with usage and health reads at/api/v1/usageand/api/v1/health. The generated Calculation API Reference is the OpenAPI source of truth for this family. - Management API — service-account-token (
pw_mgmt_…) automation for projects, product keys, PokerDeck poker rooms, webhooks, playground completions, and tournament result verification reads. These routes live under/api/v1/management/**during beta and are documented in Automation & management.
Authentication
Requests use bearer credentials. Create and manage product keys and service-account management tokens in the console — secrets are hashed at rest, scoped to your organization or service account, revocable, and shown once at creation.
Code
The response envelope
Every calculation response comes back in the same envelope, so you can handle results uniformly:
- the computed
result; - the calculation method;
- the runout or iteration count;
- a margin estimate where Monte Carlo is used;
- the engine identifier;
- validation and caveat notes when relevant.
Errors
Errors are stable, typed, and safe to show to developers. They explain how to fix invalid inputs without leaking internal route names, stack traces, or organization state. See Errors & troubleshooting.
Rate limits and metering
The API meters usage against a credit ledger. Successful calls draw down credits; validation and auth failures are never charged. Free credits get you started, and you top up your credit wallet in the console when you're ready for production traffic. Requests fail closed with a clear, machine-readable error when credits or rate limits are exhausted.