Tournament payouts

Generate a payout schedule for a tournament: how much each finishing position wins. The number of paid places can be fixed or derived automatically from the field size.

POST /v1/calculations/tournaments/payouts

Smallest runnable example

Code
curl https://api.pokerworks.io/v1/calculations/tournaments/payouts \
  -H "Authorization: Bearer pw_test_…" \
  -H "Content-Type: application/json" \
  -d '{
    "entrants": 120,
    "paidPlaces": "auto",
    "prizePool": { "entryValue": 100 },
    "rounding": { "mode": "nearest-unit", "residualPolicy": "first-place" },
    "style": "standard",
    "unit": "USD"
  }'

Important inputs

• entrants — the number of players in the field.
• prizePool — an object with entryValue, plus optional fee, addOnTotal, guarantee, or overrideTotal.
• paidPlaces — "auto" or a positive integer up to 10_000.
• rounding — { "mode": ..., "residualPolicy": ... }.
• style — friendly, standard, competitive, winner-take-all, or satellite.
• unit — chips, points, units, USD, EUR, GBP, AUD, or CAD.

Rounding modes are auto, exact, nearest-unit, nearest-5, nearest-25, nearest-ten, nearest-hundred, nearest-500, and nearest-thousand. Residual policy is first-place or spread. Optional manualEntries, fieldRange, and outcomeOverrides let advanced tooling tune the generated schedule.

Response highlights

• A payout per place, summing to the prize pool.
• The number of paid places used.
• The standard envelope: requestId, creditsCharged, engine, method, warnings, and result.

result contains entries, summary, advice, characterRead, publishability, optional schedule, input, and meta. Each entry includes position, amount, payoutPercent, optional entryMultiple, and optional note. method.type is deterministic.

Common mistakes

• Forcing more paid places than the prize pool can meaningfully cover.
• Expecting exact even splits — rounding rules redistribute the remainder.

Reference

Full schema and all fields → API reference