title | description | ms.localizationpriority | author | ms.subservice | doc_type |
---|---|---|---|---|---|
swapShiftsChangeRequest: approve |
Approve a swap shift request. |
medium |
akumar39 |
teams |
apiPageType |
Namespace: microsoft.graph
[!INCLUDE beta-disclaimer]
Approve a swapShiftsChangeRequest object.
Note: Only the recipient of the request can approve a swapShiftsChangeRequest.
Choose the permission or permissions marked as least privileged for this API. Use a higher privileged permission or permissions only if your app requires it. For details about delegated and application permissions, see Permission types. To learn more about these permissions, see the permissions reference.
[!INCLUDE permissions-table]
POST /teams/{teamId}/schedule/swapShiftsChangeRequests/{swapShiftChangeRequestId}/approve
Name | Description |
---|---|
Authorization | Bearer {token}. Required. Learn more about authentication and authorization. |
Content-type | application/json. Required. |
MS-APP-ACTS-AS | A user ID (GUID). Required only if the authorization token is an application token; otherwise, optional. |
In the request body, provide a JSON object with the following parameters.
Parameter | Type | Description |
---|---|---|
message | String | A custom approval message. |
If successful, this method returns a 204 No Content
response code. It doesn't return anything in the response body.
The following example shows how to call this API.
The following example shows a request.
POST https://graph.microsoft.com/beta/teams/{teamId}/schedule/swapShiftsChangeRequests/{swapShiftChangeRequestId}/approve
Content-type: application/json
{
"message": "message-value"
}
[!INCLUDE sample-code] [!INCLUDE sdk-documentation]
The following example shows the response.
HTTP/1.1 204 NO CONTENT