> ## Documentation Index > Fetch the complete documentation index at: https://docs.visiqlabs.com/llms.txt > Use this file to discover all available pages before exploring further. # Query the action decision log > Paginated, filterable log of action-governance decisions. Requires permission `allow_audit_log:view` and scope `allow:read`. ## OpenAPI ````yaml /api-reference/openapi.yaml get /v1/allow/audit-log openapi: 3.1.0 info: title: VisIQ Governance API version: 1.0.0 description: > The VisIQ platform API for governing agentic AI. One rule engine evaluates every governed agent event against your policies and returns a decision (permit, deny, approval-required, redact, mask, or escalate), records a cryptographically-verifiable audit trail, and governs agent-to-agent delegation. All requests are authenticated with a bearer API key. Mint a key in the dashboard under **Connectors -> API Keys**; it is presented as `Authorization: Bearer vq_prod_...`. Keys are scoped: harness/agent keys reach the operational surface (evaluate, rule bundles, telemetry, record ingestion), while management keys and dashboard sessions govern rules, agents, settings, and audit reads through role-based permissions. Decision vocabularies differ per facet. Action governance emits `permit | deny | approval_required | mask`. Retrieval governance emits `allow | deny | redact | escalate`. The unified `POST /evaluate` surface projects both into a single union vocabulary (`permit | deny | approval_required | redact | escalate | mask`). contact: name: VisIQ Labs url: https://docs.visiqlabs.com servers: - url: https://api.visiqlabs.com description: Production security: - bearerAuth: [] tags: - name: Evaluation description: Per-event governance decisions for action, retrieval, and delegation. - name: Action Rules description: Manage the rules that govern agent actions (writes/tool calls). - name: Retrieval Rules description: Manage the rules that govern retrieval and context exposure. - name: Unified Rules description: Operation-native rule management across both facets in one surface. - name: Rule Bundles description: Compiled, cacheable rule bundles the SDK runtime pulls per agent. - name: Agents description: Register and manage the agents whose events you govern. - name: Human-in-the-loop description: The approval queue for events that require a human decision. - name: Settings description: Per-account governance defaults. - name: Delegation description: Govern scoped agent-to-agent hand-offs with signed grant tokens. - name: Records description: Ingest, retrieve, finalize, and verify the tamper-evident audit trail. - name: Audit Log description: Versioned, paginated read APIs over recorded decisions and events. - name: Cognition description: >- Read captured Agent Cortex cognition sessions and beats (dedicated cognition:read scope). paths: /v1/allow/audit-log: get: tags: - Audit Log summary: Query the action decision log description: > Paginated, filterable log of action-governance decisions. Requires permission `allow_audit_log:view` and scope `allow:read`. operationId: getActionAuditLog parameters: - $ref: '#/components/parameters/Page' - $ref: '#/components/parameters/Limit100' - name: agent_id in: query required: false schema: type: string maxLength: 255 - name: target_app in: query required: false schema: type: string maxLength: 255 - name: decision in: query required: false schema: type: string enum: - permit - deny - approval_required - mask - name: hitl_result in: query required: false schema: type: string enum: - approved - rejected - timeout - name: start_date in: query required: false schema: type: string format: date-time - name: end_date in: query required: false schema: type: string format: date-time responses: '200': description: A page of decision entries. content: application/json: schema: $ref: '#/components/schemas/ActionAuditLogPage' '400': $ref: '#/components/responses/BadRequest' '401': $ref: '#/components/responses/Unauthorized' '403': $ref: '#/components/responses/Forbidden' security: - bearerAuth: [] components: parameters: Page: name: page in: query required: false schema: type: integer minimum: 1 default: 1 description: 1-based page number. Limit100: name: limit in: query required: false schema: type: integer minimum: 1 maximum: 100 default: 50 description: Page size (max 100). schemas: ActionAuditLogPage: allOf: - $ref: '#/components/schemas/PageEnvelope' - type: object properties: data: type: array items: $ref: '#/components/schemas/ActionAuditLogEntry' PageEnvelope: type: object description: Offset pagination envelope (`data` + `total`/`page`/`pageSize`). properties: total: type: integer page: type: integer pageSize: type: integer ActionAuditLogEntry: type: object properties: id: type: string format: uuid agent_id: type: string target_app: type: string action: type: string context: type: object additionalProperties: true decision: type: string enum: - permit - deny - approval_required - mask reason: type: - string - 'null' rule_id: type: - string - 'null' hitl_result: type: - string - 'null' enum: - approved - rejected - timeout - null hitl_responded_at: type: - string - 'null' format: date-time hitl_responded_by: type: - string - 'null' created_at: type: string format: date-time execution_result: type: - string - 'null' execution_completed_at: type: - string - 'null' format: date-time execution_details: type: - object - 'null' additionalProperties: true Error: type: object required: - error description: > The standard error envelope. `details` carries the validation issue list on 400s; authorization failures add fields such as `detail`, `requiredScopes`, or `requiredPermission`. properties: error: type: string detail: type: string code: type: string details: type: array items: type: object additionalProperties: true additionalProperties: true responses: BadRequest: description: The request was malformed or failed validation. content: application/json: schema: $ref: '#/components/schemas/Error' example: error: Invalid request body details: - path: - agent_id message: Required Unauthorized: description: Missing or invalid API key. content: application/json: schema: $ref: '#/components/schemas/Error' example: error: Unauthorized Forbidden: description: The key lacks the required permission or scope. content: application/json: schema: $ref: '#/components/schemas/Error' example: error: insufficient_scope detail: This API key is not authorized for the requested operation. securitySchemes: bearerAuth: type: http scheme: bearer description: > A VisIQ API key presented as `Authorization: Bearer vq_prod_...`. Mint keys under **Connectors -> API Keys** in the dashboard. ````