Webex · Schema
TelephonyParams
Telephony channel parameters.
CallingCollaborationCommunicationsEnterpriseMessagingVideo Conferencing
Properties
| Name | Type | Description |
|---|---|---|
| type | string | Must be `telephony` for telephony channel parameters. |
| outdialEntryPointId | string | UUID of the entry point for the task. For `CALLBACK` and `OUTDIAL`, this must be an outbound entry point. For `EXECUTE_FLOW`, this must be an inbound entry point mapped to the flow to be triggered. ** |
| outboundType | string | The outbound type for the task. Use `OUTDIAL` when the agent needs to make an outbound call to the customer. Use `CALLBACK` when scheduling a callback — `callback` field is required. Use `EXECUTE_FLOW |
| callback | object | Required when `outboundType` is `CALLBACK`. Must be omitted or `null` for `OUTDIAL`, `EXECUTE_FLOW`, and `RECORD_GREETING`. When provided, `type` must be `immediate` and `origin` must be `web`. **Migr |
| sipHeaders | object | Optional map of SIP headers forwarded to the telephony infrastructure for the call. Supports up to 20 headers (selected alphabetically if more than 20 are provided). Each key is converted to lowercase |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "#/components/schemas/TelephonyParams",
"title": "TelephonyParams",
"type": "object",
"description": "Telephony channel parameters.",
"required": [
"type",
"outdialEntryPointId",
"outboundType"
],
"properties": {
"type": {
"type": "string",
"enum": [
"telephony"
],
"description": "Must be `telephony` for telephony channel parameters.",
"example": "telephony"
},
"outdialEntryPointId": {
"type": "string",
"description": "UUID of the entry point for the task. For `CALLBACK` and `OUTDIAL`, this must be an outbound entry point. For `EXECUTE_FLOW`, this must be an inbound entry point mapped to the flow to be triggered. **Migrating from v1:** Previously named `entryPointId`.",
"example": "aef6455f-ccd6-4261-bb00-e80f845c01b0"
},
"outboundType": {
"type": "string",
"description": "The outbound type for the task. Use `OUTDIAL` when the agent needs to make an outbound call to the customer. Use `CALLBACK` when scheduling a callback \u2014 `callback` field is required. Use `EXECUTE_FLOW` to trigger a predefined flow through an inbound entry point. Use `RECORD_GREETING` to record a personalized agent greeting.",
"enum": [
"CALLBACK",
"OUTDIAL",
"EXECUTE_FLOW",
"RECORD_GREETING"
],
"example": "CALLBACK"
},
"callback": {
"type": "object",
"allOf": [
{
"$ref": "#/components/schemas/CallbackParams"
}
],
"nullable": true,
"description": "Required when `outboundType` is `CALLBACK`. Must be omitted or `null` for `OUTDIAL`, `EXECUTE_FLOW`, and `RECORD_GREETING`. When provided, `type` must be `immediate` and `origin` must be `web`. **Migrating from v1:** Previously a top-level `callback` object with fields `callbackType` and `callbackOrigin`; now nested under `channelParams`."
},
"sipHeaders": {
"type": "object",
"nullable": true,
"description": "Optional map of SIP headers forwarded to the telephony infrastructure for the call. Supports up to 20 headers (selected alphabetically if more than 20 are provided). Each key is converted to lowercase with hyphens retained. The payload is restricted to 1100 bytes to comply with RFC 3261 (UDP). Header values are not logged to ensure PII protection. **Migrating from v1:** Previously named `customAttributes`.",
"additionalProperties": {
"type": "string"
},
"example": {
"X-Correlation-Id": "12345"
}
}
}
}
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-telephonyparams"
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.