---
title: "Gets the list of applications deployed on a Service Fabric node."
method: GET
path: "/Nodes/{nodeName}/$/GetApplications"
tags: ["Application"]
---

# Gets the list of applications deployed on a Service Fabric node.

`GET /Nodes/{nodeName}/$/GetApplications`

Gets the list of applications deployed on a Service Fabric node. The results do not include information about deployed system applications unless explicitly queried for by ID. Results encompass deployed applications in active, activating, and downloading states. This query requires that the node name corresponds to a node on the cluster. The query fails if the provided node name does not point to any active Service Fabric nodes on the cluster.

## Path parameters

- `nodeName` string, required

## Query parameters

- `api-version` '6.1', required
- `timeout` integer
- `IncludeHealthState` boolean
- `ContinuationToken` string
- `MaxResults` integer

## Response `200`

A successful operation will return 200 status code and the list of deployed application information.

- PagedDeployedApplicationInfoList — The list of deployed applications in activating, downloading, or active states on a node. The list is paged when all of the results cannot fit in a single message. The next set of results can be obtained by executing the same query with the continuation token provided in this list.
  - `ContinuationToken` string — The continuation token parameter is used to obtain next set of results. The continuation token is included in the response of the API when the results from the system do not fit in a single response. When this value is passed to the next API call, the API returns next set of results. If there are no further results, then the continuation token is not included in the response.
  - `Items` DeployedApplicationInfo[] — List of deployed application information.
    - `Id` string — The identity of the application. This is an encoded representation of the application name. This is used in the REST APIs to identify the application resource. Starting in version 6.0, hierarchical names are delimited with the "\~" character. For example, if the application name is "fabric:/myapp/app1", the application identity would be "myapp\~app1" in 6.0+ and "myapp/app1" in previous versions.
    - `Name` string — The name of the application, including the 'fabric:' URI scheme.
    - `TypeName` string — The application type name as defined in the application manifest.
    - `Status` 'Invalid' | 'Downloading' | 'Activating' | 'Active' | 'Upgrading' | 'Deactivating' — The status of the application deployed on the node. Following are the possible values.
    - `WorkDirectory` string — The work directory of the application on the node. The work directory can be used to store application data.
    - `LogDirectory` string — The log directory of the application on the node. The log directory can be used to store application logs.
    - `TempDirectory` string — The temp directory of the application on the node. The code packages belonging to the application are forked with this directory set as their temporary directory.
    - `HealthState` 'Invalid' | 'Ok' | 'Warning' | 'Error' | 'Unknown' — The health state of a Service Fabric entity such as Cluster, Node, Application, Service, Partition, Replica etc.

## Other responses

- `default` — The detailed error response.

---

[API](https://skmtc.net/azure/apis/service-fabric-client-apis.md) · [All operations](https://skmtc.net/azure/apis/service-fabric-client-apis/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/azure/service-fabric-client-apis/versions/6df9f2f4d542/schema)