application: delta
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.
Get newly created, updated, or deleted applications without having to perform a full read of the entire resource collection. For more information, see Use delta query to track changes in Microsoft Graph data for details.
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) | Directory.Read.All | Application.Read.All, Application.ReadWrite.All, Directory.ReadWrite.All |
Delegated (personal Microsoft account) | Not supported. | Not supported. |
Application | Application.ReadWrite.OwnedBy | Application.Read.All, Application.ReadWrite.All, Directory.Read.All, Directory.ReadWrite.All |
HTTP request
To begin tracking changes, you make a request including the delta function on the application resource.
GET /applications/delta
Query parameters
Tracking changes incurs a round of one or more delta function calls. If you use any query parameter
(other than $deltatoken
and $skiptoken
), you must specify
it in the initial delta request. Microsoft Graph automatically encodes any specified parameters
into the token portion of the @odata.nextLink
or @odata.deltaLink
URL provided in the response.
You only need to specify any desired query parameters once upfront.
In subsequent requests, copy and apply the @odata.nextLink
or @odata.deltaLink
URL from the previous response, as that URL already
includes the encoded, desired parameters.
Query parameter | Type | Description |
---|---|---|
$deltatoken | string | A state token returned in the @odata.deltaLink URL of the previous delta function call for the same resource collection, indicating the completion of that round of change tracking. Save and apply the entire @odata.deltaLink URL including this token in the first request of the next round of change tracking for that collection. |
$skiptoken | string | A state token returned in the @odata.nextLink URL of the previous delta function call, indicating there are further changes to be tracked in the same resource collection. |
Optional query parameters
This method supports OData Query Parameters to help customize the response.
You can use a
$select
query parameter as in any GET request to specify only the properties your need for best performance. The id property is always returned.There is limited support for
$filter
:- The only supported
$filter
expression is for tracking changes for specific resources, by their id:$filter=id+eq+{value}
or$filter=id+eq+{value1}+or+id+eq+{value2}
. The number of ids you can specify is limited by the maximum URL length.
- The only supported
Request headers
Name | Description |
---|---|
Authorization | Bearer {token}. Required. Learn more about authentication and authorization. |
Content-Type | application/json |
Request body
Don't supply a request body for this method.
Response
If successful, this method returns 200 OK
response code and application collection object in the response body. The response also includes a nextLink URL or a deltaLink URL.
If a
@odata.nextLink
URL is returned, there are more pages of data to be retrieved in the session. The application continues making requests by using the@odata.nextLink
URL until a@odata.deltaLink
URL is included in the response.If a
@odata.deltaLink
URL is returned, there is no more data about the existing state of the resource to be returned. Persist and use the@odata.deltaLink
URL to learn about changes to the resource in the future.
See:
- Using Delta Query for more details
- Get incremental changes for users for an example request.
Example
Request
GET https://graph.microsoft.com/beta/applications/delta
Response
Note: The response object shown here might be shortened for readability.
HTTP/1.1 200 OK
Content-type: application/json
{
"@odata.context":"https://graph.microsoft.com/beta/$metadata#applications",
"@odata.nextLink":"https://graph.microsoft.com/beta/applications/delta?$skiptoken=pqwSUjGYvb3jQpbwVAwEL7yuI3dU1LecfkkfLPtnIjsXoYQp_dpA3cNJWc",
"value": [
{
"api": {
"acceptedAccessTokenVersion": 1,
"publishedPermissionScopes": [
{
"adminConsentDescription": "adminConsentDescription-value",
"adminConsentDisplayName": "adminConsentDisplayName-value",
"id": "id-value",
"isEnabled": true,
"type": "type-value",
"userConsentDescription": "userConsentDescription-value",
"userConsentDisplayName": "userConsentDisplayName-value",
"value": "value-value"
}
]
},
"allowPublicClient": true,
"applicationAliases": [
"applicationAliases-value"
],
"createdDateTime": "datetime-value",
"installedClients": {
"redirectUrls": [
"redirectUrls-value"
]
}
}
]
}