AsyncAPI channel · RingCentral · RingCentral Subscriptions and Event Notifications

/restapi/v1.0/account/{accountId}/extension/{extensionId}/telephony/sessions

Extension telephony sessions event. Documented filter: `/restapi/v1.0/account/{accountId}/extension/{extensionId}/telephony/sessions`. Fires on changes to call sessions for one specific extension. Supports the same query-parameter filters as the account-scoped variant.

Open source AsyncAPI → All RingCentral channels RingCentral provider profile
Provider: RingCentral AsyncAPI: v2.6.0 Spec: RingCentral Subscriptions and Event Notifications Operations: 1 Messages: 1

Channel address

/restapi/v1.0/account/{accountId}/extension/{extensionId}/telephony/sessions

Parameters

Operations

receiveExtensionTelephonySessions
Extension Telephony Sessions Event

Messages

TelephonySessionsEvent
Telephony Sessions Event
Content-Type: application/json

About AsyncAPI

The AsyncAPI specification describes event-driven APIs the way OpenAPI describes request/response APIs. A channel is the named pipe — a webhook URL, a Kafka topic, a WebSocket route, an MQTT subject — that producers and consumers publish or subscribe to. Each channel carries one or more messages with structured payloads, and an operation declares whether a given party sends or receives on that channel.

Browse every event-driven channel on the APIs.io network or compare with the broader Naftiko capability, Agent Skill, and MCP server surfaces of the same providers.