Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Namespace: microsoft.graph
Important
APIs under the /beta
version in Microsoft Graph are subject to change. Use of these APIs in production applications is not supported. To determine whether an API is available in v1.0, use the Version selector.
Confirm a specific timeCard for a user.
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) | Not supported. | Not supported. |
Delegated (personal Microsoft account) | Not supported. | Not supported. |
Application | Schedule.ReadWrite.All | Not available. |
HTTP request
POST /teams/{teamsId}/schedule/timeCards/{timeCardId}/confirmForUser
Request headers
Name | Description |
---|---|
Authorization | Bearer {token}. Required. Learn more about authentication and authorization. |
Content-Type | application/json. Required. |
Request body
In the request body, supply a JSON representation of the parameters.
The following table lists the parameters that are required when you call this action.
Parameter | Type | Description |
---|---|---|
userId | String | The ID of the user who confirms the timeCard. |
Response
If successful, this action returns a 200 OK
response code and a timeCard object in the response body.
Examples
Request
The following example shows a request.
POST https://graph.microsoft.com/beta/teams/fd15cad8-80f6-484f-9666-3caf695fbf32/schedule/timeCards/TCK_95c44dff-bc12-4de2-8a9a-9772e4421eb4/confirmForUser
Content-Type: application/json
{
"userId": "d56f3e8a-2b0f-42b1-88b9-e2dbd12a34d2"
}
Response
The following example shows the response.
HTTP/1.1 200 OK
Content-Type: application/json
{
"id": "TCK_95c44dff-bc12-4de2-8a9a-9772e4421eb4",
"createdDateTime": "2025-01-08T15:44:09.545Z",
"lastModifiedDateTime": "2025-01-08T19:45:25.048Z",
"userId": "d56f3e8a-2b0f-42b1-88b9-e2dbd12a34d2",
"state": "clockedOut",
"confirmedBy": "user",
"notes": null,
"lastModifiedBy": {
"application": null,
"device": null,
"user": {
"id": "d56f3e8a-2b0f-42b1-88b9-e2dbd12a34d2",
"displayName": "Alice Bradford"
}
},
"clockInEvent": {
"dateTime": "2025-01-08T15:44:09.545Z",
"isAtApprovedLocation": null,
"notes": null
},
"clockOutEvent": {
"dateTime": "2025-01-07T19:45:25.048Z",
"isAtApprovedLocation": null,
"notes": null
},
"breaks": [],
"originalEntry": {
"clockInEvent": {
"dateTime": "2025-01-07T15:44:09.545Z",
"isAtApprovedLocation": null,
"notes": null
},
"clockOutEvent": {
"dateTime": "2025-01-07T19:45:25.048Z",
"isAtApprovedLocation": null,
"notes": null
},
"breaks": []
},
"createdBy": {
"application": null,
"device": null,
"user": {
"id": "d56f3e8a-2b0f-42b1-88b9-e2dbd12a34d2",
"displayName": "Alice Bradford"
}
}
}