@Generated(value="com.amazonaws:aws-java-sdk-code-generator") public class CreateAttendeeRequest extends AmazonWebServiceRequest implements Serializable, Cloneable
NOOP| Constructor and Description |
|---|
CreateAttendeeRequest() |
| Modifier and Type | Method and Description |
|---|---|
CreateAttendeeRequest |
clone()
Creates a shallow clone of this object for all fields except the handler context.
|
boolean |
equals(Object obj) |
AttendeeCapabilities |
getCapabilities()
The capabilities (
audio, video, or content) that you want to grant an
attendee. |
String |
getExternalUserId()
The Amazon Chime SDK external user ID.
|
String |
getMeetingId()
The unique ID of the meeting.
|
int |
hashCode() |
void |
setCapabilities(AttendeeCapabilities capabilities)
The capabilities (
audio, video, or content) that you want to grant an
attendee. |
void |
setExternalUserId(String externalUserId)
The Amazon Chime SDK external user ID.
|
void |
setMeetingId(String meetingId)
The unique ID of the meeting.
|
String |
toString()
Returns a string representation of this object.
|
CreateAttendeeRequest |
withCapabilities(AttendeeCapabilities capabilities)
The capabilities (
audio, video, or content) that you want to grant an
attendee. |
CreateAttendeeRequest |
withExternalUserId(String externalUserId)
The Amazon Chime SDK external user ID.
|
CreateAttendeeRequest |
withMeetingId(String meetingId)
The unique ID of the meeting.
|
addHandlerContext, getCloneRoot, getCloneSource, getCustomQueryParameters, getCustomRequestHeaders, getGeneralProgressListener, getHandlerContext, getReadLimit, getRequestClientOptions, getRequestCredentials, getRequestCredentialsProvider, getRequestMetricCollector, getSdkClientExecutionTimeout, getSdkRequestTimeout, putCustomQueryParameter, putCustomRequestHeader, setGeneralProgressListener, setRequestCredentials, setRequestCredentialsProvider, setRequestMetricCollector, setSdkClientExecutionTimeout, setSdkRequestTimeout, withGeneralProgressListener, withRequestCredentialsProvider, withRequestMetricCollector, withSdkClientExecutionTimeout, withSdkRequestTimeoutpublic void setMeetingId(String meetingId)
The unique ID of the meeting.
meetingId - The unique ID of the meeting.public String getMeetingId()
The unique ID of the meeting.
public CreateAttendeeRequest withMeetingId(String meetingId)
The unique ID of the meeting.
meetingId - The unique ID of the meeting.public void setExternalUserId(String externalUserId)
The Amazon Chime SDK external user ID. An idempotency token. Links the attendee to an identity managed by a builder application.
Pattern: [-_&@+=,(){}\[\]\/«».:|'"#a-zA-Z0-9À-ÿ\s]*
Values that begin with aws: are reserved. You can't configure a value that uses this prefix.
externalUserId - The Amazon Chime SDK external user ID. An idempotency token. Links the attendee to an identity managed by
a builder application.
Pattern: [-_&@+=,(){}\[\]\/«».:|'"#a-zA-Z0-9À-ÿ\s]*
Values that begin with aws: are reserved. You can't configure a value that uses this prefix.
public String getExternalUserId()
The Amazon Chime SDK external user ID. An idempotency token. Links the attendee to an identity managed by a builder application.
Pattern: [-_&@+=,(){}\[\]\/«».:|'"#a-zA-Z0-9À-ÿ\s]*
Values that begin with aws: are reserved. You can't configure a value that uses this prefix.
Pattern: [-_&@+=,(){}\[\]\/«».:|'"#a-zA-Z0-9À-ÿ\s]*
Values that begin with aws: are reserved. You can't configure a value that uses this prefix.
public CreateAttendeeRequest withExternalUserId(String externalUserId)
The Amazon Chime SDK external user ID. An idempotency token. Links the attendee to an identity managed by a builder application.
Pattern: [-_&@+=,(){}\[\]\/«».:|'"#a-zA-Z0-9À-ÿ\s]*
Values that begin with aws: are reserved. You can't configure a value that uses this prefix.
externalUserId - The Amazon Chime SDK external user ID. An idempotency token. Links the attendee to an identity managed by
a builder application.
Pattern: [-_&@+=,(){}\[\]\/«».:|'"#a-zA-Z0-9À-ÿ\s]*
Values that begin with aws: are reserved. You can't configure a value that uses this prefix.
public void setCapabilities(AttendeeCapabilities capabilities)
The capabilities (audio, video, or content) that you want to grant an
attendee. If you don't specify capabilities, all users have send and receive capabilities on all media channels
by default.
You use the capabilities with a set of values that control what the capabilities can do, such as
SendReceive data. For more information about those values, see .
When using capabilities, be aware of these corner cases:
If you specify MeetingFeatures:Video:MaxResolution:None when you create a meeting, all API requests
that include SendReceive, Send, or Receive for
AttendeeCapabilities:Video will be rejected with ValidationError 400.
If you specify MeetingFeatures:Content:MaxResolution:None when you create a meeting, all API
requests that include SendReceive, Send, or Receive for
AttendeeCapabilities:Content will be rejected with ValidationError 400.
You can't set content capabilities to SendReceive or Receive unless you
also set video capabilities to SendReceive or Receive. If you don't set
the video capability to receive, the response will contain an HTTP 400 Bad Request status code.
However, you can set your video capability to receive and you set your content
capability to not receive.
When you change an audio capability from None or Receive to
Send or SendReceive , and if the attendee left their microphone unmuted, audio will
flow from the attendee to the other meeting participants.
When you change a video or content capability from None or
Receive to Send or SendReceive , and if the attendee turned on their video
or content streams, remote attendees can receive those streams, but only after media renegotiation between the
client and the Amazon Chime back-end server.
capabilities - The capabilities (audio, video, or content) that you want to grant
an attendee. If you don't specify capabilities, all users have send and receive capabilities on all media
channels by default.
You use the capabilities with a set of values that control what the capabilities can do, such as
SendReceive data. For more information about those values, see .
When using capabilities, be aware of these corner cases:
If you specify MeetingFeatures:Video:MaxResolution:None when you create a meeting, all API
requests that include SendReceive, Send, or Receive for
AttendeeCapabilities:Video will be rejected with ValidationError 400.
If you specify MeetingFeatures:Content:MaxResolution:None when you create a meeting, all API
requests that include SendReceive, Send, or Receive for
AttendeeCapabilities:Content will be rejected with ValidationError 400.
You can't set content capabilities to SendReceive or Receive unless
you also set video capabilities to SendReceive or Receive. If you
don't set the video capability to receive, the response will contain an HTTP 400 Bad Request
status code. However, you can set your video capability to receive and you set your
content capability to not receive.
When you change an audio capability from None or Receive to
Send or SendReceive , and if the attendee left their microphone unmuted, audio
will flow from the attendee to the other meeting participants.
When you change a video or content capability from None or
Receive to Send or SendReceive , and if the attendee turned on
their video or content streams, remote attendees can receive those streams, but only after media
renegotiation between the client and the Amazon Chime back-end server.
public AttendeeCapabilities getCapabilities()
The capabilities (audio, video, or content) that you want to grant an
attendee. If you don't specify capabilities, all users have send and receive capabilities on all media channels
by default.
You use the capabilities with a set of values that control what the capabilities can do, such as
SendReceive data. For more information about those values, see .
When using capabilities, be aware of these corner cases:
If you specify MeetingFeatures:Video:MaxResolution:None when you create a meeting, all API requests
that include SendReceive, Send, or Receive for
AttendeeCapabilities:Video will be rejected with ValidationError 400.
If you specify MeetingFeatures:Content:MaxResolution:None when you create a meeting, all API
requests that include SendReceive, Send, or Receive for
AttendeeCapabilities:Content will be rejected with ValidationError 400.
You can't set content capabilities to SendReceive or Receive unless you
also set video capabilities to SendReceive or Receive. If you don't set
the video capability to receive, the response will contain an HTTP 400 Bad Request status code.
However, you can set your video capability to receive and you set your content
capability to not receive.
When you change an audio capability from None or Receive to
Send or SendReceive , and if the attendee left their microphone unmuted, audio will
flow from the attendee to the other meeting participants.
When you change a video or content capability from None or
Receive to Send or SendReceive , and if the attendee turned on their video
or content streams, remote attendees can receive those streams, but only after media renegotiation between the
client and the Amazon Chime back-end server.
audio, video, or content) that you want to grant
an attendee. If you don't specify capabilities, all users have send and receive capabilities on all media
channels by default.
You use the capabilities with a set of values that control what the capabilities can do, such as
SendReceive data. For more information about those values, see .
When using capabilities, be aware of these corner cases:
If you specify MeetingFeatures:Video:MaxResolution:None when you create a meeting, all API
requests that include SendReceive, Send, or Receive for
AttendeeCapabilities:Video will be rejected with ValidationError 400.
If you specify MeetingFeatures:Content:MaxResolution:None when you create a meeting, all API
requests that include SendReceive, Send, or Receive for
AttendeeCapabilities:Content will be rejected with ValidationError 400.
You can't set content capabilities to SendReceive or Receive
unless you also set video capabilities to SendReceive or Receive.
If you don't set the video capability to receive, the response will contain an HTTP 400 Bad
Request status code. However, you can set your video capability to receive and you set your
content capability to not receive.
When you change an audio capability from None or Receive to
Send or SendReceive , and if the attendee left their microphone unmuted, audio
will flow from the attendee to the other meeting participants.
When you change a video or content capability from None or
Receive to Send or SendReceive , and if the attendee turned on
their video or content streams, remote attendees can receive those streams, but only after media
renegotiation between the client and the Amazon Chime back-end server.
public CreateAttendeeRequest withCapabilities(AttendeeCapabilities capabilities)
The capabilities (audio, video, or content) that you want to grant an
attendee. If you don't specify capabilities, all users have send and receive capabilities on all media channels
by default.
You use the capabilities with a set of values that control what the capabilities can do, such as
SendReceive data. For more information about those values, see .
When using capabilities, be aware of these corner cases:
If you specify MeetingFeatures:Video:MaxResolution:None when you create a meeting, all API requests
that include SendReceive, Send, or Receive for
AttendeeCapabilities:Video will be rejected with ValidationError 400.
If you specify MeetingFeatures:Content:MaxResolution:None when you create a meeting, all API
requests that include SendReceive, Send, or Receive for
AttendeeCapabilities:Content will be rejected with ValidationError 400.
You can't set content capabilities to SendReceive or Receive unless you
also set video capabilities to SendReceive or Receive. If you don't set
the video capability to receive, the response will contain an HTTP 400 Bad Request status code.
However, you can set your video capability to receive and you set your content
capability to not receive.
When you change an audio capability from None or Receive to
Send or SendReceive , and if the attendee left their microphone unmuted, audio will
flow from the attendee to the other meeting participants.
When you change a video or content capability from None or
Receive to Send or SendReceive , and if the attendee turned on their video
or content streams, remote attendees can receive those streams, but only after media renegotiation between the
client and the Amazon Chime back-end server.
capabilities - The capabilities (audio, video, or content) that you want to grant
an attendee. If you don't specify capabilities, all users have send and receive capabilities on all media
channels by default.
You use the capabilities with a set of values that control what the capabilities can do, such as
SendReceive data. For more information about those values, see .
When using capabilities, be aware of these corner cases:
If you specify MeetingFeatures:Video:MaxResolution:None when you create a meeting, all API
requests that include SendReceive, Send, or Receive for
AttendeeCapabilities:Video will be rejected with ValidationError 400.
If you specify MeetingFeatures:Content:MaxResolution:None when you create a meeting, all API
requests that include SendReceive, Send, or Receive for
AttendeeCapabilities:Content will be rejected with ValidationError 400.
You can't set content capabilities to SendReceive or Receive unless
you also set video capabilities to SendReceive or Receive. If you
don't set the video capability to receive, the response will contain an HTTP 400 Bad Request
status code. However, you can set your video capability to receive and you set your
content capability to not receive.
When you change an audio capability from None or Receive to
Send or SendReceive , and if the attendee left their microphone unmuted, audio
will flow from the attendee to the other meeting participants.
When you change a video or content capability from None or
Receive to Send or SendReceive , and if the attendee turned on
their video or content streams, remote attendees can receive those streams, but only after media
renegotiation between the client and the Amazon Chime back-end server.
public String toString()
toString in class ObjectObject.toString()public CreateAttendeeRequest clone()
AmazonWebServiceRequestclone in class AmazonWebServiceRequestObject.clone()