Admin Console & Operator APIs
The Admin Console is the browser UI for platform operators and tenant administrators on an EDK enterprise deployment. It is served at:
https://platform.<base-domain>/admin-console
Everything you can do in the console is backed by gateway REST APIs (Platform Admin, Platform Config, KMS, DID, credential design, status lists, DCQL, and more). This documentation set is the twin of those two surfaces:
| Path | Use it when |
|---|---|
| Guides | You have a job to finish (keys, designs, issue, verify, …) |
| Console reference | You need every screen, area, and tab explained |
| REST APIs | You need full request/response schemas (Scalar) |
| Enterprise deployment walkthrough | You are installing or first-running the platform |
Dual path: console and REST
Lifecycle guides show each step two ways: Admin Console (nav path, deep link, screenshot, clicks) and REST API (gateway HTTP, static captures from the enterprise e2e gate, optional live Run when an environment is connected).
The browser console uses a same-origin BFF (/admin-console/api/*) and keeps OAuth tokens server-side. Scripts, Postman, and the docs live playground call public gateway paths (/api/kms/v1/..., /api/platform/admin/v1/...) with a bearer token.
Audience
Platform operators after setup and license activation, tenant administrators configuring issuer, verifier, KMS, designs, and trust, and integrators who prefer REST or automation.
Start here
Open the console, then Navigation model, Using the REST APIs, and Environments and live API. First lifecycle guide: Keys and DID.
Screen inventory lives in the frontend screen catalog (packages/admin-console/docs/screen-catalog.json) so new console tabs cannot ship without a docs id.