List timeOffRequest
Namespace: microsoft.graph
Retrieve a list of timeOffRequest objects in the team.
This API is available in the following national cloud deployments.
Global service | US Government L4 | US Government L5 (DOD) | China operated by 21Vianet |
---|---|---|---|
✅ | ❌ | ❌ | ❌ |
Permissions
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.
Permission type | Least privileged permissions | Higher privileged permissions |
---|---|---|
Delegated (work or school account) | Schedule.Read.All | Group.Read.All, Group.ReadWrite.All, Schedule.ReadWrite.All |
Delegated (personal Microsoft account) | Not supported. | Not supported. |
Application | Schedule.Read.All | Schedule.ReadWrite.All |
Note: This API supports admin permissions. Global admins can access groups that they are not a member of. currently in private preview only and are not available for public use.
HTTP request
GET /teams/{teamId}/schedule/timeOffRequests
Optional query parameters
This method supports some of the OData query parameters to help customize the response. For general information, see OData query parameters.
Request headers
Name | Description |
---|---|
Authorization | Bearer {token}. Required. Learn more about authentication and authorization. |
MS-APP-ACTS-AS | A user ID (GUID). Required only if the authorization token is an application token; otherwise, optional. |
Request body
Don't supply a request body for this method.
Response
If successful, this method returns a 200 OK
response code and the requested timeOffRequest objects in the response body.
Examples
Request
The following example shows a request.
GET https://graph.microsoft.com/v1.0/teams/{teamId}/schedule/timeOffRequests
Response
The following example shows the response.
Note: The response object shown here might be shortened for readability.
HTTP/1.1 200 OK
Content-type: application/json
{
"value": [
{
"id": "0b87dd20-d5ed-4764-9c3e-cfc8516def09",
"startDateTime": "datetime-value",
"endDateTime": "datetime-value",
"timeOffReasonId": "timeOffReasonId-value"
}
]
}