Audit logs

LocalMind records a product-neutral audit trail of who did what, to which resource, with what outcome. It is the backbone behind audit-logs:read and the platform:override accountability guarantee.

What is recorded

Each entry captures the actor (user or API key), the action (dot-notation, e.g. project.updated), the resource type and id, the outcome, and request context — IP, country, request id and session id.

Scopes

There are three read surfaces, each behind its own authorization:

Your own activity — GET /api/v1/users/me/activity-logs
A project's activity — GET /api/v1/projects/{projectId}/activity-logs (project members)
Platform-wide — GET /api/v1/admin/activity-logs (operators with audit-logs:read)

Querying

All three accept the standard list grammar — page and limit for pagination — plus filters for level, resourceType, outcome and a date range:

Shell

curl "https://api.localmind.app/api/v1/projects/$PROJECT_ID/activity-logs?limit=20&level=warn" \
  -H "Authorization: Bearer $LOCALMIND_API_KEY"

JSON

{
  "data": [
    {
      "actorEmail": "ava@acme.example",
      "action": "member.added",
      "resourceType": "project",
      "outcome": "success",
      "createdAt": "2026-07-24T09:12:04.000Z"
    }
  ],
  "meta": { "pagination": { "page": 1, "limit": 20, "total": 1, "pageCount": 1 } }
}

Entries are export-ready as CSV or JSON from the activity views in the dashboard.