Seal the audit directory for handing over
const url = 'https://api.katara.com/katara/v1/orgs/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/environments/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/audit/exports';const options = { method: 'POST', headers: { cookie: 'katara_session=<katara_session>', 'Idempotency-Key': 'example', 'X-Katara-CSRF': '1', 'Content-Type': 'application/json' }, body: '{"expires_in_seconds":1}'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request POST \ --url https://api.katara.com/katara/v1/orgs/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/environments/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/audit/exports \ --header 'Content-Type: application/json' \ --header 'Idempotency-Key: example' \ --header 'X-Katara-CSRF: 1' \ --cookie katara_session=<katara_session> \ --data '{ "expires_in_seconds": 1 }'Requires the same authority the directory itself requires: current locus:audit:read permission and an owner, admin, operator or reviewer role, held by a person rather than a workload. Seals the directory as it stands into a snapshot that can be read back and handed over until it expires. A scoped key seals only the resources it may already read, so an export can never show an operation the caller could not have listed. At most 10000 operations; a larger directory is refused rather than truncated. The snapshot holds metadata only: no request bodies and no idempotency material. Sealing is itself a recorded operation. Preserve the original key after an uncertain response.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Header Parameters
Section titled “Header Parameters”Browser cookie mutations require value 1 and an allowed Origin. Session bearer clients may omit this header.
Required for cookie-authenticated changes. Use the UUID of the account that loaded the application. A different current cookie account returns account_changed before the handler runs. Session bearer and API key clients do not require this header.
Request Bodyrequired
Section titled “Request Bodyrequired”Seals the audit directory as it stands, for as long as the requested window. There is no start to choose: a caller who could pick one could pick a start that leaves an act out, and an export with a gap in it is worse than no export.
object
Examplegenerated
{ "expires_in_seconds": 1}Responses
Section titled “Responses”The sealed snapshot’s manifest.
object
Example
{ "schema_version": 1, "mode": "test"}Account_changed: reload and review with the signed-in account. Preserve the original key to recover an uncertain committed operation.
default
Section titled “default”Request rejected or unavailable.
object
object
Stable; branch on it. Any operation can answer invalid_request, with param naming the refused field when there is one; human_session_required, when an API key, service account or workload calls an operation only a signed-in person may perform; reauthentication_required, when a person’s sign-in is too old for the operation; permission_denied; route_not_found and method_not_allowed, when no operation matches the path or method; and feature_unavailable, when the operation’s service is not enabled on this deployment.
The request field a refusal is about, such as the agent_id or run_id query parameter; null when the refusal is not about one field.
Example
{ "error": { "action": "sign_in" }}