Applications and sessions

An application is an agent entry point loaded by the server. A session stores one user’s interaction state and events for that application. Discover the application name, create a session, and use the returned id for calls and session management user_id separates session namespaces; it does not authenticate the caller. See Agent API Server overview for startup and access control. Harness deployments use their corresponding session endpoint

Method	Path	Endpoint
GET	`/list-apps`	List applications
GET	`/health`	Health check
GET	`/apps/{app_name}/users/{user_id}/sessions/{session_id}`	Get a session
POST	`/apps/{app_name}/users/{user_id}/sessions`	Create a session
DELETE	`/apps/{app_name}/users/{user_id}/sessions/{session_id}`	Delete a session
GET	`/apps/{app_name}/users/{user_id}/sessions`	List sessions
GET	`/version`	Get server version
PATCH	`/apps/{app_name}/users/{user_id}/sessions/{session_id}`	Update session state
POST	`/apps/{app_name}/users/{user_id}/sessions/{session_id}`	Create a session using a path ID
GET	`/apps/{app_name}/app-info`	Get application information

Agent API Server 接口

Harness Runtime 接口