# Jamf: iOS Mobile devices connector

The Jamf Connector for iOS Mobile Devices allows you to collect additional compliance data from all iOS devices, as well as data from devices on which you cannot install Nexthink Mobile, such as certain bring your own (BYO) devices.

This connector is specifically designed for iOS mobile operating systems. The system uses the operating system's device identifier to match the device imported from Jamf with an existing device.

* If a match is found, the existing device is enriched with data from Jamf.
* If no match is found, the system imports the device as a new entry.

## Device fields <a href="#connectorforcitrixdaas-devicefields" id="connectorforcitrixdaas-devicefields"></a>

The connector for Jamf: iOS Mobile devices imports the following device fields.

| Nexthink Field   | Description                                                                                                                            |
| ---------------- | -------------------------------------------------------------------------------------------------------------------------------------- |
| `mobile_devices` | Contains information about mobile devices, including hardware specifications, operating system details, and Nexthink application data. |

Additionally, the connector populates the following fields in the `mobile_devices.governance` grouping, even for devices that have Nexthink Mobile installed:

|                    |                                                                                                                                                                                                                                                                                                                                                                                                |
| ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `compliance_state` | <p>The current compliance status of the device compared to the organization's compliance policies, as reported by the UEM.</p><p>For Jamf integrations, this status is determined based on the Smart Group configured in the connector under Non-compliant Device Smart Groups. The selected Smart Group must map to a Jamf Smart Group that contains devices identified as non-compliant.</p> |
| `is_encrypted`     | True if device storage is encrypted, as reported by the UEM.                                                                                                                                                                                                                                                                                                                                   |
| `last_synced`      | The last time the UEM successfully synced data with the device.                                                                                                                                                                                                                                                                                                                                |
| `name`             | The device name as assigned in the UEM system.                                                                                                                                                                                                                                                                                                                                                 |
| `ownership_type`   | Indicates the ownership category defined by the UEM.                                                                                                                                                                                                                                                                                                                                           |
| `is_supervised`    | Indicates if the device is supervised by the UEM, allowing deeper management capabilities.                                                                                                                                                                                                                                                                                                     |

## Prerequisite <a href="#configuring-the-connector-credentials" id="configuring-the-connector-credentials"></a>

The connector requires the following permission to be granted in Jamf:

* `DeviceManagementManagedDevices.Read.All`

## Configuring the Connector <a href="#configuring-the-connector-credentials" id="configuring-the-connector-credentials"></a>

Navigate to the **Administration** module and select **Connector credentials** from the **Integrations** section. Create new Connector Credentials for Jamf. See the [Connector credentials](/platform/configuring_nexthink/bringing-data-into-your-nexthink-instance/integrating-nexthink-with-third-party-tools/outbound-connectors/connector-credentials.md) documentation for more information.

Fill the following input fields accordingly; change the `<TENANT_ADDRESS>` to your actual Jamf Cloud tenant address:

<table><thead><tr><th width="240.666748046875">Input field</th><th>Value</th></tr></thead><tbody><tr><td>URL address</td><td><code>https://&#x3C;TENANT_ADDRESS>.jamfcloud.com</code></td></tr><tr><td>Access token URL</td><td><code>https://&#x3C;TENANT_ADDRESS>.jamfcloud.com/api/oauth/token</code></td></tr><tr><td>Authorization information</td><td>Set to <strong>Body</strong></td></tr></tbody></table>

<figure><img src="/files/ieAn98OgIT9MugbktFp9" alt="" width="437"><figcaption></figcaption></figure>

## Configuring the connector for Jamf: iOS Mobile devices

{% stepper %}
{% step %}
Go to **Administration** > **Inbound connectors**.
{% endstep %}

{% step %}
Select **New connector** button in the top-right corner of the page.
{% endstep %}

{% step %}
Select **Jamf: iOS Mobile devices** from the list of connectors.

<figure><img src="/files/YU4oyWmaSGe3MAxxr6aH" alt="Creating a new inbound connector" width="563"><figcaption></figcaption></figure>
{% endstep %}

{% step %}
On the **General** tab:

* Provide a **name** and **description** for your Jamf connector. The **NQL ID** is generated automatically.
* In the **Schedule** section, set how often the connector will fetch data from Jamf.
* In the **Connection** section, select the Jamf credentials you have configured in a previous step.

<figure><img src="/files/Rf05ygpC6kFda75li1oq" alt="" width="536"><figcaption></figcaption></figure>
{% endstep %}

{% step %}
On the **Parameters** tab:

* Select the **Start date** to determine which devices to include. Only devices synced on or after this date will be imported.
* Optionally, select the **Non-compliant device smart groups**. Define one or more groups of non-compliant devices in Jamf, then enter the group name or names in this text box. If you leave this input field empty, the system will not report compliancy information.
* Specify **Device ownership type** to include company-owned, personally-owned or both device types.

<figure><img src="/files/NDTFCymvUjU2PD2Pvw7X" alt="" width="563"><figcaption></figcaption></figure>
{% endstep %}

{% step %}
In Jamf Cloud, go to **Settings > System > API roles and clients**, and grant the following privileges to the newly created Jamf mobile connector:

* Read Mobile Devices
* Read Mobile Device Inventory Collection
  {% endstep %}
  {% endstepper %}

Once you save the connector settings, the system immediately synchronizes with Jamf and continues to synchronize based on the schedule defined in the **General** tab.

## Test results panel

{% hint style="info" %}
The **Test results** panel is available only for supported connectors. Connector availability also depends on your license.
{% endhint %}

Use the **Test results** panel on the right side to run the connector with real data on demand, and inspect responses and errors. The test panel helps with faster debugging and validation during setup, and also with more reliable mappings with less trial and error.

Select the **Run test** button to call the API, and validate the credentials and check connectivity to the targeted endpoint.

<figure><img src="/files/im1NGuQLiTtjQKmRJfRQ" alt=""><figcaption></figcaption></figure>

Besides basic information, such as the response status code and time, the panel also shows a sample record of the response at the bottom.

<figure><img src="/files/Z1VrzzOWvFnxIgsOOKqZ" alt="" width="316"><figcaption></figcaption></figure>

In the event of an error, the system displays the API response to aid in diagnosing the issue.

<figure><img src="/files/le130lodDCk1yPY02v87" alt="" width="309"><figcaption></figcaption></figure>


---

# Agent Instructions: 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:

```
GET https://docs.nexthink.com/platform/configuring_nexthink/bringing-data-into-your-nexthink-instance/integrating-nexthink-with-third-party-tools/inbound-connectors/jamf-ios-mobile-devices-connector.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.