> ## Documentation Index
> Fetch the complete documentation index at: https://developers.nexspace365.com/llms.txt
> Use this file to discover all available pages before exploring further.

# List the approvals a headless run raised

> A run that hits a `require_approval` action pauses at
`status: pending_approval` and records one approval row per gated
action. This lists them (pending and resolved) so a caller can inspect
what needs a decision before POSTing to
`/api/approvals/{approvalId}/approve` or `/reject`.
Requires the `agents:run` scope and ownership of the run.




## OpenAPI

````yaml https://api.nexspace365.com/api/openapi.json get /api/agents/{id}/runs/{runId}/approvals
openapi: 3.0.3
info:
  title: NexSpace 365 API
  description: >
    Multi-industry enterprise workforce management platform — scheduling, HR,

    payroll, CRM, AI, and messaging suites.


    ## Authentication

    Three schemes: session cookie, JWT bearer, or API key (`nex_live_…` /

    `nex_test_…` / `nex_pat_…`). AI agents should use API keys with appropriate

    scopes.


    ## Authorization

    Endpoints require specific permissions via the RBAC system:

    - **Internal team**: Full platform access

    - **Facility users**: Scoped to their org/facilities

    - **Staff**: Limited to own data


    ## Error Contract

    All errors return `{ error: { message, code?, suggestion?, retryable? },
    requestId? }`.

    The `suggestion` field hints at how to fix the request; `retryable` signals
    whether

    retry-with-backoff is appropriate.


    ## Versioning

    Pin your integration to a specific API version via the `NexSpace-Version`
    header

    (date-based, e.g. `2026-05-10`). When absent, the latest version is assumed.

    Deprecated versions include `Sunset` and `Deprecation` headers. Discovery at

    `GET /.well-known/api-versions`.


    ## Idempotency

    Write operations (POST/PUT/PATCH) accept an `Idempotency-Key` header. If

    the same key + body combination is sent again within 24 hours, the original

    response is replayed. Different body with the same key returns 409 Conflict.


    ## MCP (Model Context Protocol)

    AI agents interact via `POST /mcp` using JSON-RPC 2.0. Call `tools/list` to

    discover available verbs, then `tools/call` to invoke them.
  version: 1.0.0
  contact:
    name: NexSpace API Support
    email: support@nexspace365.com
  license:
    name: MIT
    url: https://opensource.org/licenses/MIT
servers:
  - url: https://api.nexspace365.com
    description: Production server
security:
  - bearerAuth: []
  - apiKeyAuth: []
tags:
  - name: Authentication
    description: User authentication and session management
  - name: Facilities
    description: Facility management
  - name: Staff
    description: Staff member management and profiles
  - name: Credentials
    description: Staff credential tracking — licenses, certifications, and training
  - name: Shifts
    description: Shift scheduling and management
  - name: Dashboard
    description: Dashboard statistics and widgets
  - name: API Keys
    description: API key lifecycle — create, list, revoke, rotate
  - name: MCP
    description: Model Context Protocol endpoint for AI agent tool calling
  - name: OAuth
    description: OAuth 2.1 authorization server — DCR, authorize, token
  - name: Webhooks
    description: Outbound webhook subscription management
  - name: Analytics
    description: API usage analytics and observability
paths:
  /api/agents/{id}/runs/{runId}/approvals:
    get:
      tags:
        - Agents
      summary: List the approvals a headless run raised
      description: |
        A run that hits a `require_approval` action pauses at
        `status: pending_approval` and records one approval row per gated
        action. This lists them (pending and resolved) so a caller can inspect
        what needs a decision before POSTing to
        `/api/approvals/{approvalId}/approve` or `/reject`.
        Requires the `agents:run` scope and ownership of the run.
      operationId: listAgentRunApprovals
      parameters:
        - name: id
          in: path
          required: true
          schema:
            type: integer
        - name: runId
          in: path
          required: true
          schema:
            type: string
      responses:
        '200':
          description: Approvals for the run
          content:
            application/json:
              schema:
                type: object
                properties:
                  runId:
                    type: string
                  pending:
                    type: array
                    items:
                      type: integer
                    description: Ids of approvals still awaiting a decision.
                  approvals:
                    type: array
                    items:
                      type: object
                      properties:
                        id:
                          type: integer
                        toolName:
                          type: string
                        displayName:
                          type: string
                          nullable: true
                        status:
                          type: string
                          enum:
                            - pending
                            - approved
                            - rejected
                            - expired
                        riskLevel:
                          type: string
                          nullable: true
                        createdAt:
                          type: string
                          format: date-time
                          nullable: true
                        resolvedAt:
                          type: string
                          format: date-time
                          nullable: true
        '404':
          description: Run not found or expired
      security:
        - apiKeyAuth: []
components:
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: JWT token authentication
    apiKeyAuth:
      type: http
      scheme: bearer
      bearerFormat: NexSpaceApiKey
      description: |
        API key or personal access token (NEX-1042). Send as
        `Authorization: Bearer <token>`. Token format:
          - `nex_live_…`  — live API key (server-to-server)
          - `nex_test_…`  — sandbox API key
          - `nex_pat_…`   — personal access token (acts as the issuing user)

        Authorization is decided by the key's `scopes` array, not the
        owning user's RBAC role. See `POST /api/api-keys` to mint a key.

````