GET /drives/{drive-id}/items/{driveItem-id}/delta()
Track changes in a driveItem and its children over time. Your app begins by calling delta without any parameters. The service starts enumerating the drive's hierarchy, returning pages of items and either an @odata.nextLink or an @odata.deltaLink, as described below. Your app should continue calling with the @odata.nextLink until you no longer see an @odata.nextLink returned, or you see a response with an empty set of changes. After you have finished receiving all the changes, you may apply them to your local state. To check for changes in the future, call delta again with the @odata.deltaLink from the previous response. Deleted items are returned with the deleted facet. Items with this property set should be removed from your local state.
Servers
- https://graph.microsoft.com/v1.0
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
drive-id |
String | Yes |
The unique identifier of drive |
driveItem-id |
String | Yes |
The unique identifier of driveItem |
Query parameters
| Name | Type | Required | Description |
|---|---|---|---|
$orderby[] |
Array | No |
Order items by property values |
$top |
Integer | No |
Show only the first n items |
$count |
Boolean | No |
Include count of items |
$filter |
String | No |
Filter items by property values |
$skip |
Integer | No |
Skip the first n items |
$select[] |
Array | No |
Select properties to be returned |
$expand[] |
Array | No |
Expand related entities |
$search |
String | No |
Search items by search phrases |
How to start integrating
- Add HTTP Task to your workflow definition.
- Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
- Click Test request to test run your request to the API and see the API's response.