> ## Documentation Index > Fetch the complete documentation index at: https://docs.mka1.com/llms.txt > Use this file to discover all available pages before exploring further. # List tool approvals > List the tool calls waiting for your decision (which=pending, the default) or the ones already decided or expired (which=decided): the calls your organization's tool policy named you an approver of. With response_id, list instead the approvals of that response that you may see; the caller that made the request sees all of them. Results are paged with limit and after. ## OpenAPI ````yaml https://apigw.mka1.com/speakeasy.json get /api/v1/llm/tool_approvals openapi: 3.1.1 info: title: MKA1 API version: 1.1.0 description: >- The MKA1 API is a RESTful API that provides access to the MKA1 platform. Learn how to get started with the API and the TypeScript SDK [here](https://mka1.apidocumentation.com/guides/getting-started). license: name: Proprietary servers: - url: https://apigw.mka1.com description: MKA1 API Gateway - url: / description: Relative server URL (configurable via SDK constructor) security: [] tags: - name: Resource Authorization description: >- Manage permissions for LLM resources. Create resources, grant/revoke permissions, and delete resources. Only resource owners can grant, revoke, or delete permissions. x-displayName: Resource Authorization - name: Audit description: >- Audit API for org owners and admins. Trace one request end to end by its X-Request-ID: API gateway timing, the responses it created, and their model invocations and tool calls. x-displayName: Audit - name: Embeddings description: >- Text embedding API endpoints for generating vector representations of text. Create semantic embeddings for search, clustering, and similarity matching using various embedding models. x-displayName: Embeddings - name: Feedback description: >- User feedback API for rating and commenting on chat completions. Collect thumbs up/down ratings and detailed feedback to improve model responses and track user satisfaction. x-displayName: Feedback - name: Images description: >- Image generation API endpoints for creating images from text descriptions. Generate images with control over size, quality, and style. x-displayName: Images - name: MCP Vault description: >- MCP vault API for storing user-owned MCP server configurations and encrypted credentials. Agents reference vault IDs so secrets are resolved only at tool execution time. x-displayName: MCP Vault - name: Speech description: >- Speech API endpoints for audio processing. Convert text to natural-sounding speech (TTS) or transcribe speech to text (STT) in different languages. x-displayName: Speech - name: Usage description: >- Usage tracking and analytics API for monitoring token consumption, request counts, and cost analysis. View detailed statistics per user, model, and time period. x-displayName: Usage - name: Extract description: >- Structured data extraction API for extracting information from files. Define JSON schemas to extract structured data from images, PDFs, and documents. Supports reusable schema templates. x-displayName: Extract - name: Text Classification description: >- Text classification API for categorizing text into predefined labels. Use AI models to classify text content for sentiment analysis, topic categorization, and content moderation. x-displayName: Text Classification - name: Responses description: >- Agent-powered responses API for creating AI agents with autonomous tool usage. Build conversational assistants that can use web search, file operations, image generation, code execution, and MCP integrations. Supports background processing, streaming, and real-time status tracking. x-displayName: Responses - name: Files description: >- File management API for uploading, storing, and managing files with automatic expiration and S3 integration. Upload files that can be used with Assistants, Vector Stores, and other features. Files are stored in S3 with metadata tracked in PostgreSQL. Supports automatic cleanup of expired files. x-displayName: Files - name: Vector Stores description: >- Vector store API for storing and searching documents using embeddings. Create vector stores, upload files with automatic chunking and embedding generation, and perform semantic search. Files are processed asynchronously using Temporal workflows for durability. Supports automatic cleanup of expired stores and LanceDB for efficient vector storage. x-displayName: Vector Stores - name: Conversations description: >- Conversation management API for storing and retrieving conversation state across Response API calls. Create conversations, add items (user messages, assistant messages, system messages), and maintain conversation history. Supports metadata tracking and multi-turn dialogue state management. x-displayName: Conversations - name: Guardrails description: >- AI safety guardrails API for configuring content moderation and security policies. Set up ban word lists, prompt injection detection, and system prompt leakage prevention. Guardrails apply to all requests from an account and can be tested before deployment. x-displayName: Guardrails - name: Tool Policy description: >- Organization tool policy API. Org admins deny tool types, or require approval before their calls run, for every Responses request in the organization, including saved agent runs. The policy overrides what requests and agents configure. x-displayName: Tool Policy - name: Models description: >- Model listing API for discovering available models. Returns model IDs, ownership, and metadata for all registered models in the gateway. x-displayName: Models - name: Skills description: >- Skills API for managing versioned bundles of instructions and files following the Agent Skills standard. Create, version, and download reusable skill packages that include SKILL.md manifests for agent environments. x-displayName: Skills - name: Chat Completions description: >- **Deprecated: Use the Responses API (`/api/v1/llm/responses`) instead.** Chat completion endpoints with support for streaming, tool calls, and multiple providers. x-deprecated: true x-displayName: Chat Completions - name: Batches x-displayName: Batches - name: Evals x-displayName: Evals - name: Fine-Tuning x-displayName: Fine-Tuning - name: Memory Stores x-displayName: Memory Stores - name: Prompts x-displayName: Prompts - name: API Key x-displayName: API Key - name: OAuth x-displayName: OAuth - name: Session x-displayName: Session - name: Organization x-displayName: Organization - name: Cluster Admin x-displayName: Cluster Admin - name: Sessions description: Create, inspect, access, and terminate sandbox sessions. x-displayName: Sessions - name: Browser description: >- Connect to browser sessions through the gateway port proxy. Browser sessions expose a Chrome DevTools Protocol endpoint on port 9222. x-displayName: Browser - name: Execution description: Run shell commands and code inside an existing sandbox session. x-displayName: Execution - name: Workspace description: >- Inspect the workspace manifest, transfer files or archives, and download generated artifacts. x-displayName: Workspace - name: Sandbox Usage description: >- Aggregate sandbox usage statistics across sessions, execution, and workspace operations. x-displayName: Sandbox Usage - name: Sandbox Pricing description: >- Cluster-admin management of the sandbox compute rate card used for budgeted spend. x-displayName: Sandbox Pricing - name: Sandbox GitHub description: >- Connect a GitHub account, clone its repositories into sandbox sessions, and push branches and open pull requests from a session. The GitHub token stays in the sandbox service and never enters a session. x-displayName: Sandbox GitHub - name: Sandbox Environments description: >- Save reusable session configuration (repositories, environment variables, network access, and a setup script) and run the setup script in a session. x-displayName: Sandbox Environments - name: Sandbox Connectors description: >- Connect remote MCP servers (Linear, Notion, Sentry and others) to your account so Coding Harness sessions started from an environment that lists them can call their tools. The sandbox service keeps each connector's credential and never puts it in a session. x-displayName: Sandbox Connectors - name: Agents description: Create and manage reusable agent definitions. x-displayName: Agents - name: Agent Versions description: Inspect an agent's configuration history and roll back to a prior version. x-displayName: Agent Versions - name: Agent Runs description: Execute saved agents and inspect persisted run results. x-displayName: Agent Runs - name: Agent Connectors description: >- Connect saved agents to external messaging channels such as Telegram, including text, photo, and supported document exchange. x-displayName: Agent Connectors - name: Agent Schedules description: Create and manage scheduled or recurring saved agent runs. x-displayName: Agent Schedules - name: schema-4_other x-displayName: other - name: Billing x-displayName: Billing - name: Budgets x-displayName: Budgets - name: Settings x-displayName: Settings - name: Compute Jobs x-displayName: Compute Jobs - name: Compute Services x-displayName: Compute Services - name: Compute Catalog x-displayName: Compute Catalog - name: Compute Volumes x-displayName: Compute Volumes - name: Compute Pricing x-displayName: Compute Pricing - name: Compute Secrets x-displayName: Compute Secrets - name: Compute Usage x-displayName: Compute Usage - name: Compute Tenants x-displayName: Compute Tenants - description: Create, list, read, update, and delete repositories. name: Repositories x-displayName: Repositories - name: Tracking Experiments description: Create and query tenant experiments. x-displayName: Tracking Experiments - name: Tracking Runs description: Record and retrieve run parameters, metrics, and tags. x-displayName: Tracking Runs - name: analytics.projects x-displayName: Projects description: Create, list, rename, and archive analytics projects. - name: analytics.keys x-displayName: Capture keys description: Create and revoke project keys for sending events. - name: analytics x-displayName: Events description: Send events and query event counts or unique visitors. - name: analytics.events x-displayName: Event search description: List individual events with their properties, newest first. - name: analytics.visitors x-displayName: Visitor search description: List visitors by their latest activity, with first and last seen times. - name: generators x-displayName: generators - name: generations x-displayName: generations - name: formats x-displayName: formats - description: >- Flags, environments, evaluation, and the audit log. Administrative operations require a cluster administrator; evaluation uses an environment-specific evaluation key. name: Feature Flags x-displayName: Feature Flags - name: Service Status description: >- Current status of each service and the incident history, for this deployment's region. x-displayName: Service Status - name: Support Cases description: >- Open and follow support cases. Organization owners and admins see all of the organization's cases; other members see the cases they opened. x-displayName: Support Cases paths: /api/v1/llm/tool_approvals: get: tags: - Tool Policy summary: List tool approvals description: >- List the tool calls waiting for your decision (which=pending, the default) or the ones already decided or expired (which=decided): the calls your organization's tool policy named you an approver of. With response_id, list instead the approvals of that response that you may see; the caller that made the request sees all of them. Results are paged with limit and after. operationId: listToolApprovals parameters: - name: which in: query schema: enum: - pending - decided type: string description: >- Which part of your approval inbox to list: pending (undecided and not expired, oldest first) or decided (decided or expired, most recently closed first). Defaults to pending. Cannot be combined with response_id. allowEmptyValue: true example: pending - name: response_id in: query schema: type: string minLength: 1 maxLength: 255 description: >- List the approvals of this response that you may see, oldest first, instead of your inbox. The caller that made the request sees all of them. allowEmptyValue: true - name: limit in: query schema: type: integer minimum: 1 maximum: 100 default: 100 description: How many approvals to return. allowEmptyValue: true example: 20 - name: after in: query schema: type: string minLength: 1 maxLength: 255 description: Return the approvals that follow this approval ID in the listing. allowEmptyValue: true - name: X-On-Behalf-Of in: header required: false schema: type: string description: Optional external end-user identifier forwarded by the API gateway. responses: '200': description: OK content: application/json: schema: $ref: '#/components/schemas/ToolApprovalList' example: object: list data: - object: tool_approval id: tapr_0f1e2d3c4b5a69788796a5b4c3d2e1f0 kind: tool_approval_request status: pending tool_type: code_interpreter tool_name: code_interpreter server_label: null arguments: code: print(open('report.csv').read()) response_id: resp_7d1c9b6e5a4f4c2e9b8a7f6e5d4c3b2a agent_id: null requested_by: user_id: user_2f6c1e user_type: user external_user_id: null team_id: team_finance approver_user_ids: - user_9a41b7 - user_c03d52 decided_by_user_id: null comment: null claimed: false created_at: '2026-11-10T09:30:00.000Z' expires_at: '2026-11-11T09:30:00.000Z' decided_at: null has_more: false security: - bearerAuth: [] x-codeSamples: - lang: csharp label: CSharp (SDK) source: |- using MeetKai.MKA1; using MeetKai.MKA1.Types.Components; using MeetKai.MKA1.Types.Requests; var sdk = new SDK(bearerAuth: ""); ListToolApprovalsRequest req = new ListToolApprovalsRequest() { Which = Which.Pending, Limit = 20, }; var res = await sdk.ToolPolicy.ListToolApprovalsAsync(req); // handle response - lang: python label: Python (SDK) source: |- from meetkai_mka1 import SDK with SDK( bearer_auth="", ) as sdk: res = sdk.tool_policy.list_tool_approvals(which="pending", limit=20) # Handle response print(res) - lang: typescript label: Typescript (SDK) source: |- import { SDK } from "@meetkai/mka1"; const sdk = new SDK({ bearerAuth: "", }); async function run() { const result = await sdk.toolPolicy.listToolApprovals({ which: "pending", limit: 20, }); console.log(result); } run(); - lang: go label: Go (SDK) source: "package main\n\nimport(\n\t\"context\"\n\tmka1 \"github.com/MeetKai/mka1-sdks/go\"\n\t\"github.com/MeetKai/mka1-sdks/go/models/operations\"\n\t\"log\"\n)\n\nfunc main() {\n ctx := context.Background()\n\n s := mka1.New(\n mka1.WithSecurity(\"\"),\n )\n\n res, err := s.ToolPolicy.ListToolApprovals(ctx, operations.ListToolApprovalsRequest{\n Which: operations.WhichPending.ToPointer(),\n Limit: mka1.Pointer[int64](20),\n })\n if err != nil {\n log.Fatal(err)\n }\n if res.ToolApprovalList != nil {\n // handle response\n }\n}" components: schemas: ToolApprovalList: type: object properties: object: const: list data: type: array items: $ref: '#/components/schemas/ToolApproval' has_more: type: boolean description: >- Whether more approvals follow; pass the last ID as after to read them. required: - object - data - has_more title: Tool approval list ToolApproval: type: object properties: object: const: tool_approval id: type: string description: >- The ID of the approval request item in the response output (mcpr_... or tapr_...). kind: enum: - mcp_approval_request - tool_approval_request type: string description: >- The type of the approval request item: mcp_approval_request for an MCP call, tool_approval_request for a built-in tool. status: $ref: '#/components/schemas/ToolApprovalStatus' tool_type: type: string description: >- The held tool's type: mcp, or a built-in tool type such as web_search or code_interpreter. tool_name: type: string description: The name of the tool the model called. server_label: anyOf: - type: string - type: 'null' description: 'MCP calls only: the label of the MCP server.' arguments: type: object propertyNames: type: string additionalProperties: {} description: The arguments the call runs with if it is approved. response_id: type: string description: The response that stopped for this approval. agent_id: anyOf: - type: string - type: 'null' description: The saved agent the request ran for, if any. requested_by: $ref: '#/components/schemas/ToolApprovalRequester' approver_user_ids: type: array items: type: string description: >- The users the organization's tool policy named to decide this call. Empty when the caller decides. decided_by_user_id: anyOf: - type: string - type: 'null' description: >- Who decided: the approver, or the caller for an approval without approvers. comment: anyOf: - type: string - type: 'null' description: The comment or reason given with the decision. claimed: type: boolean description: >- Whether the caller's continuation has consumed the decision. An approved call runs only when this happens, and only once. created_at: type: string format: date-time description: When the call was held. expires_at: type: string format: date-time description: >- The deadline for the next step: the decision while pending, then the caller's continuation. A decision gives the caller 24 hours. decided_at: anyOf: - type: string format: date-time - type: 'null' description: When the decision was made. required: - object - id - kind - status - tool_type - tool_name - server_label - arguments - response_id - agent_id - requested_by - approver_user_ids - decided_by_user_id - comment - claimed - created_at - expires_at - decided_at title: Tool approval description: >- A tool call held for approval. Approvals that name approvers stay listed for 30 days after they are decided or time out; the others are removed at their deadline. ToolApprovalStatus: enum: - pending - approved - denied - expired type: string description: >- pending until an approver decides, or, for an approval without approvers, until the caller's continuation answers it. expired when the deadline passed without a decision. ToolApprovalRequester: type: object properties: user_id: type: string description: The user or service account whose request was held. user_type: type: string description: user or service-account. external_user_id: anyOf: - type: string - type: 'null' description: The end user the request acted on behalf of, if any. team_id: anyOf: - type: string - type: 'null' description: The team the request ran in, if any. required: - user_id - user_type - external_user_id - team_id title: Tool approval requester description: >- Who made the request whose tool call was held. Only this caller can continue the response. securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: API Key description: >- Send Authorization: Bearer , using an MKA1 API key for automation or an OAuth API access token for a signed-in application. Use a dynamic security callback to refresh OAuth access tokens. Browser session-only operations still require their declared cookie. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.