Skip to content

Administration APIs

Why This Exists

This document defines API responsibilities for the Administration Domain. It does not define final OpenAPI specifications.

Owner

The owner is the Chief Product Officer and Enterprise Architect.

Business Value

Administration APIs provide controlled access to platform configuration, support workflows, feature flags, audit review, policy configuration, and platform-level controls.

API Groups

API group Responsibilities Example endpoints
Platform Configuration API Manage configuration records and versions. GET /administration/configuration, POST /administration/configuration
Feature Flag API Manage feature flags and rollout state. GET /administration/feature-flags, POST /administration/feature-flags/{flagId}/rollout
Support Case API Create, triage, update, and resolve support cases. POST /administration/support-cases, POST /administration/support-cases/{caseId}/resolve
Tenant Administration API Retrieve admin tenant views by OrganizationId. GET /administration/tenants/{organizationId}
Audit Review API Open, review, and close audit reviews. POST /administration/audit-reviews, POST /administration/audit-reviews/{reviewId}/findings
Governance API Record and inspect governance decisions. POST /administration/governance-decisions, GET /administration/governance-decisions
Policy Configuration API Manage policy configuration records. POST /administration/policy-configurations, POST /administration/policy-configurations/{configId}/approve
Integration Configuration API Manage integration configuration records. POST /administration/integration-configurations, GET /administration/integration-configurations
Admin Dashboard API Retrieve administration dashboard composition. GET /administration/dashboards/{dashboardId}
Admin Action API Retrieve auditable admin actions. GET /administration/admin-actions

API Design Rules

  • Every Administration API must require Identity authorization.
  • APIs must use references for source domain facts.
  • Configuration updates must be versioned.
  • Sensitive integration settings must not expose secrets in responses.
  • Final OpenAPI schemas will be defined later.

Example Policy Configuration Flow

sequenceDiagram
    participant Admin
    participant AdministrationAPI as Administration API
    participant Identity
    participant TargetDomain as Target Domain

    Admin->>AdministrationAPI: Submit policy configuration change
    AdministrationAPI->>Identity: Authorize admin action
    Identity-->>AdministrationAPI: Allowed
    AdministrationAPI->>AdministrationAPI: Version and approve record
    AdministrationAPI-->>TargetDomain: PolicyConfigurationChanged