Sign in

8d602198ec97

latestOpenAPI 3.0.3RingCentral API License Agreement2026-08-064871,2921.5 MB
Call Control

Bring-In Call Party

Adds a new party to the call session by bringing in an established SIP call connection. The maximum number of parties to bring in is 10; only 1 call party can be added per request. Currently, the method is supported for sessions of the Conference origin only.

post/restapi/v1.0/account/{accountId}/telephony/sessions/{telephonySessionId}/parties/bring-in

Path parameters

accountIdstring required

Internal identifier of the RingCentral account (can be set to "~" to indicate that the account associated with current authorization session should be used)

telephonySessionIdstring required

Internal identifier of a call session

Request body

sessionIdstring required

Internal identifier of a call session

partyIdstring required

Internal identifier of a party that should be added to the call session

Response

Created

idstring

Internal identifier of a party

mutedboolean

Specifies if a call participant is muted or not. Note: If a call is also controlled via Hard phone or RingCentral App (not only through the API by calling call control methods) then it cannot be fully muted/unmuted via API only, in this case the action should be duplicated via Hard phone/RC App interfaces

standAloneboolean

If true then the party is not connected to a session voice conference, false means the party is connected to other parties in a session

direction'Inbound' | 'Outbound'

Direction of a call

conferenceRole'Host' | 'Participant'

A party's role in the conference scenarios. For calls of 'Conference' type only

ringOutRole'Initiator' | 'Target'

A party's role in 'Ring Me'/'RingOut' scenarios. For calls of 'Ringout' type only

ringMeRole'Initiator' | 'Target'

A party's role in 'Ring Me'/'RingOut' scenarios. For calls of 'Ringme' type only