Everything that ever happened to one record
const url = 'https://beta-api.plune.ai/v1/audit/test_case/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/test_case/example \ --header 'Authorization: Bearer <token>'The “History” of a case, a suite or a run on its own page (api.ts → the detail screens): every entry that names this record, newest first, each with before/after and who did it. The entity kind is in the path because ids are not unique across tables; an unknown kind is refused with the five that exist. A record that was deleted still has its history — that is where the deletion is.
Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”Responses
Section titled “ Responses ”The record’s history, newest first
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
Unknown entity kind
object
Example generated
{ "error": "example"}