> 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.

### 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. Locate **Addigy** under the MDM integrations and select the option to add a new connection.
3. Enter your Addigy API key when prompted.
4. Save the configuration.

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, return to the integration settings in Harmony and update the credential for the relevant Addigy instance.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.harmony.io/integrations/mdm/addigy-mdm.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.