Skip to content

List your account activity

GET
/account/activity

Returns the audit log entries that name you, as the person who acted or as the account acted on, newest first, one page at a time.

You need to be signed in; no capability is needed. Without a session cookie or bearer token that identifies you, the answer is 401, whether or not public mode is on. A limit that isn’t a whole number, or a parameter given twice, gets a plain-text 400 before sign-in is checked. After sign-in, a cursor that can’t be read gets 400.

An entry where you acted has role by_me, even when it was about your own account. An entry about your account where someone else acted, or no one was recorded as acting, has role on_my_account. Entries that don’t name you on either side aren’t listed, even when they concern your content: for example, someone else deleting one of your items is recorded without naming your account. This is the audit log, not the activity log that listAdminActivities reads, so actions recorded only there, such as sending a direct message, don’t appear.

Each entry shows its event type and time. Entries for your own actions also include the details saved with them, with no further filtering: depending on the event they can hold ids, capability codes and reasons typed at the time. Entries about your account by someone else leave out the details and who acted. No entry includes the IP address or browser recorded with it.

Pages hold at most limit entries, 50 unless you ask for another number; values below 1 count as 1 and above 200 as 200. When more remain, next_cursor is set: send it back as cursor for older entries. Entries written by one request share a time and come in a fixed order by id, not the order they were written. Each page is read separately, so an entry saved by a request that finished late can sort into a page you have already read, and you won’t see it.

Entries are written on a best-effort basis, so an action can be missing. The audit retention cleanup can delete entries older than their category’s retention period, seven years unless an administrator sets another, except entries on legal hold, so this isn’t a permanent history. Server errors get a plain-text 500.

limit
integer
default: 50 >= 1 <= 200

How many entries per page, 50 if left out; values below 1 count as 1 and above 200 as 200.

cursor
string

The next_cursor from the previous page, to get older entries. Left out or empty, the page starts from the newest; one that can’t be read gets 400.

A page of your activity, newest first.

object
items
required

Up to limit entries, newest first; empty when there are none.

Array<object>

One audit log entry that names you.

object
id
required

The entry’s id, for referring to it. Nothing can be fetched with it.

string format: uuid
event_type
required

What happened, as a dotted event type such as user.password_changed. New types are added over time, so show one you don’t recognise in a readable way.

string
occurred_at
required

When the entry was recorded.

string format: date-time
role
required

by_me when you acted, including on your own account. on_my_account when your account was acted on by someone else, or with no one recorded as acting, such as an automatic cleanup.

string
Allowed values: by_me on_my_account
metadata

The details stored with the entry, on by_me entries only, with no further filtering: an object whose keys depend on the event type, or null where null was stored. Left out on on_my_account entries, and when the stored details can’t be read as an object.

object
key
additional properties
any
next_cursor

Send this back as cursor for older entries. Left out when there are no more.

string
nullable

Malformed request

object
error
required

Human-readable error summary

string
Example
the request could not be completed

Authentication required, missing, or invalid

object
error
required

Human-readable error summary

string
Example
the request could not be completed
Example
{
"error": "authentication required: sign in and retry with a valid session or API token"
}

Unexpected server error

object
error
required

Human-readable error summary

string
Example
the request could not be completed