Create a Video Bridge and Manage Its Lifecycle

Create a Video Bridge and Manage Its Lifecycle

Create a video bridge, capture its join details, resolve it by PIN, rotate its password, and delete it.

1. Create a Scheduled bridge for the extension. Scheduled bridges survive across multiple meetings, unlike Instant bridges which are deleted right after their single use. RingCentral generates the Web PIN when one is not supplied.
2. Read the bridge back to capture the join URI. discovery.web only carries the embedded password parameter when the caller is the bridge owner, a delegate, or a Super Admin, so this read is what produces a distributable join link.
3. Look the bridge up by its Web PIN. This is the lookup behind a join-by-code screen, where a participant supplies only the meeting code.
4. Update the bridge to rotate the meeting password. Note the update operation is a PATCH and cannot change the Web PIN — the spec routes PIN changes to a dedicated endpoint instead.
5. Delete the bridge when the recurring meeting series ends so the Web PIN and join URI stop resolving.

What you'll need to have ready

• accountId: Internal identifier of the RingCentral account. Use "~" for the account associated with the current authorization session.
• extensionId: Internal identifier of the extension that owns the bridge. Use "~" for the extension associated with the current authorization session.
• bridgeName: Custom name of the bridge (e.g. "Weekly Design Review").
• password: Meeting password. When passwordProtected is true and this is omitted, RingCentral generates one.
• rotatedPassword: The replacement meeting password applied by the update step.
• waitingRoomRequired: Waiting room policy before the host starts the meeting. One of Nobody, Everybody, GuestsOnly, OtherAccount.

For your developer

Arazzo workflow ringcentral:video-bridge-lifecycle, 5 operations: createBridge → getBridge → getBridgeByWebPin → updateBridge → deleteBridge. Specs on APIs.io.