Chip starting stacks

Plan the physical chips for a live event: which denominations to use and how many of each to put in every player's starting stack, for a target stack size and player count.

POST /v1/calculations/chips/starting-stack

Smallest runnable example

Code
curl https://api.pokerworks.io/v1/calculations/chips/starting-stack \
  -H "Authorization: Bearer pw_test_…" \
  -H "Content-Type: application/json" \
  -d '{
    "startingStack": 20000,
    "startingStackMode": "manual",
    "players": 90,
    "firstSmallBlind": 100,
    "firstBigBlind": 200,
    "targetStyle": "comfortable",
    "denominations": [
      { "value": 25, "color": "green" },
      { "value": 100, "color": "black" },
      { "value": 500, "color": "purple" },
      { "value": 1000, "color": "yellow" },
      { "value": 5000, "color": "orange" }
    ]
  }'

Important inputs

• startingStack — the chip total each player should start with.
• startingStackMode (optional) — manual or big-blinds.
• players — the field size, used to plan inventory.
• firstSmallBlind / firstBigBlind — opening blind level.
• targetStyle — efficient, comfortable, or deep-stack.
• denominations — 1-10 denomination objects with value and optional label/color.

Optional inventory controls include availableSet, rebuyReserve, addonReserve, desiredStartingBigBlinds, and allowReserveDenominationSubstitution. Reserve counts can be fixed or percentage-based.

Response highlights

• A per-player breakdown: how many of each denomination make up the starting stack.
• A total inventory needed across the field.
• The standard envelope: requestId, creditsCharged, engine, method, warnings, and result.

result contains perPlayerStack, startingTotalChips, grandTotalChips, reserve, inventory, summary, advice, input, and meta. Stack entries include denominationValue, label, nullable color, count, and totalValue. method.type is deterministic.

Common mistakes

• Denominations that can't cleanly compose the target stack.
• Forgetting the smallest denomination needed for early blind levels — cross-check with your blind structure.

Reference

Full schema and all fields → API reference