Admin Router runs on DC/OS master nodes and exposes the following API routes.

Admin Router listens on port 80 (HTTP) and 443 (HTTPS).

For more detail about how API routing works, see DC/OS API Reference.


    • File /

      DC/OS GUI
    • Proxy /(slave|agent)/(?<agentid>[0-9a-zA-Z-]+)(?<url>.+)

      API proxy to a specific agent node
    • Proxy /acs/api/v1

      Access Control Service
    • Proxy /acs/api/v1/auth/

      Access Control Service (unauthenticated)
    • Redirect /login

      Redirect to OpenID Connect server for user login
    • Proxy /capabilities

      List of capabilities supported by DC/OS
    • Proxy /cosmos/service/

      Start a DC/OS service from a DC/OS package
    • Proxy /marathon/

    • Proxy /mesos_dns/

    • File /dcos-metadata/

      DC/OS metadata
    • File /dcos-metadata/dcos-version.json

      DC/OS version (unauthenticated)
    • Proxy /dcos-metadata/ui-config.json

      DC/OS GUI configuration
    • Lua /metadata

      Public IP and Cluster ID
    • Proxy /navstar/lashup/key

    • Proxy /package/

      Package Management
    • Proxy /pkgpanda/

      DC/OS component package management
    • File /pkgpanda/active.buildinfo.full.json

      List the active Pkgpanda packages
    • Proxy /service/(?<serviceid>[0-9a-zA-Z-.]+)/(?<url>.*)

      Proxy to services running on DC/OS
    • Proxy /system/health/v1

      Component service status
    • Proxy /system/v1/agent/(?<agentid>[0-9a-zA-Z-]+)(?<type>(/logs/v1|/metrics/v0))(?<url>.*)

      System proxy to a specific agent node
    • Proxy /system/v1/leader/marathon(?<url>.*)

      System proxy to the master node with the Marathon leader
    • Proxy /system/v1/leader/mesos(?<url>.*)

      System proxy to the master node with the Mesos leader
    • Proxy /system/v1/logs/v1/

      Node, component service, and container (task) logs
    • Proxy /system/v1/metrics/

      Node, container, and application metrics