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

# List Call Outcomes



## OpenAPI

````yaml /openapi/openapi.yaml get /v1/workspace/call-outcomes
openapi: 3.1.0
info:
  title: OneInbox API
  version: 1.0.0
servers:
  - url: https://api-tokyo.oneinbox.ai
    description: Production (Tokyo ap-northeast-1)
security: []
tags:
  - name: health
  - name: integrations
  - name: llm-models
  - name: tools
  - name: knowledge-bases
  - name: voices
  - name: webhooks
  - name: agents
  - name: phone-numbers
  - name: calls
  - name: workspace
  - name: usage
  - name: audit-events
paths:
  /v1/workspace/call-outcomes:
    get:
      tags:
        - workspace
      summary: List Call Outcomes
      operationId: list_call_outcomes_v1_workspace_call_outcomes_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/CallOutcomeListResponse'
      security:
        - API Key: []
components:
  schemas:
    CallOutcomeListResponse:
      properties:
        builtin:
          items:
            type: string
          type: array
          title: Builtin
        items:
          items:
            $ref: '#/components/schemas/CallOutcomeResponse'
          type: array
          title: Items
        total:
          type: integer
          title: Total
      type: object
      required:
        - builtin
        - items
        - total
      title: CallOutcomeListResponse
      description: |-
        GET /v1/workspace/call-outcomes. `builtin` are the always-available
        platform outcome names; `items` are this workspace's custom outcomes.
    CallOutcomeResponse:
      properties:
        id:
          type: string
          title: Id
        name:
          type: string
          title: Name
        label:
          type: string
          title: Label
        description:
          anyOf:
            - type: string
            - type: 'null'
          title: Description
        is_active:
          type: boolean
          title: Is Active
        created_at:
          type: string
          format: date-time
          title: Created At
        updated_at:
          type: string
          format: date-time
          title: Updated At
      type: object
      required:
        - id
        - name
        - label
        - description
        - is_active
        - created_at
        - updated_at
      title: CallOutcomeResponse
  securitySchemes:
    API Key:
      type: http
      description: >-
        Your **API key** sent as a Bearer credential — `Authorization: Bearer
        <api_key>`, where `<api_key>` starts with `oi_sk_` (create one via `POST
        /v1/api-keys`). Although the field is labelled 'token', paste your API
        key here. A dashboard JWT is also accepted on this header for the same
        endpoints.
      scheme: bearer

````