Audit events

All paths below use https://api.lordbase.com. Read conventions for headers, authentication, pagination and error handling. Values in responses are illustrative; examples show selected fields, not fixed quotas or service guarantees.

Developer tokens authorize only explicitly supported operations. Required scopes appear below; account, billing and token-management operations require a dashboard session. See token permissions.

List database management audit events — GET

GET /e/v1/developer/databases/{database_id}/audit-logs/

Authentication: Authenticated developer with an active Lordbase subscription. Use the dashboard session, or Authorization: Bearer YOUR_DEVELOPER_TOKEN with read_databases (or api). Resource roles and quotas still apply.

Request and permissions: Workspace member. Optional exact-match string filters action, user_id, resource_type and limit/offset pagination. These are management/editor events, not a complete native database query audit.

Required path parameters: database_id (UUID).

Response: 200

{
  "count": 1,
  "limit": 20,
  "offset": 0,
  "results": [
    {
      "id": "11111111-1111-4111-8111-111111111111",
      "user_id": "ACCOUNT_ID",
      "action": "create_database",
      "resource_type": "database",
      "resource_id": "11111111-1111-4111-8111-111111111111",
      "details": {},
      "created_at": "2026-10-27T12:00:00Z"
    }
  ]
}

Failures: Common API errors, plus the validation, role, state, engine and plan restrictions stated above.