Skip to main content
client.getActivityLog(opts?) returns one page of your organization’s agent-activity audit log — every audited contract dispatch (actor, on-behalf-of, contract, function, outcome), reconstructed from the cluster’s append-only ledger. The scope organization is resolved server-side from your session DID: there’s no scope parameter, and a page carries every member’s activity in that org, not just your own.
Page until next_seq is null — never stop on a short or empty page. The node caps how much ledger a single call decrypts, so a page can come back shorter than limit (even empty) while the window still has rows and next_seq is still non-null. Only a null next_seq means the window is exhausted.
Rows come back newest first (descending seq_no). Each ActivityEntry: Params (GetActivityLogOptions), all optional — {} is a valid call: from_ms / to_ms bound the window (Unix ms, inclusive); before_seq is the paging cursor (the previous page’s next_seq); limit is clamped server-side to 1–1000 (default 200). Like execute, this runs the session-payload encryption rather than plain HTTPS — entries carry principal DIDs, so getActivityLog() requires an authenticated session.
Not the same method as getAuditEvents(). getAuditEvents() returns your own audit trail (every actor, PII-bearing action/target/details included) — it’s the right call when you need your own history with detail. getActivityLog() returns your organization’s activity, metadata only (no call arguments or payloads), scoped to every member. Reach for getActivityLog() for an org-wide activity view; reach for getAuditEvents() for your own detailed trail.