PLATINUM DOCS

Audit log

The record of actions in your org — who did what, and when.

The audit log records account and sandbox management actions in your org. Each event stores the actor, the action, the target, and the time. Read it in the dashboard Audit tab or over REST.

Query the log

Only org owners and admins can read the log. Other members get 403.

The SDKs have no typed wrapper for audit. Use the generic request method.

const events = await client.request(
  "GET",
  "/v1/audit?action=sandbox.&status=denied&limit=100",
);
events = client.request(
    "GET",
    "/v1/audit?action=sandbox.&status=denied&limit=100",
)
pt api /v1/audit --query "action=sandbox." --query "status=denied" --query "limit=100"
curl -s "$PT_API_URL/v1/audit?action=sandbox.&status=denied&limit=100" \
  -H "Authorization: Bearer $PT_TOKEN"

Filters

ParamMeaning
qSubstring match on action or resource id
actionAction prefix match (sandbox., org.member)
actorExact actorUserId
statusok | denied | error
since / untilTimestamp bounds (ISO-8601)
limit / offsetPagination — limit 1–200, default 50

Event fields

Some system rows have null actorType / status / source. The status=ok filter still matches them.

Recorded events

The log covers account and sandbox management. It records code execution as an event. It does not record file operations or network traffic inside a sandbox.

Retention

Each org keeps its most recent 10,000 rows for up to 90 days. The platform removes older or excess rows automatically.

Logs inside a sandbox

The audit log does not stream process output. Capture stdout / stderr with exec. Watch file changes with the filesystem watch API. Receive lifecycle events with webhooks. Or attach an interactive terminal.