- 6.9
Key Points
- IT Administrators: manage configuration, licensing, servers, and reports through a structured API instead of manual admin workflows.
- External Integrators: use API keys and OpenAPI documentation to connect EO.workspace with reporting, provisioning, and automation systems.
- Platform Teams: monitor API health, database activity, and runtime behavior through authenticated Prometheus metrics.
- Security Teams: control programmatic access with API keys, JWT sessions, permissions, expiry, and key disablement.
Automate EO.workspace Administration With a Secure REST API
Give administrators and integrators a documented interface for operational control.
Enterprise environments need repeatable administration. Manual steps slow down provisioning, reporting, licensing, and operational checks, especially when EO.workspace is part of a larger IT service workflow.
The EO.workspace REST API provides a versioned interface for administration and integration tasks. It supports server information, session reports, system settings, licensing actions, API key management, application data, configuration overrides, EULA acceptance, health checks, and runtime metrics.
For IT teams, this means faster automation, clearer integration contracts, and better operational visibility. For partners and external systems, it provides a documented API surface with interactive Swagger documentation, OpenAPI artifacts, and static HTML documentation for offline or release-based distribution.
⚙️ Built for Automation
Use REST endpoints to connect EO.workspace with provisioning tools, reporting systems, service workflows, and partner platforms. Administrators can manage key operational data without relying only on the graphical console.
🔐 Secure Programmatic Access
The API supports JWT-based sessions for the Admin Console and API keys for external integrations. API keys can be created, listed, enabled, disabled, deleted, assigned permissions, given optional expiry, and tracked through usage metadata.
📘 Documented for Integrators
OpenAPI documentation is generated from the implementation and served through Swagger UI at /eow/api/v1/admin/docs. Static HTML documentation can also be generated for customer-facing or offline distribution.
📊 Operational Visibility Included
Authenticated Prometheus metrics expose HTTP activity, authentication events, database pool status, query behavior, Go runtime data, and process health. This helps platform teams monitor the API as part of normal infrastructure operations.
🧩 Practical Admin Coverage
The REST API includes endpoints for session reports, server lists and details, system settings, licenses, API keys, configuration overrides, application groups, applications, readiness checks, and liveness checks.
🤝 Easier Partner Enablement
When API keys are created, partners can receive direct access to the documentation URL. This reduces integration friction and gives external teams a clearer contract for building against EO.workspace.
Want to See EO.workspace REST API in Action?
Contact us to see how the REST API can support administration, reporting, partner integrations, and operational monitoring in your EO.workspace deployment.
Recommended For You

CIS Virtualizes Bank Branches

NOS Virtualizes Critical Applications






