Get session value

Get session value reads a value from session-scoped storage by key. This operation is available only after successful Initialize.

Reads from session cache

This operation reads data from the same volatile per-session cache used by Set session value. Cached values are not persisted and are not shared across sessions.

Request

Get session value uses packet type = 13.

{
  "type": 13,
  "id": 14,
  "key": "launcher_token"
}

Prop

Type

Response

{
  "id": 14,
  "status": 1,
  "value": "abc123"
}

Prop

Type

Behavior notes

Request and response are regular text JSON websocket frames.
Storage is session-scoped; values are available only inside the current session.
Value lifetime is limited by session lifetime and per-key TTL configured during Set session value.
If key is missing or expired, server returns StoreValueNotFound.
On non-OK statuses, value is omitted.
Reading a value does not extend its TTL.

Get-session-value statuses

Status	Constant	Returned when
`1`	`Ok`	Value was found and returned.
`700`	`StoreValueNotFound`	Key does not exist in current session cache or value already expired.

Connection-close cases (before/around this usecase)

Get session value itself returns regular JSON responses, but session can still be closed by protocol/session guards:

Close code	Error	When it happens
`4200`	`connection is not initialized`	Request was sent before successful `Initialize`.
`4201`	`rate limit hit`	Global per-session packet rate limit was exceeded.
`4302`	`invalid request body`	Packet body does not match the required schema for this operation.
`4304`	`received unsupported data`	Client sent unsupported frame type (request packets must be text JSON).