Getting Started
Overview
What operators build and how the Mini App integration is structured.
Overview
OpenPoly Mini App lets an operator embed Opinion market trading and shared Polyflight rounds while keeping operator-owned wallet balances and webhook receivers.
Operator responsibilities
- Call
POST /api/operator/launchfrom your backend - Implement
GET /balance,POST /debit,POST /credit, andPOST /debit-reversalwith durable mutation idempotency - Receive signed webhook events
- Configure staff access, API keys, callback endpoints, Opinion visibility, and enabled-product reporting in the operator dashboard
- Run staging drills before production launch
OpenPoly responsibilities
- Mini App UI for Opinion and Polyflight
- Operator API surface
- Product-specific quote/execution and shared-flight proof
- Opinion settlement plus dedicated Polyflight native-IDR statements/liabilities
- Signed webhook delivery
- Operator dashboard
Environment model
The integration contracts use stable paths across staging and production. Credentials, hosts, records, product enablement, and rollout availability are environment-specific; staging simulator routes are not production APIs.
Documentation describes the current source contract, not proof of deployment or production approval. Confirm availability with Polynion before relying on an unreleased feature.
Find the right operational view
| Question | Start here |
|---|---|
| Did the user gain or lose actual wallet cash on a resolved Opinion market? | Market PnL, not resolution exposure or monthly settlement. |
| Which Opinion wallet outcomes still need evidence? | Cash Flow Triage and the original wallet ledger. |
| Did a callback reach the receiver? | Webhook Deliveries; delivery success is not a wallet payment. |
| What is owed between operator and Polynion? | Opinion reports or Polyflight statements, separately. |
| How do staff raise an incident? | Operator Support; API keys cannot access conversations. |
| Can an operator request its own market? | Market Requests, subject to rollout, approval, and explicit operator underwriting. |