https://sandbox-api.nuvante.ioRole guide
Administrator guide
For central bank observers, supervisory staff and Nuvanté operations. You get full visibility into what's happening on the platform, without the ability to initiate transactions.
What this covers
Administrators usually hold viewDashboard, viewAuditLog and viewReserves, and don't hold initiateTransaction. You can see everything that moves but can't start anything yourself. There's quite a lot you can do with that access, and this guide walks through it.
What you can check for yourself
- Reserve compliance. A pass or fail check of declared reserve figures against policy, published separately from the reporting dashboard. It isn't a cryptographic proof yet. Zero-knowledge reserve proofs explains how it works today and what's still pending (D-6). That page was written with administrators in mind.
- The full saga history of every transaction. You can see each step a transaction took along with where it is now, which helps you understand why something parked.
- Compliance agent history for any flagged transaction. Agentic compliance explains what the history contains and why it's kept as an auditable chain of checks.
- Aggregate exposure and volume, handy if you're tracking transaction caps and daily limits.
Where to look
- Parked transactions and the reason they parked: check
details.reasonon the transaction resource, and compare it with the normalised events. - Reserve state:
GET /api/v1/reservesgives the reported figures, andGET /api/v1/reserves/{issuerId}/proofgives the verifiable claim behind them. - The full audit trail: this lives in the admin console. Ask your Nuvanté account team for console access scoped to your supervisory role.
What you can call from the API vs the console
Not everything an administrator can do is available on the integrator API. This table shows what you can call with an API key or SDK, and what needs a console session.
| Action | API | Console | Scope or capability needed |
|---|---|---|---|
| List transactions | ✓ GET /api/v1/transactions | No | transactions:read |
| View dashboard summary | ✓ GET /api/v1/dashboard | No | viewDashboard |
| View reserves | ✓ GET /api/v1/reserves | No | viewReserves |
| Generate or verify a reserve proof | ✓ POST /api/v1/reserves/{id}/proof/generate | Also in the portal | generateReserveProof (issuers only) |
| View audit log | ✓ GET /api/v1/audit | Also in the console, with richer filters | viewAuditLog |
| List participants and issued assets | ✓ GET /api/v1/participants | No | viewParticipants |
| Override a parked transaction | Admin API only (overrideTransaction) | ✓ Nuvanté ops console only. Participant API keys can't do this. | Platform-operator role |
| Adjust reserve figures | Admin API only | ✓ Console, with manageAccounts | manageAccounts |
| Onboard or delete a participant | Admin API only | ✓ Nuvanté ops console | Platform-operator role |
| Invite or revoke team members | ✓ POST /api/v1/team/invitations (portal session) | Also on the portal Team page | manageOwnTeam |
| Arm conformance scenarios | ✗ Needs a JWT session | ✓ sandbox.nuvante.io/conformance | runOwnConformancePack (tenant admin) |
"Admin API only" means the action is available through the /api/v1/admin/* routes with a platform-operator JWT session. Participant and integrator API keys can't reach those routes.
Next
Read Reserve proofs to see exactly what you can verify yourself and how. If you haven't yet, read Platform concepts too.