Neun Predictions developer docs (v0)
For PAM integrators. Every statement carries a status label, copied from the integration guide:
- [BT] BUILT-AND-TESTED: code and a spec file exist.
- [FO] BUILT-FLAG-OFF: code exists and its flag defaults to
false. - [NB] NOT-BUILT: no code exists. Do not build against it.
Pages generated from committed documents say status: generated and name their source. No dates are promised.
Architecture
- A. Wallet API v1: Neun is the client, the PAM is the server. HMAC both ways. [BT]
- B. Operator API
/v1/s2s/*: the PAM calls Neun with OAuth2 client credentials. Controllers [BT]; realm verifier, scopes, idempotency and problem+json [FO]. - C. Embed SDK and Player API: SDK [BT], not published [NB]; Player API [BT] at
/v1/player/*. - D. Event Connector: webhook or pull feed. [FO]
Money moves only through API A. Events never move money. [BT]
What is released and what is on branches
Only what is on origin/integration/final (9eed38ff) counts as released.
| Item | State |
|---|---|
Contracts wallet-v1, operator-v1, player-v1 | Released |
| Conformance CLI source | Released (source only; no published package) |
| Subscription test endpoint | Released |
Signed webhooks (flag EVENT_SUBSCRIPTIONS_ENABLED) | Released, flag off by default |
| These docs pages | On a branch, not released yet |
Server SDK (@neungaming/predictions-server) | On a branch, not released yet |
| Handover tarballs | On a branch, not released yet |
| Dev overlay | On a branch, not released yet |
| AsyncAPI examples | On a branch, not released yet |
Start with the integration guide (from zero to certified) and the quickstart.