Categorized Overview

description bridge actions allow you to control media playback, announcements, recordings, and event routing for all participants connected to a bridge these actions apply at the bridge level , not to individual legs all bridge actions are executed using post /v2/accounts/{accountsid}/bridges/{bridgesid}/actions a media & interaction actions these actions control what all participants in the bridge hear \<startplay> plays an audio file (from a url) to every leg currently joined to the bridge \<stopplay> stops any currently playing audio on the bridge \<startsay> (say) converts text to speech and plays it to all participants in the bridge \<stopsay> stops an ongoing text to speech playback on the bridge b recording actions these actions control bridge level recording , capturing audio from all participants \<startrecording> starts recording the bridge audio supports configurable format and storage destinations \<stoprecording> stops the ongoing bridge recording and finalizes the recording file c event routing & control these actions control how bridge events are delivered to external systems \<refer> registers a grpc endpoint to receive external events for the bridge used for real time monitoring, analytics, or orchestration engines summary — bridge action apis category actions media & interaction startplay, stopplay, startsay, stopsay recording startrecording, stoprecording event routing refer key differences vs leg actions aspect bridge actions leg actions scope all participants single participant media playback broadcast individual recording conference level per leg event routing bridge wide per leg notes for developers bridge actions are asynchronous action success/failure is communicated via bridge external events media actions affect current and future participants use leg actions (joinbridge / leavebridge) to manage membership