Webex · Schema

SummaryListResponse

CallingCollaborationCommunicationsEnterpriseMessagingVideo Conferencing

Properties

Name Type Description
orgId string The unique identifier of the organization to which the summarized interactions belong.
agentCiUserId stringnull The CI (Common Identity) user ID of the agent associated with the summaries. Present when searchType is AGENT; otherwise null.
interactionId stringnull The unique identifier of a specific interaction. Present when searchType is INTERACTION; otherwise null.
queueId stringnull The queue ID (reserved for future use).
searchType object
summaries object Map of summaries keyed by feature type (POST_CALL, MID_CALL). Each feature maps summary identifiers to their summary fields.
View JSON Schema on GitHub

JSON Schema

webex-summary-list-response-schema.json Raw ↑
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://raw.githubusercontent.com/api-evangelist/webex/main/json-schema/webex-summary-list-response-schema.json",
  "title": "SummaryListResponse",
  "x-generated": "2026-10-04",
  "x-method": "derived",
  "x-generator": "derive-json-schema.py",
  "x-source": "openapi/webex-agent-summaries-api-openapi.yml#/components/schemas/SummaryListResponse",
  "type": "object",
  "properties": {
    "orgId": {
      "type": "string",
      "description": "The unique identifier of the organization to which the summarized interactions belong."
    },
    "agentCiUserId": {
      "type": [
        "string",
        "null"
      ],
      "description": "The CI (Common Identity) user ID of the agent associated with the summaries. Present when searchType is AGENT; otherwise null."
    },
    "interactionId": {
      "type": [
        "string",
        "null"
      ],
      "description": "The unique identifier of a specific interaction. Present when searchType is INTERACTION; otherwise null."
    },
    "queueId": {
      "type": [
        "string",
        "null"
      ],
      "description": "The queue ID (reserved for future use)."
    },
    "searchType": {
      "$ref": "#/$defs/SearchType"
    },
    "summaries": {
      "type": "object",
      "description": "Map of summaries keyed by feature type (POST_CALL, MID_CALL). Each feature maps summary identifiers to their summary fields.",
      "properties": {
        "POST_CALL": {
          "type": "object",
          "description": "Post-call summaries keyed by summary identifier.",
          "additionalProperties": {
            "$ref": "#/$defs/PostCallSummary"
          }
        },
        "MID_CALL": {
          "type": "object",
          "description": "Mid-call summaries keyed by summary identifier.",
          "additionalProperties": {
            "$ref": "#/$defs/MidCallSummary"
          }
        }
      }
    }
  },
  "$defs": {
    "MidCallSummary": {
      "type": "object",
      "properties": {
        "reasonForTransferOrConsult": {
          "type": "string",
          "description": "The specific reason the interaction is being transferred or consulted."
        },
        "additionalContext": {
          "type": "string",
          "description": "Important information already gathered that the next agent needs to continue smoothly."
        },
        "keyActionsTaken": {
          "type": "string",
          "description": "Steps completed so far in the interaction before the transfer or consult occurred."
        }
      }
    },
    "PostCallSummary": {
      "type": "object",
      "properties": {
        "initialContactReason": {
          "type": "string",
          "description": "The primary issue or request the customer contacted you about at the start of the interaction."
        },
        "additionalContext": {
          "type": "string",
          "description": "Relevant background details shared during the conversation that help explain the situation."
        },
        "additionalContactReasons": {
          "type": "string",
          "description": "Any new or secondary issues raised after the initial reason for contact."
        },
        "keyActionsTaken": {
          "type": "string",
          "description": "The main steps the agent took to investigate, resolve, or address the customer's request."
        },
        "nextSteps": {
          "type": "string",
          "description": "Clear follow-up actions and expected outcomes agreed upon before ending the interaction."
        },
        "chosenWrapUpCode": {
          "type": "string",
          "description": "The wrap-up reason code that was ultimately selected by the agent at the end of the interaction."
        },
        "proposedWrapUpCodes": {
          "type": [
            "array",
            "null"
          ],
          "description": "A list of wrap-up reasons suggested by the AI based on the interaction content. Each object contains a name field. Can return null, 1, or 2 objects.",
          "items": {
            "$ref": "#/$defs/ProposedWrapUpCode"
          }
        }
      }
    },
    "ProposedWrapUpCode": {
      "type": "object",
      "properties": {
        "name": {
          "type": "string",
          "description": "The name of the proposed wrap-up reason."
        }
      }
    },
    "SearchType": {
      "type": "string",
      "description": "The type of search to be performed.",
      "enum": [
        "ORGANIZATION",
        "INTERACTION",
        "AGENT"
      ]
    }
  }
}

Work with this as data

Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for schemas

4 MCP tools reach this
  • find_json_schemasBrowse and filter every JSON Schema in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/webex-summary-list-response"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.