API reference / Sessions
Look at the new sessions now
Troopy reads the sessions since the last look, and a teammate reads the busiest ones. It answers at once with the look that waits: GET /session-looks/{id} shows how it goes. A workspace looks 12 times a day at most, with the schedule. While a look waits or works, this gives that look back.
/api/v1/session-looksOther ways to call it
troopy sessions look-nowResponse
202 · application/jsondata*object12 properties
id*stringA 24-character id
source*enum<string>Where the look read the sessions: troopy, Troopy's own script, or posthog
troopyposthog
state*enum<string>queued, fetching (Troopy reads the source), analyzing (a teammate reads the sessions), done or failed
queuedfetchinganalyzingdonefailed
error*string | nullfrom*stringIt reads the sessions that started from this time on
hours*integercounts*object3 properties
recordings*integerThe sessions that the source had
matched*integerThose that the countries and the paths to leave out kept
analyzed*integerThose that the teammate read: the busiest ones
summary*string | nullWhat the sessions show together
issues*array<integer>The numbers of the problems that it found or saw again
by*string | nullThe person who asked for it. Null: the schedule
createdAt*stringISO 8601 date and time
sessions*array<object>Empty in a list
16 properties
id*stringreplayUrl*string | nullThe replay in Sessions or in PostHog. Null: no replay of the session
replay*string | nullSource troopy: the id of the replay
startedAt*stringISO 8601 date and time
durationSec*integeractiveSec*integerstartPath*string | nullcountry*string | nullclicks*integerkeys*integererrors*integerThe errors that the console of the browser showed
events*integerflow*string | nullWhat the person did
dropOff*string | nullWhere the person stopped
reason*string | nullWhy the person possibly stopped
friction*array<string>