OnLink · Device data

Importing Device Data from Device42 to Assets

OnLink imports device data from Device42 into Jira Service Management Assets.

Step 1: Authenticate with the Device42 API

OnLink supports Basic Authentication against the Device42 API. You’ll need your Device42 username and password.

  1. Add Assets Data Source
  2. Give a name to the connection
  3. Select source as API Docs
  4. Give URL as http://api.device42.com/
OnLink Basic Auth settings for the Device42 API
OnLink: Basic Auth connection settings for the Device42 API.

Step 2: Choose your device endpoint

Device42 offers two endpoints depending on how much detail you need.

GET /api/1.0/devices/

Returns core device information. Use this when you only need a lightweight import.

Sample fields:

Device42 Field
Assets Attribute
name
Name
serial_no
Serial Number
asset_no
Asset Number
device_url
Device URL

OnLink Field Mapping

				
					key:serial_no=Serial No
map:asset_no=Asset No
map:device_url=Device URL
map:name=Name
				
			

OnLink Configuration

OnLink endpoint settings to get basic device data from Device42
OnLink: endpoint settings for GET /api/1.0/devices/.
OnLink field mapping from Device42 devices to JSM Assets attributes
OnLink: field mapping from Device42 devices to JSM Assets attributes.

GET /api/1.0/devices/all/

Returns all device details including network and service information (available since v6.3.4). Use this when you need a comprehensive import.

Sample fields:

Device42 Field
Assets Attribute
ip_addresses
IP Addresses
serial_no
Serial Number
hw_depth
Hardware Depth
device_id
Device ID
service_level
Service Level

OnLink Field Mapping

				
					key:serial_no=Serial No
map:ip_addresses=IP
map:device_id=Device ID
map:service_level=Service Level
				
			

Step 3: Use filters to limit records

Both endpoints support query parameters to narrow results and avoid pulling your entire inventory on every sync. Config:

OnLink pagination settings for the Device42 devices endpoint
OnLink: limit/offset pagination settings for the Device42 devices endpoint.

Use filters to target only the devices relevant to your Assets object schema. This keeps imports fast and avoids unnecessary data in your Assets.

Step 4: Import into OnLink and verify in Assets

1. Configure the OnLink connection

Point OnLink to your Device42 API endpoint (either /api/1.0/devices/ or /api/1.0/devices/all/) with your Basic Auth credentials.

2. Map fields

In OnLink, map the Device42 response fields to your Assets object type attributes using the mappings from Step 2.

3. Run the import

Execute the import. OnLink will pull records from Device42 and create or update corresponding objects in Assets.

4. Verify in Assets

Navigate to Assets, and confirm that the imported objects appear with the correct attribute values.

Summary

Step
Action
1
Authenticate using Basic Auth
2
Choose /api/1.0/devices/ (basic) or /api/1.0/devices/all/ (detailed)
3
Apply filters to scope the import
4
Map fields in OnLink, run the import, verify in Assets
The app handles multi-source data imports into Assets well, overcoming gaps in other native solutions. Support has been responsive, and documentation is clear and thorough.
Gikku John
OnLink customer · Atlassian Marketplace review, Sep 2026
Ready to import your Device42 data to Assets?

Try OnLink on the Atlassian Marketplace and bring Device42 devices into JSM Assets this afternoon.

FAQ

Start with /api/1.0/devices/. It returns name, serial number, asset number and the device URL, which is enough for most Assets object types. Switch to /api/1.0/devices/all/ only when you need IP addresses, hardware depth or service level, since the larger payload makes each sync slower.

The mapping declares serial_no as the key. On every run OnLink matches existing Assets objects on that attribute and updates them instead of creating new ones. Choose device_id as the key if some of your devices have no serial number.

The Device42 REST API uses Basic Authentication with a Device42 username and password. Create a dedicated read-only API user for OnLink so the credentials are scoped and can be rotated independently of your admin accounts.

Yes. OnLink is one app for every source: the same instance can pull ServiceNow CMDB, Fleet, NinjaOne, Intune, Jamf and more into the same Assets schema. See the full list of sources and how OnLink compares with single-source importers and iPaaS tools.

On this page

Device42 data in Assets

Start a free trial of OnLink on the Atlassian Marketplace. Device42 is one of 100+ device, identity and HR sources in the same app.

Try OnLink for Device42 to JSM Assets

Try OnLink on the Atlassian Marketplace today.

With Device42 device data in Assets, your team can: