ms:rtc:saas:accept
- JSON
Accepts an incoming invitation.
Web link
For more on web links, see Web Links.
| Name | Description |
|---|---|
| rel | The resource that this link points to. In JSON, this is the outer container. |
| href | The location of this resource on the server, and the target of an HTTP operation. |
Resource description
This resource is used to accept an incoming ms:rtc:saas:messagingInvitation or ms:rtc:saas:onlineMeetingInvitation as part of a new or existing ms:rtc:saas:conversation. An application can determine whether the invitation was successfully accepted based on whether the corresponding invitation completed with success. For an incoming ms:rtc:saas:messagingInvitation, accept will change the status of the instant messaging modality to "Connected" in the corresponding conversation. Subsequently the application will be able to send and receive messages and typing notifications.. For an incoming ms:rtc:saas:onlineMeetingInvitation, accept will make the user join the corresponding ms:rtc:saas:onlineMeeting. The ms:rtc:saas:conversation state will change to conferenced. Note that the application is then responsible for joining a modality. .
Properties
None
Links
None
Operations
Accepts an incoming invitation.
Request body
Click here to see the input values.
| Name | Description | Required? |
|---|---|---|
| mediaHost | Sets whether to provision media remotely for the applciation. | No |
Response body
None
Synchronous errors
The errors below (if any) are specific to this resource. Generic errors that can apply to any resource are covered in Generic synchronous errors.
| Error | Code | Subcode | Description |
|---|---|---|---|
| ServiceFailure | 500 | CallbackChannelError | |
| Conflict | 409 | AlreadyExists | |
| Conflict | 409 | TooManyGroups | |
| Conflict | 409 | None | |
| Gone | 410 | CannotRedirect |
Examples
Request
JSON Response
This sample is given only as an illustration of response syntax. The semantic content is not guaranteed to correspond to a valid scenario.