Conference Participant Resource

The SID of the Account that created the Participant resource.

The SID of the Call the Participant resource is associated with.

The user-specified label of this participant, if one was given when the participant was created. This may be used to fetch, update or delete the participant.

The SID of the participant who is being coached. The participant being coached is the only participant who can hear the participant who is coaching.

Whether the participant is coaching another call. Can be: true or false. If not present, defaults to false unless call_sid_to_coach is defined. If true, call_sid_to_coach must be defined.

The SID of the conference the participant is in.

The date and time in GMT that the resource was created specified in RFC 2822 format.

The date and time in GMT that the resource was last updated specified in RFC 2822 format.

Whether the conference ends when the participant leaves. Can be: true or false and the default is false. If true, the conference ends and all other participants drop out when the participant leaves.

Whether the participant is muted. Can be true or false.

Whether the participant is on hold. Can be true or false.

Whether the conference starts when the participant joins the conference, if it has not already started. Can be: true or false and the default is true. If false and the conference has not started, the participant is muted and hears background music until another participant starts the conference.

The status of the participant's call in a session. Can be: queued, connecting, ringing, connected, complete, or failed.

The URI of the resource, relative to https://api.twilio.com.

The SID of the Account that will create the resource.

The SID of the participant's conference.

The phone number, Client identifier, or username portion of SIP address that made this call. Phone numbers are in E.164 format (e.g., +16175551212). Client identifiers are formatted client:name. If using a phone number, it must be a Twilio number or a Verified outgoing caller id for your account. If the to parameter is a phone number, from must also be a phone number. If to is sip address, this value of from should be a username portion to be used to populate the P-Asserted-Identity header that is passed to the SIP endpoint.

The phone number, SIP address, or Client identifier that received this call. Phone numbers are in E.164 format (e.g., +16175551212). SIP addresses are formatted as sip:name@company.com. Client identifiers are formatted client:name. Custom parameters may also be specified.

The URL we should call using the status_callback_method to send status information to your application.

The HTTP method we should use to call status_callback. Can be: GET and POST and defaults to POST.

The conference state changes that should generate a call to status_callback. Can be: initiated, ringing, answered, and completed. Separate multiple values with a space. The default value is completed.

A label for this participant. If one is supplied, it may subsequently be used to fetch, update or delete the participant.

The number of seconds that we should allow the phone to ring before assuming there is no answer. Can be an integer between 5 and 600, inclusive. The default value is 60. We always add a 5-second timeout buffer to outgoing calls, so value of 10 would result in an actual timeout that was closer to 15 seconds.

Whether to record the participant and their conferences, including the time between conferences. Can be true or false and the default is false.

Whether the agent is muted in the conference. Can be true or false and the default is false.

Whether to play a notification beep to the conference when the participant joins. Can be: true, false, onEnter, or onExit. The default value is true.

Whether to start the conference when the participant joins, if it has not already started. Can be: true or false and the default is true. If false and the conference has not started, the participant is muted and hears background music until another participant starts the conference.

Whether to end the conference when the participant leaves. Can be: true or false and defaults to false.

The URL we should call using the wait_method for the music to play while participants are waiting for the conference to start. The default value is the URL of our standard hold music. Learn more about hold music.

The HTTP method we should use to call wait_url. Can be GET or POST and the default is POST. When using a static audio file, this should be GET so that we can cache the file.

Whether to allow an agent to hear the state of the outbound call, including ringing or disconnect messages. Can be: true or false and defaults to true.

The maximum number of participants in the conference. Can be a positive integer from 2 to 250. The default value is 250.

Whether to record the conference the participant is joining. Can be: true, false, record-from-start, and do-not-record. The default value is false.

Whether to trim leading and trailing silence from your recorded conference audio files. Can be: trim-silence or do-not-trim and defaults to trim-silence.

The URL we should call using the conference_status_callback_method when the conference events in conference_status_callback_event occur. Only the value set by the first participant to join the conference is used. Subsequent conference_status_callback values are ignored.

The HTTP method we should use to call conference_status_callback. Can be: GET or POST and defaults to POST.

The conference state changes that should generate a call to conference_status_callback. Can be: start, end, join, leave, mute, hold, modify, speaker, and announcement. Separate multiple values with a space. Defaults to start end.

The recording channels for the final recording. Can be: mono or dual and the default is mono.

The URL that we should call using the recording_status_callback_method when the recording status changes.

The HTTP method we should use when we call recording_status_callback. Can be: GET or POST and defaults to POST.

The SIP username used for authentication.

The SIP password for authentication.

The region where we should mix the recorded audio. Can be:us1, ie1, de1, sg1, br1, au1, or jp1.

The URL we should call using the conference_recording_status_callback_method when the conference recording is available.

The HTTP method we should use to call conference_recording_status_callback. Can be: GET or POST and defaults to POST.

The recording state changes that should generate a call to recording_status_callback. Can be: started, in-progress, paused, resumed, stopped, completed, failed, and absent. Separate multiple values with a space, ex: 'in-progress completed failed'.

The conference recording state changes that generate a call to conference_recording_status_callback. Can be: in-progress, completed, failed, and absent. Separate multiple values with a space, ex: 'in-progress completed failed'

Whether the participant is coaching another call. Can be: true or false. If not present, defaults to false unless call_sid_to_coach is defined. If true, call_sid_to_coach must be defined.

The SID of the participant who is being coached. The participant being coached is the only participant who can hear the participant who is coaching.

Jitter buffer size for the connecting participant. Twilio will use this setting to apply Jitter Buffer before participant's audio is mixed into the conference. Can be: off, small, medium, and large. Default to large.

The SID of a BYOC (Bring Your Own Carrier) trunk to route this call with. Note that byoc is only meaningful when to is a phone number; it will otherwise be ignored. (Beta)

The phone number, Client identifier, or username portion of SIP address that made this call. Phone numbers are in E.164 format (e.g., +16175551212). Client identifiers are formatted client:name. If using a phone number, it must be a Twilio number or a Verified outgoing caller id for your account. If the to parameter is a phone number, callerId must also be a phone number. If to is sip address, this value of callerId should be a username portion to be used to populate the From header that is passed to the SIP endpoint.

The Reason for the outgoing call. Use it to specify the purpose of the call that is presented on the called party's phone. (Branded Calls Beta)

The audio track to record for the call. Can be: inbound, outbound or both. The default is both. inbound records the audio that is received by Twilio. outbound records the audio that is sent from Twilio. both records the audio that is received and sent by Twilio.

The maximum duration of the call in seconds. Constraints depend on account and configuration.

The SID of the Account that created the Participant resource to fetch.

The SID of the conference with the participant to fetch.

The Call SID or label of the participant to fetch. Non URL safe characters in a label must be percent encoded, for example, a space character is represented as %20.

The SID of the Account that created the Participant resources to read.

The SID of the conference with the participants to read.

Whether to return only participants that are muted. Can be: true or false.

Whether to return only participants that are on hold. Can be: true or false.

Whether to return only participants who are coaching another call. Can be: true or false.

The SID of the Account that created the Participant resources to update.

The SID of the conference with the participant to update.

The Call SID or label of the participant to update. Non URL safe characters in a label must be percent encoded, for example, a space character is represented as %20.

Whether the participant should be muted. Can be true or false. true will mute the participant, and false will un-mute them. Anything value other than true or false is interpreted as false.

Whether the participant should be on hold. Can be: true or false. true puts the participant on hold, and false lets them rejoin the conference.

The URL we call using the hold_method for music that plays when the participant is on hold. The URL may return an MP3 file, a WAV file, or a TwiML document that contains the <Play>, <Say> or <Redirect> commands.

The HTTP method we should use to call hold_url. Can be: GET or POST and the default is GET.

The URL we call using the announce_method for an announcement to the participant. The URL must return an MP3 file, a WAV file, or a TwiML document that contains <Play> or <Say> commands.

The HTTP method we should use to call announce_url. Can be: GET or POST and defaults to POST.

The URL we should call using the wait_method for the music to play while participants are waiting for the conference to start. The default value is the URL of our standard hold music. Learn more about hold music.

The HTTP method we should use to call wait_url. Can be GET or POST and the default is POST. When using a static audio file, this should be GET so that we can cache the file.

Whether to play a notification beep to the conference when the participant exits. Can be: true or false.

Whether to end the conference when the participant leaves. Can be: true or false and defaults to false.

Whether the participant is coaching another call. Can be: true or false. If not present, defaults to false unless call_sid_to_coach is defined. If true, call_sid_to_coach must be defined.

The SID of the participant who is being coached. The participant being coached is the only participant who can hear the participant who is coaching.

The SID of the Account that created the Participant resources to delete.

The SID of the conference with the participants to delete.

The Call SID or label of the participant to delete. Non URL safe characters in a label must be percent encoded, for example, a space character is represented as %20.