Keyban Dashboard
The Keyban Dashboard is the no-code surface above the Keyban platform. It gives administrators and brand teams direct access to every domain object exposed by the backend — Digital Product Passports, loyalty programs, investment funds, organizations, applications, agent wallets and operational metrics — without writing a line of code or a single API call.
Sign in at admin.keyban.io. Every action available in the UI is also reachable from your own backend through the REST API or the SDK.
Who uses it
The dashboard targets four operational personas:
- Org admins provision applications, manage members and rotate API credentials.
- Brand teams (loyalty, product) configure programs, launch campaigns and publish passports.
- Fund managers run the Invest module — funds, holdings, NAV, lockups, offers.
- Tech leads audit quotas, inspect events and supervise agent wallets.
Each section of the UI maps to a resource — a CRUD surface over a backend domain object. Permissions are evaluated server-side per role.
Available resources
The dashboard exposes the following resources today. Each row links to the matching tag in the public OpenAPI reference so you can inspect the underlying endpoints.
| Resource | Purpose | API reference |
|---|---|---|
| Digital Product Passport | Draft, publish, certify and inspect passports — model, batch and item granularity | DPP |
| Loyalty program | Configure currency, earning ratio, redemption table and rewards | Loyalty |
| Invest (fund, holding, identity, lockup, NAV, offer, fund-investor) | Manage tokenised investment vehicles end-to-end | Invest |
| Zelty integration | Register API keys and link applications to point-of-sale terminals | Integrations |
| Onboarding / Pending onboarding | Provision new organizations and finalise sign-up | Billing |
| Plans | Inspect subscription tiers, sync with Chargebee, preview overage | Billing |
| Organizations / Applications / API credentials | Tenant, application and key management | Organizations, Applications |
| Agent wallets | Programmable wallets and policies for autonomous flows | Agent Wallets |
| Shopify integration | Connect a Shopify catalogue, drive passport creation from product metafields | Integrations |
| Point of sale | Configure brick-and-mortar registers tied to a loyalty program | Loyalty |
| Imports | Bulk-upload passports and inspect import jobs | Import |
| Files | Manage uploaded assets (logos, passport images, reward visuals) | Backend OpenAPI |
| LLM / MCP usage | Track LLM calls, providers and quotas | LLM |
| Metrics, quotas, events | Operational visibility on the platform | Metrics, Quotas, Events |
The full OpenAPI reference is also available at /backend-openapi.
Common workflows
Configure a loyalty program
In the matching application, open the Loyalty resource and set the currency, the earning ratio and the redemption table. The configuration is propagated to every front-end consuming the same application — embedded wallet, end-user apps, partner POS. See the On-chain Loyalty introduction for the underlying model.
Issue and certify a Digital Product Passport
Open the DPP resource, draft a passport at the right granularity (model, batch or item), upload images, fill certifiedPaths, then publish. Publication triggers public visibility and the on-chain certificate atomically. See the DPP introduction for the four-step lifecycle.
Manage applications and API credentials
From the Applications resource, create a new application, copy its public identifier and rotate its API credentials. Each application carries its own theme, domain, supported authentication methods and resource access — all editable in place without leaving the dashboard.
Theme and branding
Each application carries its own brand: name, domain, logo, light/dark theme, primary and secondary colours. The configuration is consumed by the embedded wallet and by every Keyban-powered end-user app, so changing it once propagates everywhere. Use the Application resource to update those values; uploaded assets go through the Files resource.
Access control
The dashboard distinguishes two roles inside an organization:
org-admin— full read/write on every resource of the organization.member— read-write scoped per application; access can be further restricted to specific resources.
Permission resolution is server-side: the front-end only renders what the API returns. See the permissions reference for the canonical role matrix.
Where to go next
- Backend API reference — the OpenAPI spec behind every dashboard action.
- On-chain Loyalty introduction.
- Digital Product Passport introduction.
- Permissions — role matrix and resource-level access.