Every change of one session, oldest first
const url = 'https://beta-api.plune.ai/v1/audit/sessions/example';const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://beta-api.plune.ai/v1/audit/sessions/example \ --header 'Authorization: Bearer <token>'A session is one agent run — every write it made carries the same sessionHash. The Activity screen opens a grouped row into this list; it is also the preview of what POST /v1/audit/sessions/{hash}/restore would undo, in the order it was done. An unknown hash is an empty list, not a 404: a session that wrote nothing and one that never existed look the same, and neither is an error.
Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”Responses
Section titled “ Responses ”The session entries
object
object
A bearer token WITH a session header is an agent; without one it is a token; a session cookie is a user.
For a token this is the TOKEN id — when one leaks, the question is what that credential did.
Keyed with the deployment secret, so one client cannot compute another’s.
Only the fields that moved. A field whose NAME says it holds a credential is masked, though the fact that it changed is still recorded.
object
object
object
False when the diff was truncated — the previous values were not kept in full.
On a restore entry: the entry it undid.
Example
{ "entries": [ { "entity": "test_case", "action": "create", "actorType": "user" } ]}No / invalid token or session