> ## Documentation Index > Fetch the complete documentation index at: https://docs.ankra.ai/llms.txt > Use this file to discover all available pages before exploring further. # List the organisation audit log with an API token > Bearer twin of GET /org/organisation/audit-logs: the organisation audit log, newest first, paginated with `page` and `page_size` (default 50, at most 200), with the actor, agent and target of each row. Accepts a personal or service-account API token; the token (its scopes and its role) must hold audit.read in the organisation. Same filters as the session listing. The organisation is the token's own, or the one named by the X-Ankra-Organisation-Id header when the token's user is a member of it; a service-account token cannot leave its organisation. The audit trail belongs to the whole organisation: audit.read cannot be held through a project, so a project-only member's token is refused, and a token pinned to a project is refused with 403 whatever its holder's role. ## OpenAPI ````yaml https://platform.ankra.app/openapi.json get /api/v1/org/organisation/audit-logs openapi: 3.1.0 info: title: Ankra Platform API version: v1 description: >- The Ankra platform HTTP contract. The /api/v1 surface is the public, bearer-authenticated API used by the Ankra CLI, MCP clients and automation; send a personal or service API token as `Authorization: Bearer `. Browser routes under /org and /chat are served on api.platform.ankra.app (each declares that server); they and /oauth/access authenticate with the ankra_session cookie, and mutations also require the X-Ankra-CSRF header. Every operation declares the credential it accepts, and no operation is served without one. This document is published deliberately: it describes the contract only and carries no organisation data or credentials. Report security issues to security@ankra.ai (see /.well-known/security.txt). servers: - url: https://platform.ankra.app security: - BearerAuth: [] tags: - name: Onboarding description: >- Generate a first website from a prompt and deploy it to a new organisation's cluster. - name: Access Gate description: >- Private service sign-in and membership checks for trusted Ankra proxy relays. - name: Canvas Datasets description: >- Read the fixed, named datasets canvas dashboards bind their charts, tables and stats to. - name: Canvases description: >- Keep dashboards and pages in the organisation's canvas library, with revision history, undo and pins. - name: Canvas Pages description: >- Publish a chat canvas artifact at a public pages address and take it down again. - name: Cloud Delegation description: >- Platform browser consent and organisation-bound connections for Ankra Cloud. - name: Organisation IAM description: >- Custom organisation roles and scoped role assignments for member and service-account identities. - name: Clusters description: Create, inspect and manage clusters, and the stacks deployed on them. - name: Managed Clusters description: Provider-managed control planes, driven through one common surface. - name: Playground description: >- The organisation's playground cluster: order one, read its provisioning status, list the orderable sizes, resize it and destroy it. - name: Imported Clusters description: Clusters that already existed and were connected to Ankra. - name: Cluster Access description: Kubeconfigs, service-account tokens and per-cluster access grants. - name: Cluster Meshes description: >- Cilium ClusterMeshes that join an organisation's clusters into one network: create a mesh, check whether clusters can join, prepare a running cluster, and add or remove members. - name: Kubernetes description: Read and act on the Kubernetes objects inside a cluster. - name: AWS Clusters description: >- Provision and manage self-managed k3s / kubeadm clusters on AWS EC2 in your own VPC. - name: Ankra Cloud Clusters description: >- Provision and manage self-managed kubeadm / k3s clusters on Ankra Cloud servers: a private network, a NAT router and a bastion per cluster. - name: DigitalOcean Clusters description: Provision and manage DigitalOcean Kubernetes clusters. - name: Hetzner Clusters description: Provision and manage Hetzner Kubernetes clusters. - name: OVH Clusters description: Provision and manage OVH Kubernetes clusters. - name: Scaleway Clusters description: Provision and manage Scaleway Kapsule clusters. - name: UpCloud Clusters description: Provision and manage UpCloud Kubernetes clusters. - name: Proxmox Clusters description: >- Self-managed Kubernetes clusters Ankra builds on Proxmox VE VMs: the node, storage, bridge, template and size catalogs, create and teardown, start and stop, node groups, nodes, standalone VMs, upgrades and the bastion. - name: HPE Morpheus Clusters description: >- Self-managed Kubernetes clusters Ankra builds on HPE Morpheus VMs: the group, cloud, plan, layout and network catalogs, create and teardown, start and stop, node groups, nodes, standalone VMs, upgrades and the bastion. - name: Applications description: Deploy, configure and observe applications across the fleet. - name: Pipelines description: >- Pipeline definitions, the approval of the authority they declare, and the caches pipelines keep between runs. - name: Workspaces description: >- Personal workspaces on the organisation's CI pool where a repository's heavy commands run, and the repository profiles they are built from. - name: Deploy Targets description: >- Environments, the hosts registered to receive deployments, and the releases deployed to them. - name: Deploy Provenance description: >- Whether an application's deploys verify signed provenance from the organisation's own pipeline, the keys that provenance is signed with, and a dry-run that verifies images without deploying. - name: Backups description: >- Backup vaults, restore points, protection posture and captures for stacks and application deployments; a completed capture is not a verified restore. - name: Stack Profiles description: Reusable stack definitions, their versions and sharing. - name: Services description: >- Versioned service packages and explicit sharing. Runtime admission is separate from publication. - name: Charts description: Browse the chart catalogue behind stacks and addons. - name: Helm description: Helm registries, credentials and the charts they expose. - name: Executions description: Long-running platform executions and their jobs. - name: Operations description: Cancel in-flight cluster operations and their jobs. - name: Chat description: Conversational sessions, plans and confirmable actions. - name: AI Management description: >- Customer agent lifecycle, authenticated identity and organisation automation controls. - name: AI Agent Runs description: Autonomous agent runs and their outcomes. - name: AI Tickets description: The AI ticket board, its sync connections and settings. - name: AI Playbooks description: Reusable playbooks the AI lanes execute. - name: AI Conditions description: Conditions that gate AI autonomy. - name: AI Remediation description: >- The organisation's auto-remediation policy: what the AI lanes may fix by themselves, and who approves the rest. - name: AI Engineering Handoffs description: Work the AI lanes escalate to a human engineer. - name: AI Environment description: The environment and base stacks AI demos deploy into. - name: AI Memory description: >- What the assistant has learned about you: your cross-session memories and learned profile. - name: MCP Servers description: >- Register the MCP servers the organisation's AI agents can call, choose their tools and grant them to roles. - name: Security description: Findings, advisories, SBOMs, compliance and posture. - name: Cost description: Cluster and fleet cost, rate cards and cost settings. - name: Decisions description: >- The decision ledger behind the Security and Cost queues: proposals a surface computed, the approve and set-aside decisions people took on them, and the receipts of running them. - name: Usage description: >- What your organisation used of Ankra - vCPU-hours, playgrounds, managed services, hosted logs and metrics, and AI - per meter and period, with how completely it was measured and whether a published rate applies. - name: Billing description: Subscription and spend caps. - name: Organisation description: Members, invitations, audit logs and organisation settings. - name: Projects description: >- Projects group an organisation's clusters, applications, credentials and other resources beneath it: list, create, rename and delete them, switch the current project, see who reaches one, and move resources between them. - name: Account description: >- Your own account: the contact email Ankra mails when it differs from your sign-in address, and the AI provider keys your own work runs on. - name: Account Tokens description: Personal access tokens for the API and CLI. - name: Credentials description: The shared credential store. - name: AWS Credentials description: >- AWS credentials: access keys or CloudFormation-onboarded STS roles for cost, EKS and self-managed provisioning. - name: Ankra Cloud Credentials description: >- Ankra Cloud API tokens, shared by the self-managed and managed Ankra Cloud lanes. - name: Azure Credentials description: Azure credentials and SSH keys. - name: DigitalOcean Credentials description: DigitalOcean credentials and SSH keys. - name: Hetzner Credentials description: Hetzner credentials and SSH keys. - name: HPE Morpheus Credentials description: HPE Morpheus credentials and the capacity and quotas behind them. - name: OVH Credentials description: OVH credentials and SSH keys. - name: Proxmox Credentials description: Proxmox VE credentials and the capacity and quotas behind them. - name: Scaleway Credentials description: Scaleway credentials. - name: UpCloud Credentials description: UpCloud credentials and SSH keys. - name: Data Source Credentials description: Credentials for metrics and log sources. - name: DNS Credentials description: Credentials for DNS providers. - name: Object Storage Buckets description: >- Buckets Ankra creates and manages on an organisation's own provider credentials. - name: DNS description: DNS zones and records, including custom organisation zones. - name: Cloudflare description: Cloudflare domains and the credentials behind them. - name: Avura description: >- The linked Avura organization, the domains it shares with Ankra Platform, and their DNS records. - name: Variables description: Organisation- and cluster-scoped variables. - name: Secret Slots description: >- Store secrets in Vault and reference them by ${SECRET_SLOT:} sentinel instead of by value. - name: SOPS description: Encrypt and decrypt values with the organisation SOPS config. - name: Alerts description: Alert integrations and ingest credentials. - name: Notifications description: Notification routes and their delivery targets. - name: Support description: Support tickets. - name: AI Settings description: Organisation AI provider, model catalog and per-function model settings paths: /api/v1/org/organisation/audit-logs: get: tags: - Organisation summary: List the organisation audit log with an API token description: >- Bearer twin of GET /org/organisation/audit-logs: the organisation audit log, newest first, paginated with `page` and `page_size` (default 50, at most 200), with the actor, agent and target of each row. Accepts a personal or service-account API token; the token (its scopes and its role) must hold audit.read in the organisation. Same filters as the session listing. The organisation is the token's own, or the one named by the X-Ankra-Organisation-Id header when the token's user is a member of it; a service-account token cannot leave its organisation. The audit trail belongs to the whole organisation: audit.read cannot be held through a project, so a project-only member's token is refused, and a token pinned to a project is refused with 403 whatever its holder's role. operationId: list_org_audit_logs_api_v1 parameters: - in: query name: page required: false schema: default: 1 type: integer - in: query name: page_size required: false schema: default: 50 maximum: 200 type: integer - in: query name: search required: false schema: type: string - in: query name: user_id required: false schema: type: string format: uuid - in: query name: action_type required: false schema: type: string - in: query name: resource_type required: false schema: type: string - in: query name: start_date required: false schema: type: string format: date-time - in: query name: end_date required: false schema: type: string format: date-time - in: query name: actor_type required: false schema: enum: - agent - human - service_account - system type: string - in: query name: outcome required: false schema: enum: - succeeded - failed type: string - description: Narrow the listing to one cluster's slice of the organisation trail. in: query name: cluster_id required: false schema: type: string format: uuid - in: query name: agent_task_id required: false schema: type: string format: uuid responses: '200': content: application/json: schema: $ref: '#/components/schemas/OrgAuditLogListResponse' description: One page of the organisation audit trail, newest first. '400': description: >- Missing bearer token or malformed Authorization / X-Ankra-Organisation-Id header content: application/json: schema: $ref: '#/components/schemas/OrgAuditDetailError' '401': description: Invalid, expired or revoked API token content: application/json: schema: $ref: '#/components/schemas/OrgAuditDetailError' '403': description: >- The token's scopes or the principal's role lack audit.read, or the token's user is not a member of the requested organisation, or the token is pinned to a project content: application/json: schema: oneOf: - $ref: '#/components/schemas/SecurityPermissionDenied' - $ref: '#/components/schemas/OrgAuditDetailError' '422': content: application/json: schema: $ref: '#/components/schemas/HTTPValidationError' description: Request validation error '500': description: Internal server error '503': description: Authorisation service unavailable content: application/json: schema: $ref: '#/components/schemas/OrgAuditDetailError' security: - BearerAuth: [] components: schemas: OrgAuditLogListResponse: properties: items: items: $ref: '#/components/schemas/OrgAuditLogItem' type: array page: type: integer page_size: type: integer total: type: integer total_pages: type: integer required: - items - total - page - page_size - total_pages type: object OrgAuditDetailError: properties: detail: type: string required: - detail type: object SecurityPermissionDenied: properties: detail: enum: - permission_denied type: string permission: type: string scope_type: type: string required: - detail - permission - scope_type type: object HTTPValidationError: properties: detail: items: $ref: '#/components/schemas/ValidationError' title: Detail type: array title: HTTPValidationError type: object OrgAuditLogItem: properties: action_type: type: string actor: $ref: '#/components/schemas/OrgAuditActor' cluster_id: anyOf: - type: string format: uuid - type: 'null' cluster_is_deleted: type: boolean cluster_name: anyOf: - type: string - type: 'null' details: type: object ip_address: anyOf: - type: string - type: 'null' log_id: type: string format: uuid outcome: $ref: '#/components/schemas/OrgAuditOutcome' resource_id: anyOf: - type: string - type: 'null' resource_type: type: string target: $ref: '#/components/schemas/OrgAuditTarget' timestamp: type: string format: date-time user_email: type: string user_id: anyOf: - type: string format: uuid - type: 'null' required: - log_id - timestamp - user_id - user_email - action_type - resource_type - resource_id - details - ip_address - cluster_id - cluster_name - cluster_is_deleted - actor - target - outcome type: object ValidationError: properties: loc: items: anyOf: - type: string - type: integer title: Location type: array msg: title: Message type: string type: title: Error Type type: string required: - loc - msg - type title: ValidationError type: object OrgAuditActor: description: >- Who took the action. type separates an autonomous agent turn from a hand-clicked one, which email cannot: a dispatched agent run borrows the identity of the human who owns its session. The agent members are populated only when the row resolves to a dispatched agent run. properties: agent_id: anyOf: - type: string format: uuid - type: 'null' agent_name: anyOf: - type: string - type: 'null' autonomy: anyOf: - type: string - type: 'null' email: type: string origin: anyOf: - type: string - type: 'null' run_id: anyOf: - type: string format: uuid - type: 'null' session_id: anyOf: - type: string format: uuid - type: 'null' trigger: anyOf: - type: string - type: 'null' type: enum: - agent - human - system type: string required: - type - email - agent_id - agent_name - run_id - session_id - autonomy - origin - trigger type: object OrgAuditOutcome: description: >- Whether the action succeeded. "unknown" is for writers that record no success marker - a domain audit describes an action already committed when the row was written, so a missing marker is not a failure. properties: duration_ms: anyOf: - type: integer - type: 'null' error: anyOf: - type: string - type: 'null' status: enum: - succeeded - failed - unknown type: string required: - status - error - duration_ms type: object OrgAuditTarget: description: >- What the action acted on, resolved from the recorded parameters. An empty kind and name means nothing nameable was recorded and the client should fall back to resource_id. properties: kind: type: string name: type: string namespace: anyOf: - type: string - type: 'null' required: - kind - name - namespace type: object securitySchemes: BearerAuth: bearerFormat: PAT scheme: bearer type: http ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.