Webex · Schema
PostCallSummary
CallingCollaborationCommunicationsEnterpriseMessagingVideo Conferencing
Properties
| Name | Type | Description |
|---|---|---|
| initialContactReason | string | The primary issue or request the customer contacted you about at the start of the interaction. |
| additionalContext | string | Relevant background details shared during the conversation that help explain the situation. |
| additionalContactReasons | string | Any new or secondary issues raised after the initial reason for contact. |
| keyActionsTaken | string | The main steps the agent took to investigate, resolve, or address the customer's request. |
| nextSteps | string | Clear follow-up actions and expected outcomes agreed upon before ending the interaction. |
| chosenWrapUpCode | string | The wrap-up reason code that was ultimately selected by the agent at the end of the interaction. |
| proposedWrapUpCodes | array | 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. |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "#/components/schemas/PostCallSummary",
"title": "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",
"nullable": true,
"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": "#/components/schemas/ProposedWrapUpCode"
}
}
}
}
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.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/webex-postcallsummary"
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.