client.getActivityLog(opts?) returns one page of your organization’s agent-activity audit trail — every audited contract dispatch (actor, on-behalf-of, contract, function, outcome), reconstructed from the cluster’s append-only, tamper-evident ledger. This is what you point a compliance team or an auditor at to prove what an agent actually did, not just what it was supposed to do. The scope organization is resolved server-side from your session DID — there’s no scope parameter — and how much comes back depends on your admin standing: an admin gets every member’s activity; anyone else gets only the calls they made, plus the calls their agents made in their name.
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); custom keeps only calls whose labels carry every one of the given key → value pairs (compared exactly; keys and values must not be empty) and has_custom keeps only labelled (true) or unlabelled (false) calls.
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, PII included — use it for your own detailed history. getActivityLog() returns metadata only (no call arguments or payloads), scoped as above — use it for an org-wide activity view.Label a call from your contract
A contract can attach labels to its own activity entry — an approval outcome, a reason code, a workflow id — by returning a top-levelcustom object in its JSON response:
custom off the response, stores the labels that pass the limits on the entry, and returns the rest of the response to the caller without custom. Every other field of the entry stays host-stamped; a label can’t change them.
- Keys: 1–32 characters from
a-z,0-9,_,.,-. - Values: strings only, up to 128 bytes.
- At most 16 labels per entry (extras are dropped in key order).
- A label that breaks a limit is dropped whole, never truncated; the entry is still written. A
customthat is not an object is dropped too.
custom / has_custom above.
Calls a contract makes to other contracts get their own rows. Each
contracts-call invoke made inside a call is written as a separate entry after the outer call’s entry, for the target contract and function, under the same actor, on_behalf_of and origin. An invoke the allowlist, depth or reentrancy gate refused is recorded as denied; one whose target failed is error; and an invoke that returned success inside an outer call that did not commit is recorded as error. The target’s own custom labels travel on its row, and the calling contract still receives them in the response.