List logs
List what has been done in your account, newest first.
The account log belongs to the account rather than to you, which matters in one case: an entry the application wrote on its own has nobody behind it, and those are exactly the entries nobody watched happen. Its author reads as the system and it carries no address.
Each entry carries both the raw name of the action, which is what a program matches on, and a sentence in the language on your account, which is what a person reads.
Nothing here can be written, changed or removed. A log that can be rewritten is worth nothing, so there is no endpoint for it.
This endpoint also answers QUERY, with the same parameters sent in the request body. How QUERY works.
Query parameters
Sent as JSON. Anything not listed here is ignored.
Which page to answer with.
How many entries one page holds, between 1 and 100. A number outside the range is brought back into it rather than refused.
Returns
A page of account log entries, and how many there are in all.
The entries on this page. An empty list rather than an error when there are none.
One entry.
Always log. It names the kind of record, so a caller holding several kinds can tell them apart without looking at where they came from.
The id of this record, as a string even when it reads as a number. It is what every endpoint naming this record takes.
Everything the record holds.
Who did it: their name while they are still on the account, the address they had once they are not, and a translated phrase reading The system for anything the product did on its own. Worked out when you ask rather than stored, so a deleted person still reads as somebody.
What was done, as a key such as vault_created or contact_deleted, up to 255 characters. The keys come from a set the product keeps and adds to as it gains capabilities, and the column is a plain string rather than a fixed set, so match the ones you care about and let an unfamiliar one through rather than treating it as an error.
What the action was about, as whatever that kind of action recorded. The keys depend entirely on the action, so nothing here promises a shape: a vault creation carries the name of the vault, another action carries something else.
The entry as a sentence a person can read, with the parameters already put into it. Worked out when you ask, and in the language of whoever is asking.
Where it came from: one of web, api, mcp, import, automation, module or system. It is how a change made by a script is told from one made by hand.
The address the request came from, up to 45 characters so that a version six address fits, or null when nothing was recorded, which is the case for anything the system did on its own.
When it happened, as a count of seconds since 1970. The account log is append only, so this never moves.
Where to find this record.
The absolute address this record is read from.
Where you are in the collection.
The page this is, counting from 1.
How many one page holds, which is the size that was asked for once it has been brought into the allowed range.
How many entries there are in all, not how many are on this page.
Rate limit
Sixty requests per minute, per user, shared by every key and device. Every answer carries the budget left in X-RateLimit-Remaining.
Keys act as you, with exactly the access you have. Make one per integration so you can revoke it alone.