Import Workspace ONE UEM Devices into JSM Assets with OnLink

Use this procedure to configure OnLink, connect to the Workspace ONE UEM API, map device data to JSM Assets attributes, validate the response, and run an import. The procedure uses the Workspace ONE UEM Devices template; adapt the endpoint, response path, and mappings when importing another Workspace ONE resource.

How the integration works

OnLink converts Workspace ONE UEM API responses into JSM Assets objects. Configure a stable key: mapping to identify each object, then add map: mappings for the attributes you want to import. Optional config: statements can be used when required by the selected data source or endpoint.

The high-level process is:

Create or confirm the target JSM Assets schema and object type.
Configure an OnLink Assets Data Source that uses the required authentication to connect to Workspace ONE.
Set the API method and Workspace ONE endpoint, then fetch sample data.
Map Workspace ONE JSON fields to JSM Assets attributes.
Use Get Data to validate the result, then run the import.

Prerequisites

A JSM Assets schema and object type for the data you want to import.
OnLink installed and available from Manage your apps.
Workspace ONE credentials with permission to access the required API endpoints.
Permission in JSM Assets to configure data sources, mappings, and imports.
The Workspace ONE API endpoint URL for the object type you plan to import.

Scope

This procedure targets Workspace ONE UEM devices. The same workflow applies to other Workspace ONE resources when the API endpoint, response data path, and target Assets object type are available. For API reference material, see https://developer.omnissa.com/workspace-one-uem-apis/.

1. Prepare Workspace ONE UEM credentials

Obtain Workspace ONE UEM credentials that can access the device endpoint. For the required API URL and aw-tenant-code, see the https://developer.omnissa.com/workspace-one-uem-apis/#aw-tenant-code-and-rest-api-url.

Keep the username, password, tenant code, API version, and API host available while configuring the OnLink data source.

2. Configure the OnLink data source

In OnLink, add an Assets Data Source.
Set Source to Template.
In the template list, select Workspace ONE UEM - Devices.
- Username
- Password
- aw-tenant-code
- API version, for example 2
- Workspace ONE UEM host or instance name

3. Configure the API request

Configure the request so OnLink retrieves the collection that contains the records to import. The endpoint and response path depend on the Workspace ONE resource.

Set Method to GET.
Replace <your-host> in the URL with your Workspace ONE UEM host or instance name.
Set Response data path to Devices, or to the collection name returned by the selected endpoint.
Leave the remaining settings at their defaults unless the endpoint requires query parameters or other request options.

Refer to this page to create an Asset Import JSM Assets Data Synchronization

4. Fetch and inspect sample data

Save the connection, then run it to retrieve sample values from Workspace ONE UEM. Use the sample JSON to verify the endpoint and identify the field names required for mapping.

Sample response

          "Value": 987
        },
        "Uuid": "1A2B3C4D-5E6F-7A8B-9C0D-1E2F3A4B5C6D",
        "Name": "jdoe"
      },
      "UserName": "jdoe",
      "UserEmailAddress": "john.doe@acme.com",
      "EnrolledDeviceCount": 1,
      "AssignedProfileCount": 8,
      "InstalledProfileCount": 8,
      "AssignedApplicationCount": 12,
      "InstalledApplicationCount": 11
    },
    {
      "DeviceId": 154322,
      "Udid": "9F3D2A1B7C6E4D5F8A9B0C1D2E3F4A5B6C7D8E9F",
      "Uuid": "3A7B9C1D-4E6F-4890-B1C2-D3E4F5A6B7C8",
      "SerialNumber": "5CD1234ABC",
      "MacAddress": "00:1A:2B:3C:4D:5E",
      "ImeiNumber": "356789104567890",
      "AssetNumber": "ASSET-004522",
      "DeviceFriendlyName": "Galaxy S24 - Jane Smith",
      "Model": "SM-S921U",
      "ModelId": 88,
      "Platform": "Android",
      "OperatingSystem": "14",
      "PhoneNumber": "+15555550456",
      "LastSeen": "2026-08-09T09:15:42.000",
      "EnrollmentStatus": "Enrolled",
      "ComplianceStatus": "NonCompliant",
      "Ownership": "E",
      "LocationGroupId": {
        "Id": {
          "Value": 12345
        },
        "Uuid": "069DC0E2-D4E2-E611-8114-005056AF67FF",
        "Name": "Acme Corp / Sales"
      },
      "UserId": {
        "Id": {
          "Value": 988
        },
        "Uuid": "2B3C4D5E-6F7A-8B9C-0D1E-2F3A4B5C6D7E",
        "Name": "jsmith"
      },
      "UserName": "jsmith",
      "UserEmailAddress": "jane.smith@acme.com",
      "EnrolledDeviceCount": 1,
      "AssignedProfileCount": 6,
      "InstalledProfileCount": 5,
      "AssignedApplicationCount": 9,
      "InstalledApplicationCount": 9
    }
  ]
}

5. Configure the Assets import and mappings

After the connection is established, create the Assets import by following the JSM Assets Data Synchronization guide. Select the target schema and object type before configuring attribute mappings.

Use the fetched sample JSON to identify the available Workspace ONE fields and map them to the corresponding JSM Assets attributes. The key: mapping must use a stable, unique value so OnLink can match existing objects and update them instead of creating duplicates.

Workspace ONE column	Value	OnLink mapping	Asset field

Workspace ONE column	Value	OnLink mapping	Asset field
`DeviceId`	`154321`	`key:deviceid=Device ID`	Device ID
`Udid`	`827BE1C5AEC05C378C61C44103E9D3FCB2EC354D`	`map:udid=UDID`	UDID
`Uuid`	`0258902A-9E0C-4DC5-A997-9E079559F75E`	`map:uuid=UUID`	UUID
`SerialNumber`	`C02ZR1XYLVDT`	`map:serialnumber=Serial Number`	Serial Number
`MacAddress`	`AC:BC:32:9E:5D:11`	`map:macaddress=MAC Address`	MAC Address
`ImeiNumber`	`null`	`map:imeinumber=IMEI Number`	IMEI Number
`AssetNumber`	`ASSET-004521`	`map:assetnumber=Asset Number`	Asset Number
`DeviceFriendlyName`	`iPhone 15 Pro - John Doe`	`map:devicefriendlyname=Device Friendly Name`	Device Friendly Name
`Model`	`iPhone`	`map:model=Model`	Model
`ModelId`	`40`	`map:modelid=Model ID`	Model ID
`Platform`	`Apple`	`map:platform=Platform`	Platform
`OperatingSystem`	`17.5.1`	`map:operatingsystem=Operating System`	Operating System

Mapping rules

Start with one unique key: mapping so OnLink can identify whether to create or update an Assets object.
Add map: entries for each Workspace ONE table result field you want to store in Assets.
Compare the Workspace ONE sample JSON with the Assets object type attributes before running an import.
If a value is nested in the JSON response, inspect the sample output carefully and use the field path supported by the OnLink mapping configuration.

6. Validate and run the import

Use Get Data to preview the data returned by Workspace ONE.
Confirm that the sample records contain the expected fields and values.
Verify that the key field maps to a unique JSM Assets attribute.
Review object type mappings and attribute names for spelling and case consistency.
Run the import only after the previewed data and mapping are correct.

Workspace ONE UEM to JSM Assets