Polyflight overview

GET /api/operator/polyflight/overview
Authorization: Bearer {operator_api_key_or_staff_session}

Required scope: polyflight:read.

The authenticated operator is the tenant. There is no operator selector, and activity belonging to another operator is never included. Responses use Cache-Control: private, no-store.

Optional activity window

The interval is half-open: [date_from, date_to). Ticket counts and accepted stake use ticket creation time; fee, position, and clearing totals use accounting-event effective time. The three unpaid-liability totals and unresolvedOperationCount are current totals, not narrowed by the activity window; the optional game filter applies to them too. Invalid or repeated game values return 400 INVALID_GAME.

curl -sS -G \
  -H "Authorization: Bearer ${OPERATOR_API_KEY}" \
  --data-urlencode "date_from=2026-08-01T00:00:00Z" \
  --data-urlencode "date_to=2026-09-01T00:00:00Z" \
  "https://your-beacon-origin.example.com/api/operator/polyflight/overview"

Representative response

{
  "operatorCount": 1,
  "flightCount": 12,
  "ticketCount": 48,
  "userCount": 19,
  "acceptedStakeMinor": "480000",
  "ticketFeesMinor": "24000",
  "signedPositionResultMinor": "-28500",
  "clearingReceiptsMinor": "480000",
  "clearingOutflowsMinor": "76000",
  "clearingNetMinor": "404000",
  "unpaidCompensationMinor": "0",
  "unpaidWinningsMinor": "38000",
  "unpaidRefundsMinor": "10000",
  "unresolvedOperationCount": 1,
  "currencyCode": "IDR"
}

All money values are decimal strings in whole-rupiah IDR minor units: "10000" means 10,000 IDR. Empty activity returns zero counts and "0" amounts rather than a missing payload.

signedPositionResultMinor is the fee-exclusive game result and may be negative. Confirmed clearing is shown separately: it proves wallet movement and is not fee or position income. Outstanding winnings, refunds, and compensations are delivery liabilities, not a reason to change the ticket result.

unresolvedOperationCount counts sent, unknown, and manual_review balance operations, including zero-amount loss deliveries. Loss acknowledgements create no monetary liability or clearing. A rejected payout can instead have a failed operation and a manual_review obligation, so a zero count is not proof that all obligations were delivered. Ticket payment state and monetary liabilities must be inspected separately.

Dashboard and next steps

Open Operator Dashboard → Polyflight for the combined Classic-and-Pro summary, then use Flights, Tickets, Wallet operations, Settlement reports, or Commercial terms for the underlying records. The overview screen does not expose activity-window or game filters; use the API for those slices.

• Flights API
• Tickets API
• Balance operations API
• Settlement reports API
• API, events, and proof

Playground: /api-playground/polyflight?request=polyflight-overview.