Application API

Topolo Admin

Clear API and contract surface for Topolo Admin, grouped under the application instead of split across generic reference sections.

curated srv_SySYzmlOH5H1

Documentation Map

Authority

Service IDs:

srv_SySYzmlOH5H1

Repos: PlatformApplications/TopoloAdmin

Hosts:

https://admin.topolo.app https://topoloadmin-staging.pages.dev

Dependencies: topolo-auth, applications-packages

Depends on Topolo Auth: yes

Contract Source

Type: curated

Source: PlatformApplications/TopoloDocs/src/content/public/applications/admin.mdx

Source exists: yes

Canonical admin coverage now lives in the docs application. Admin first-party embedded password login completes through Admin-owned router navigation after shared Auth token persistence rather than a shared hard document redirect. Admin keeps same-tab sessionStorage access-token restore enabled by default after login and refresh so normal reloads do not appear logged out before cookie refresh completes. Service detail views expose app-centric organization and user assignment or revocation while Auth remains the source of truth for organization-service and user-service access evaluation. User detail views now use Auth's seat-assignment entitlement model for launchable applications: org-included apps stay enabled for everyone, while seat-based apps can be assigned or unassigned by same-org admins only when seats are available. Organization service-assignment views consume Auth service surface metadata so launchable applications are separated from API, runtime, and internal technical services, and the Available Services add flow excludes developer-owned third-party apps marked as organization-internal. Admin now classifies non-org identities from Auth principal metadata plus membership summaries instead of `orgId = null`, treats households as connected personal-account collections rather than separate identity principals, and surfaces Auth-backed org billable-seat summary plus TopoloOne billing preview and billing portal actions in the add-user and organization-detail flows. Admin exposes `GET /api/widget` as a stats widget for TopoloOne live workspace, with platform-admin versus org-admin counts aligned to the Admin dashboard.

API key scopes in Auth catalog: 22

Auth Requirements

No global OpenAPI security scheme is declared.

  • analytics.read
  • billing.read
  • billing.write
  • branding.read
  • branding.write
  • dashboard.read
  • developers.read
  • developers.write
  • organizations.read
  • organizations.write
  • security.read
  • security.write
  • services.read
  • services.write
  • settings.read
  • settings.write
  • support.read
  • support.write
  • system.read
  • system.write

Runtime and Deployment

Wrangler surfaces: PlatformApplications/TopoloAdmin/wrangler.toml

Environment variables: AUTH_API_URL

Routes: workers.dev or Pages-only delivery

Observability enabled: yes

README-Derived Interface Surface

Source: PlatformApplications/TopoloAdmin/README.md

No route-level highlights were extracted from the current README.

Package Surfaces

topolo-admin

No package description recorded.

Source: PlatformApplications/TopoloAdmin/package.json

Scripts: dev, build, build:clean, build:dev, build:staging, preview, lint, lint:full, typecheck, verify:pre-demo, deploy, deploy:staging

Runtime Surface

Wrangler surfaces: PlatformApplications/TopoloAdmin/wrangler.toml

This application does not yet have a source-controlled OpenAPI spec in the docs platform. The current API page is derived from the registered contract source and repository surface.