> For the complete documentation index, see [llms.txt](https://docs.harmony.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.harmony.io/integrations/mdm/addigy-mdm.md). # Addigy MDM The Addigy integration connects Harmony to your Addigy Mobile Device Management (MDM) environment, giving you visibility into your Apple device fleet directly within Harmony. Once connected, Harmony automatically collects and syncs device and application data from Addigy, so your support teams always have accurate, up-to-date context when working with managed devices. ### What Harmony collects from Addigy After connecting Addigy, Harmony syncs the following data from your environment: * **Managed device inventory** - details about all devices enrolled and managed via Addigy * **Installed applications** - a full view of the software installed across those managed devices Harmony keeps this data current so you do not need to manually reconcile information between platforms. ### Creating an API key in Addigy 1. Log in to Addigy as a user whose role can create API keys (the **Create Integrations API Keys** permission). 2. Go to **Account** > **Integrations** > **API & Webhooks**. 3. In the **Addigy API** section, select **New API Token** and give the token at least the **View Devices** and **Execute Commands** permissions, plus permission to view policies. Harmony uses **Execute Commands** only to read the users Addigy lists for each device, which it uses to associate devices with employees. 4. Copy the token. Addigy shows it only once. ### Connecting Addigy to Harmony Addigy uses API key authentication. Your API key is securely masked after entry and is never exposed in plain text within the Harmony interface. To connect Addigy: 1. In Harmony, go to **Settings** and navigate to the **Integrations** section. 2. Find **Addigy** under **MDM** (or search for it by name) and click its card. If an Addigy instance is already connected, click **+ Create instance**. 3. Enter an **Instance name** (required) and your Addigy **API key**. 4. Click **Connect**. Harmony checks the key with Addigy and shows an error if Addigy rejects it. Harmony will begin collecting device and application data from your Addigy environment shortly after the connection is established. #### Multiple Addigy instances If your organization manages more than one Addigy account, you can configure multiple independent Addigy integrations within Harmony. Each instance is set up and managed separately, following the same steps above. ### Application management Applications collected from Addigy are fully reflected across Harmony's Application Management features: * **Software (Applications) page** - Apps sourced from Addigy are listed alongside those from other MDM providers. Addigy is shown as the source so you can easily identify where each application record originates. * **Device application inventory** - Each device managed via Addigy displays its installed applications in the Related Applications section, consistent with how other MDM integrations surface application data. * **Employee association** - Application and device data from Addigy is associated with employees in the same way as other MDM sources, giving you a complete picture of what is installed across your workforce. ### Asset management and direct links From within Harmony's asset management features, you can navigate directly to the corresponding record in your Addigy MDM console. Direct links to Addigy are surfaced alongside your managed assets, so you can jump into your MDM console without manually searching for a device. This reduces context-switching when investigating or managing Apple device records across both Harmony and Addigy. ### Notes * Addigy follows the same setup and management pattern as other MDM integrations in Harmony's settings, so the experience is consistent if you already use other MDM providers. * If you need to update or rotate your API key, open the relevant Addigy instance in **Settings** > **Integrations**, click **Replace** next to **API key**, paste the new key, and click **Save changes**. The new key must belong to the same Addigy organization. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.harmony.io/integrations/mdm/addigy-mdm.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.