API Sessions represent a client that is either partially or fully authenticated as a specific Ziti Identity.
API Sessions are used to scope authentication and Posture Data.
API Sessions are used to make authorization decisions. Clients interact with
API Sessions via a opaque security token value and is received during authentication via
Sessions represent a client's ability to dial (connect) or bind (host) a service. Clients receive them by request
/edge/client/v1/sessions endpoint. A sessions are service and identity specific. Clients interact with them
as an opaque security token and is provided to Edge Routers during dial or bind requests.