Blind structures

Produce a blind-level structure for a tournament — the schedule of small blind, big blind, and ante for each level — shaped to a target duration and level length.

POST /v1/calculations/tournaments/blinds

Smallest runnable example

Code
curl https://api.pokerworks.io/v1/calculations/tournaments/blinds \
  -H "Authorization: Bearer pw_test_…" \
  -H "Content-Type: application/json" \
  -d '{
    "players": 90,
    "startingStack": 20000,
    "targetDurationMinutes": 240,
    "levelDurationMinutes": 20,
    "pace": "standard",
    "anteStyle": "big-blind",
    "rebuys": { "enabled": false, "endsAfterLevel": 1 }
  }'

Important inputs

• startingStack — chips each player starts with.
• targetDurationMinutes — how long the tournament should run.
• levelDurationMinutes — length of each blind level, 5-60 minutes.
• players — 2-200 players.
• pace — gentle, standard, or fast.
• anteStyle — none, big-blind, or classic.
• rebuys — { "enabled": boolean, "endsAfterLevel": number, "expectedRebuysPerPlayer"?: number }.

startingStack must be between 500 and 10_000_000; targetDurationMinutes must be between 30 minutes and 24 hours. rebuys.endsAfterLevel is required even when rebuys are disabled.

Response highlights

• An ordered list of levels, each with small blind, big blind, ante, and duration.
• The standard envelope: requestId, creditsCharged, engine, method, warnings, and result.

result contains levels, summary, advice, input, and meta. Each level includes levelNumber, smallBlind, bigBlind, nullable ante, durationMinutes, optional breakAfter, and notes. summary includes estimated duration, starting/final pressure metrics, total chips, and break/playing minutes. method.type is deterministic.

Common mistakes

• A level length and target duration that imply too few levels to play down the field.
• Expecting round numbers at every level — blinds scale to fit the target duration.

Reference

Full schema and all fields → API reference