Creating the First Tenant
Tenants are registered through the Platform Admin API on the platform service. These calls carry the operator bearer token obtained through operator sign-in. Schemas are in the Platform Admin API reference.
Register the tenant
Registration creates the tenant with an owner account. Owner credentials are delivered by email in production; the example below disables delivery:
- Overview
- Request
- Response
01 Register tenant
Endpoint: POST /api/platform/admin/v1/tenants
Captured response: 201 Created
This captured endpoint is shown from the E2E run; it is not mapped to one of the generated EDK REST API reference pages.
The tenant identifier returned here is used in every tenant-scoped call that follows:
- Overview
- Request
- Response
02 Get tenant
Endpoint: GET /api/platform/admin/v1/tenants/00000000-0000-4000-8000-000000000002
Captured response: 200 OK
This captured endpoint is shown from the E2E run; it is not mapped to one of the generated EDK REST API reference pages.
Public protocol endpoints
Each tenant binds the public hosts and path prefixes under which its issuer and verifier are reachable. Wallets resolve issuer metadata and verification requests through these endpoints, so they must match your ingress configuration:
- Overview
- Request
- Response
03 Bind issuer public endpoint
Endpoint: PUT /api/platform/admin/v1/tenants/00000000-0000-4000-8000-000000000002/public-endpoints/OID4VCI_ISSUER
Captured response: 200 OK
This captured endpoint is shown from the E2E run; it is not mapped to one of the generated EDK REST API reference pages.
- Overview
- Request
- Response
04 Bind verifier public endpoint
Endpoint: PUT /api/platform/admin/v1/tenants/00000000-0000-4000-8000-000000000002/public-endpoints/OID4VP_VERIFIER
Captured response: 200 OK
This captured endpoint is shown from the E2E run; it is not mapped to one of the generated EDK REST API reference pages.
- Overview
- Request
- Response
05 List public endpoints
Endpoint: GET /api/platform/admin/v1/tenants/00000000-0000-4000-8000-000000000002/public-endpoints
Captured response: 200 OK
This captured endpoint is shown from the E2E run; it is not mapped to one of the generated EDK REST API reference pages.