Get a person's milestones
/api/audit/milestonesHow many dates of calendar events one VRChat user came to, the date of the event Modbot calls their first moment (firstAt) and of the one that made them a Regular (regularAt), and the visit that ended their latest gap of the welcome-back length or more. Counted from the companion's presence reports, so only people in an instance where a moderator's app was present are counted.
Needs ViewAuditLog, the permission that reads the same arrivals in the audit log.
An API key, made on Settings, API keys. Every key starts with mbk_.
In: header
Query Parameters
Response Body
application/json
application/problem+json
application/problem+json
application/problem+json
curl -X GET "https://example.com/api/audit/milestones"{ "eventsCame": 0, "firstAt": 0, "firstDate": null, "regularAt": 0, "regularSince": null, "backAt": null, "backAfterDays": null}List a person's visits GET
Where one VRChat user has been seen, a visit per row, newest first: the arrival (or "already here" when a moderator's companion arrived after them), the leave when one was seen, `until` (when they left, or the last report from that instance when nobody saw them go), the display name they had, the avatars they were seen changing into, and `seenBy`, the moderators whose companions reported them. Visits are made from the companion's presence reports exactly as the time-in-world figures are, so they only cover time a moderator was in the same instance. Needs ViewAuditLog, the permission that reads the same arrivals and leaves in the audit log. Paged by keyset: send the returned `next` back as beforeStartedAt and beforeId; both are required.
List audit log GET
The merged fact timeline: who did what to whom, and when. One log, discriminated by source (spec 5.9). ViewAuditLog covers moderation and membership history; ViewOperationalLog covers Modbot's own record — logins, settings changes, sync failures. The two are separate permissions and the filter is applied server-side on every query: asking for a type you cannot see omits it rather than refusing the request. Facts carry occurredAt and, when the time is an inference rather than a statement, occurredBefore. `precision` says which, so a window is never rendered as an instant. `account` is one Modbot account's whole history: facts about it — sign-ins, role changes, its password being reset — and facts it did, including every kick and ban pressed in Modbot. Both halves at once, because the log records the first against the subject and the second against the actor, and either alone is half the story. It narrows what you may already see: a caller with only ViewAuditLog gets the account's moderation actions, one with only ViewOperationalLog gets its sign-ins and role changes. `person` is one person's whole history across every account Modbot can tie to the one named: facts about any of them and facts any of them did. `personPlatform` says which platform the id is on: `VRChat` (the default), `Discord`, or `Modbot` for a Modbot account id. Accounts are tied the way GET /api/people/lookup ties them, with your permissions: the linked Discord account needs ViewProfile and the Modbot account needs ViewOperationalLog or ManageUsers, and without them only the account you named is read. `show` narrows to `moderation` (bans, kicks, warnings, turned-down requests, notes, case files, AutoMod and copied bans), `presence` (arrivals, leaves and avatars a companion saw) or `discord` (Discord's own log and every copy between the two platforms). Leave it out, or send `everything`, for all of it. `GET /api/audit/filters` lists which of the three each type is in. `notType` leaves out the types it names, and can be combined with `type`. `world` and `instance` narrow to one world or one VRChat instance number; `category` to Moderation or Operational; `precision` to Exact or Window; `hasActor` to facts somebody is named for, or not; `q` finds a word in the payload, the subject id or the actor id. Paged by keyset. Send the returned `next` back as beforeOccurredAt + beforeId; both are required.