Sessions within the Janus logically group related Janus resources, tying together the Janus lifecycle into a single Assessment per session. Session set-up is a requirement, and must be done prior to making any other request to the API.
A session is defined as the steps undertaken, in practice and in service, for a measure to create an Assessment. A single assessment is defined as the set of lifecycle steps taken for one rater, at a specific point in time. This means that even if there are multiple raters for a single ratee, or the same rater is taking multiple tests at different points in time, these assessments should be created independently across multiple sessions.
Sessions provide value across the Janus lifecycle by: collecting Janus resources into a single container; relating all calls for a single assessment and thereby clarifying billing; and defining settings for the session, eliminating the need for a subsequent call.
Session requests contain an optional "routingCode" parameter, which is provided for event routing scenarios. It encodes a three-character value into a six-character hexadecimal value within the sessionID itself - this provides calling systems a way of routing received events by region, environment, or workflow, without needing to manage multiple webhooks. This provides a scalable, flexible way to manage routing across systems.
→ See Routing Codes for more information.
The following endpoints are available related to sessions: