Public APIs - Device Application Retrieval | Help Center

This article provides technical details for retrieving the list of applications installed on a specific device using the Swif.ai Public API.

To optimize performance and reduce payload sizes, the main device inventory API (/restful/organization/devices) no longer includes the full list of installed applications. Instead, you can use this dedicated endpoint to fetch application data for individual devices.

Retrieve Applications for a Specific Device

Use this endpoint to get a detailed list of all applications detected on a managed device.

Endpoint

GET https://api.swifteam.com/restful/organization/devices/:deviceId/applications

EU: api.eu.swifteam.com

CURL Request Example

curl --location 'https://api.swifteam.com/restful/organization/devices/{deviceId}/applications?q=chrome&offset=0&limit=10' \ 
--header 'Authorization: Bearer {YOUR_API_TOKEN}'

Query Parameters

Parameter	Type	Description
`deviceId`	Path	Required. The unique identifier of the device.
`q`	Query	Optional. A case-insensitive fuzzy search query. Searches across application name, bundle name, version, and status.
`limit`	Query	Optional. The maximum number of application records to return.
`offset`	Query	Optional. The number of records to skip (useful for pagination).

Sample JSON Response

{
  "records": [
    {
      "appName": "Google Chrome.app",
      "bundleName": "Google Chrome",
      "displayName": "Google Chrome",
      "executable": "Google Chrome",
      "identifier": "com.google.Chrome",
      "version": "120.0.6099.109",
      "shortVersion": "120.0.6099.109",
      "path": "/Applications/Google Chrome.app",
      "status": "Installed",
      "installedDate": "2023-12-15T10:30:00Z",
      "systemApp": false
    }
  ],
  "meta": {
    "totalCount": 1,
    "resultCount": 1,
    "haveMore": false
  }
}

Security and Access

Authentication: All requests must include a valid Organization API token in the Authorization header as a Bearer token.
Permissions: API keys are restricted to their own organization. Attempting to access a deviceId belonging to another organization will result in a 403 Forbidden or 404 Not Found error.

Error Handling

If the request fails, the API returns a clear error message to assist with troubleshooting:

Invalid Token: "Unable to retrieve organization devices. Please verify your API key and try again."
Device Not Found: Returns a 404 error if the deviceId is incorrect or belongs to a different organization.