|
64 | 64 | "Capabilities": { |
65 | 65 | "target": "com.amazonaws.chimesdkmeetings#AttendeeCapabilities", |
66 | 66 | "traits": { |
67 | | - "smithy.api#documentation": "<p>The capabilities (audio, video, or content) assigned to an attendee.</p>" |
| 67 | + "smithy.api#documentation": "<p>The capabilities assigned to an attendee: audio, video, or content.</p>\n <note>\n <p>You use the capabilities with a set of values that control what the capabilities can do, such as <code>SendReceive</code> data. For more information about those values, see \n .</p>\n </note>\n \n <p>When using capabilities, be aware of these corner cases:</p>\n <ul>\n <li>\n <p>You can't set <code>content</code> capabilities to <code>SendReceive</code> or <code>Receive</code> unless you also set <code>video</code> capabilities to <code>SendReceive</code> \n or <code>Receive</code>. If you don't set the <code>video</code> capability to receive, the response will contain an HTTP 400 Bad Request status code. However, you can set your <code>video</code> capability \n to receive and you set your <code>content</code> capability to not receive.</p> \n </li>\n <li>\n <p>When you change an <code>audio</code> capability from <code>None</code> or <code>Receive</code> to <code>Send</code> or <code>SendReceive</code> , \n and if the attendee left their microphone unmuted, audio will flow from the attendee to the other meeting participants.</p>\n </li>\n <li>\n <p>When you change a <code>video</code> or <code>content</code> capability from <code>None</code> or <code>Receive</code> to <code>Send</code> or <code>SendReceive</code> , \n and if the attendee turned on their video or content streams, remote attendess can receive those streams, but only after media renegotiation between the client and the Amazon Chime back-end server.</p>\n </li>\n </ul>" |
68 | 68 | } |
69 | 69 | } |
70 | 70 | }, |
|
98 | 98 | } |
99 | 99 | }, |
100 | 100 | "traits": { |
101 | | - "smithy.api#documentation": "<p>The media capabilities of an attendee, including audio, video and content. </p>" |
| 101 | + "smithy.api#documentation": "<p>The media capabilities of an attendee: audio, video, or content. </p>\n <note>\n <p>You use the capabilities with a set of values that control what the capabilities can do, such as <code>SendReceive</code> data. For more information about those values, see \n .</p>\n </note>\n \n <p>When using capabilities, be aware of these corner cases:</p>\n <ul>\n <li>\n <p>You can't set <code>content</code> capabilities to <code>SendReceive</code> or <code>Receive</code> unless you also set <code>video</code> capabilities to <code>SendReceive</code> \n or <code>Receive</code>. If you don't set the <code>video</code> capability to receive, the response will contain an HTTP 400 Bad Request status code. However, you can set your <code>video</code> capability \n to receive and you set your <code>content</code> capability to not receive.</p> \n </li>\n <li>\n <p>When you change an <code>audio</code> capability from <code>None</code> or <code>Receive</code> to <code>Send</code> or <code>SendReceive</code> , \n and if the attendee left their microphone unmuted, audio will flow from the attendee to the other meeting participants.</p>\n </li>\n <li>\n <p>When you change a <code>video</code> or <code>content</code> capability from <code>None</code> or <code>Receive</code> to <code>Send</code> or <code>SendReceive</code> , \n and if the attendee turned on their video or content streams, remote attendess can receive those streams, but only after media renegotiation between the client and the Amazon Chime back-end server.</p>\n </li>\n </ul>" |
102 | 102 | } |
103 | 103 | }, |
104 | 104 | "com.amazonaws.chimesdkmeetings#AttendeeIdItem": { |
|
288 | 288 | } |
289 | 289 | ], |
290 | 290 | "traits": { |
291 | | - "smithy.api#documentation": "<p>Updates <code>AttendeeCapabilities</code> except the capabilities listed in an <code>ExcludedAttendeeIds</code> table.</p>", |
| 291 | + "smithy.api#documentation": "<p>Updates <code>AttendeeCapabilities</code> except the capabilities listed in an <code>ExcludedAttendeeIds</code> table.</p>\n \n <note>\n <p>You use the capabilities with a set of values that control what the capabilities can do, such as <code>SendReceive</code> data. For more information about those values, see \n .</p>\n </note>\n \n <p>When using capabilities, be aware of these corner cases:</p>\n <ul>\n <li>\n <p>You can't set <code>content</code> capabilities to <code>SendReceive</code> or <code>Receive</code> unless you also set <code>video</code> capabilities to <code>SendReceive</code> \n or <code>Receive</code>. If you don't set the <code>video</code> capability to receive, the response will contain an HTTP 400 Bad Request status code. However, you can set your <code>video</code> capability \n to receive and you set your <code>content</code> capability to not receive.</p> \n </li>\n <li>\n <p>When you change an <code>audio</code> capability from <code>None</code> or <code>Receive</code> to <code>Send</code> or <code>SendReceive</code> , \n and if the attendee left their microphone unmuted, audio will flow from the attendee to the other meeting participants.</p>\n </li>\n <li>\n <p>When you change a <code>video</code> or <code>content</code> capability from <code>None</code> or <code>Receive</code> to <code>Send</code> or <code>SendReceive</code> , \n and if the attendee turned on their video or content streams, remote attendess can receive those streams, but only after media renegotiation between the client and the Amazon Chime back-end server.</p>\n </li>\n </ul>", |
292 | 292 | "smithy.api#http": { |
293 | 293 | "method": "PUT", |
294 | 294 | "uri": "/meetings/{MeetingId}/attendees/capabilities?operation=batch-update-except", |
|
509 | 509 | "Capabilities": { |
510 | 510 | "target": "com.amazonaws.chimesdkmeetings#AttendeeCapabilities", |
511 | 511 | "traits": { |
512 | | - "smithy.api#documentation": "<p>The capabilities (<code>audio</code>, <code>video</code>, or <code>content</code>) that you want to grant an attendee. If you don't specify capabilities, all users have send and receive capabilities on \n all media channels by default.</p>" |
| 512 | + "smithy.api#documentation": "<p>The capabilities (<code>audio</code>, <code>video</code>, or <code>content</code>) that you want to grant an attendee. If you don't specify capabilities, all users have send and receive capabilities on \n all media channels by default.</p>\n \n <note>\n <p>You use the capabilities with a set of values that control what the capabilities can do, such as <code>SendReceive</code> data. For more information about those values, see \n .</p>\n </note>\n \n <p>When using capabilities, be aware of these corner cases:</p>\n <ul>\n <li>\n <p>You can't set <code>content</code> capabilities to <code>SendReceive</code> or <code>Receive</code> unless you also set <code>video</code> capabilities to <code>SendReceive</code> \n or <code>Receive</code>. If you don't set the <code>video</code> capability to receive, the response will contain an HTTP 400 Bad Request status code. However, you can set your <code>video</code> capability \n to receive and you set your <code>content</code> capability to not receive.</p> \n </li>\n <li>\n <p>When you change an <code>audio</code> capability from <code>None</code> or <code>Receive</code> to <code>Send</code> or <code>SendReceive</code> , \n and if the attendee left their microphone unmuted, audio will flow from the attendee to the other meeting participants.</p>\n </li>\n <li>\n <p>When you change a <code>video</code> or <code>content</code> capability from <code>None</code> or <code>Receive</code> to <code>Send</code> or <code>SendReceive</code> , \n and if the attendee turned on their video or content streams, remote attendess can receive those streams, but only after media renegotiation between the client and the Amazon Chime back-end server.</p>\n </li>\n </ul>" |
513 | 513 | } |
514 | 514 | } |
515 | 515 | } |
|
646 | 646 | "traits": { |
647 | 647 | "smithy.api#documentation": "<p>When specified, replicates the media from the primary meeting to the new meeting.</p>" |
648 | 648 | } |
| 649 | + }, |
| 650 | + "TenantIds": { |
| 651 | + "target": "com.amazonaws.chimesdkmeetings#TenantIdList", |
| 652 | + "traits": { |
| 653 | + "smithy.api#documentation": "<p>A consistent and opaque identifier, created and maintained by the builder to represent a segment of their users.</p>" |
| 654 | + } |
649 | 655 | } |
650 | 656 | } |
651 | 657 | }, |
|
755 | 761 | "traits": { |
756 | 762 | "smithy.api#documentation": "<p>When specified, replicates the media from the primary meeting to the new meeting.</p>" |
757 | 763 | } |
| 764 | + }, |
| 765 | + "TenantIds": { |
| 766 | + "target": "com.amazonaws.chimesdkmeetings#TenantIdList", |
| 767 | + "traits": { |
| 768 | + "smithy.api#documentation": "<p>A consistent and opaque identifier, created and maintained by the builder to represent a segment of their users.</p>" |
| 769 | + } |
758 | 770 | } |
759 | 771 | } |
760 | 772 | }, |
|
940 | 952 | "Region": { |
941 | 953 | "target": "com.amazonaws.chimesdkmeetings#TranscribeMedicalRegion", |
942 | 954 | "traits": { |
943 | | - "smithy.api#documentation": "<p>The AWS Region passed to Amazon Transcribe Medical. If you don't specify a Region, Amazon Chime uses the meeting's Region.</p>" |
| 955 | + "smithy.api#documentation": "<p>The AWS Region passed to Amazon Transcribe Medical. If you don't specify a Region, Amazon Chime uses the meeting's Region. </p>" |
944 | 956 | } |
945 | 957 | }, |
946 | 958 | "ContentIdentificationType": { |
|
1483 | 1495 | "traits": { |
1484 | 1496 | "smithy.api#documentation": "<p>When specified, replicates the media from the primary meeting to this meeting.</p>" |
1485 | 1497 | } |
| 1498 | + }, |
| 1499 | + "TenantIds": { |
| 1500 | + "target": "com.amazonaws.chimesdkmeetings#TenantIdList", |
| 1501 | + "traits": { |
| 1502 | + "smithy.api#documentation": "<p>Array of strings.</p>" |
| 1503 | + } |
1486 | 1504 | } |
1487 | 1505 | }, |
1488 | 1506 | "traits": { |
|
1602 | 1620 | } |
1603 | 1621 | }, |
1604 | 1622 | "traits": { |
1605 | | - "smithy.api#documentation": "<p>The service is currently unavailable.</p>", |
| 1623 | + "smithy.api#documentation": "<p>The service encountered an unexpected error.</p>", |
1606 | 1624 | "smithy.api#error": "server", |
1607 | 1625 | "smithy.api#httpError": 500 |
1608 | 1626 | } |
|
1767 | 1785 | } |
1768 | 1786 | } |
1769 | 1787 | }, |
| 1788 | + "com.amazonaws.chimesdkmeetings#TenantId": { |
| 1789 | + "type": "string", |
| 1790 | + "traits": { |
| 1791 | + "smithy.api#length": { |
| 1792 | + "min": 2, |
| 1793 | + "max": 256 |
| 1794 | + }, |
| 1795 | + "smithy.api#pattern": "^(?!.*?(.)\\1{3})[-_!@#$a-zA-Z0-9]*$" |
| 1796 | + } |
| 1797 | + }, |
| 1798 | + "com.amazonaws.chimesdkmeetings#TenantIdList": { |
| 1799 | + "type": "list", |
| 1800 | + "member": { |
| 1801 | + "target": "com.amazonaws.chimesdkmeetings#TenantId" |
| 1802 | + }, |
| 1803 | + "traits": { |
| 1804 | + "smithy.api#length": { |
| 1805 | + "min": 1, |
| 1806 | + "max": 5 |
| 1807 | + } |
| 1808 | + } |
| 1809 | + }, |
1770 | 1810 | "com.amazonaws.chimesdkmeetings#ThrottlingException": { |
1771 | 1811 | "type": "structure", |
1772 | 1812 | "members": { |
|
1781 | 1821 | } |
1782 | 1822 | }, |
1783 | 1823 | "traits": { |
1784 | | - "smithy.api#documentation": "<p>The number of requests exceeds the limit.</p>", |
| 1824 | + "smithy.api#documentation": "<p>The number of customer requests exceeds the request rate limit.</p>", |
1785 | 1825 | "smithy.api#error": "client", |
1786 | 1826 | "smithy.api#httpError": 429 |
1787 | 1827 | } |
|
2186 | 2226 | } |
2187 | 2227 | ], |
2188 | 2228 | "traits": { |
2189 | | - "smithy.api#documentation": "<p>The capabilties that you want to update.</p>", |
| 2229 | + "smithy.api#documentation": "<p>The capabilties that you want to update.</p>\n <note>\n <p>You use the capabilities with a set of values that control what the capabilities can do, such as <code>SendReceive</code> data. For more information about those values, see \n .</p>\n </note>\n \n <p>When using capabilities, be aware of these corner cases:</p>\n <ul>\n <li>\n <p>You can't set <code>content</code> capabilities to <code>SendReceive</code> or <code>Receive</code> unless you also set <code>video</code> capabilities to <code>SendReceive</code> \n or <code>Receive</code>. If you don't set the <code>video</code> capability to receive, the response will contain an HTTP 400 Bad Request status code. However, you can set your <code>video</code> capability \n to receive and you set your <code>content</code> capability to not receive.</p> \n </li>\n <li>\n <p>When you change an <code>audio</code> capability from <code>None</code> or <code>Receive</code> to <code>Send</code> or <code>SendReceive</code> , \n and if the attendee left their microphone unmuted, audio will flow from the attendee to the other meeting participants.</p>\n </li>\n <li>\n <p>When you change a <code>video</code> or <code>content</code> capability from <code>None</code> or <code>Receive</code> to <code>Send</code> or <code>SendReceive</code> , \n and if the attendee turned on their video or content streams, remote attendess can receive those streams, but only after media renegotiation between the client and the Amazon Chime back-end server.</p>\n </li>\n </ul>", |
2190 | 2230 | "smithy.api#http": { |
2191 | 2231 | "method": "PUT", |
2192 | 2232 | "uri": "/meetings/{MeetingId}/attendees/{AttendeeId}/capabilities", |
|
2226 | 2266 | "type": "structure", |
2227 | 2267 | "members": { |
2228 | 2268 | "Attendee": { |
2229 | | - "target": "com.amazonaws.chimesdkmeetings#Attendee" |
| 2269 | + "target": "com.amazonaws.chimesdkmeetings#Attendee", |
| 2270 | + "traits": { |
| 2271 | + "smithy.api#documentation": "<p>The updated attendee data.</p>" |
| 2272 | + } |
2230 | 2273 | } |
2231 | 2274 | } |
2232 | 2275 | } |
|
0 commit comments