The operator dashboard
For bank operations staff who monitor issuance, reserves and activity in the Management Panel.
The reporting views include summary, issuance, recent activity and reserve information. The current documented figures are static demonstration data. They help teams explore the reporting format but cannot establish live reserves, a settled payment or a current operational position.
For daily decisions, use the actual token outcome, settled account balances, approval records and the bank's own cash records. Operations and finance teams should agree the reporting sources and reconciliation controls before relying on a live reporting feed. The dashboard endpoints and their current limitations are set out below.
Understand the views
| View | API Reference | Current use |
|---|---|---|
| Summary | GET /api/dashboard/summary | Inspect the summary response shape; the figures are static. |
| Issuance | GET /api/dashboard/issuance | Inspect instrument/period reporting fields; the values are static. |
| Activity | GET /api/dashboard/activity | Inspect the feed structure; it is not the authoritative activity log. |
| Reserve attestation | GET /api/reserves/attestation | Static reserve, outstanding-token and ratio fields pending a core-banking data integration. |
| Reserve snapshot | GET /api/reserves/attestation/snapshot | Static snapshot response; not a verified live reserve position. |
Reserve amounts currently use JSON numbers. The attestation response includes currency, reserve held, tokens outstanding, ratio, verification flag and date; the presence of these fields does not make a static example an independently verified attestation.
Use authoritative evidence for operations
- Read an operation with GET /api/transactions/{transactionId} and track its actual state.
- Read an account's settled position with GET /api/accounts/{accountRef}/balances.
- Investigate outstanding cases with GET /api/transactions/breaks.
- Use Audit and evidence for recorded activity, and bank-held records for cash reserves and reconciliation.
Integrate a reporting screen
Build the screen around the fields documented in the reference, keeping static demonstration values visibly distinct from live evidence. Confirm Management Panel access and the caller's entitlements for your deployment through Roles and access.
Before using a future live reporting feed, establish its source systems, update cadence, reconciliation controls and the party responsible for reserve attestation. The current contract does not promise a live-dashboard release date. See Limitations.
API Reference
Open an endpoint for request fields, response examples and the interactive API console.
Related pages
Implementation resources
Use Implement a backend client for request handling, durable idempotency and outcome tracking. The developer integration coverage map links every public operation to its API Reference and contract-derived code recipe. Replace example identifiers with values from your assigned environment.
Updated 2 days ago