In this blog we will cover how to import people and devices data from Kolide to Assets.
OnLink lets you import People and Devices from Kolide into Assets by connecting to the Kolide API, and mapping fields such as id, name, email, operating_system, and hardware_model to your Assets schema. The sync can then run manually or on a schedule.
Kolide is a device-trust and endpoint visibility platform that ensures only secure, compliant devices can access company applications. It focuses on zero-trust access, user transparency, and lightweight device checks.
Kolide exposes a People API:
API Endpoint:
GET https://kolideapi.readme.io/reference/get_people
{
"id": "string",
"name": "string",
"email": "string",
"created_at": "2025-11-17T14:08:19.090Z",
"last_authenticated_at": "2025-11-17T14:08:19.090Z",
"has_registered_device": true,
"usernames": [0]
}
API Endpoint:
GET https://kolideapi.readme.io/reference/get_devices
{
"id": "string",
"name": "string",
"registered_at": "2025-11-17T14:09:50.253Z",
"last_authenticated_at": "2025-11-17T14:09:50.253Z",
"registered_owner_info":
{
"identifier": "string",
"location": "string"
},
"operating_system": "string",
"hardware_model": "string",
"serial": "string",
"hardware_uuid": "string",
"note": "string",
"auth_state": "Will Block",
"will_block_at": "2025-11-17T14:09:50.253Z",
"product_image_url": "string",
"auth_configuration": {
"device_id": "string",
"authentication_mode": "string",
"person_groups": [
{
"id": "string",
"name": "string"
}
]
},
"device_type": "Mac",
"form_factor": "Computer"
}
Next, create an import job in Assets:
Use OnLink’s mapping:
key:id=id
map:name=Full Name
map:email=Email
config:api=people
|
Mapping |
Meaning |
|
key:id=id |
Uses Kolide’s id as the unique key so OnLink updates existing objects instead of duplicating them |
|
map:name=Full Name |
Maps Kolide’s name to your Assets “Full Name” attribute |
|
map:email=Email |
Maps Kolide email → Assets email |
|
config:api=people |
Tells OnLink to pull People objects |
Any field from the Kolide People API can be mapped.
You can map any device-level fields, such as:
Your configuration might look like:
key:id=id
map:name=Device Name
map:operating_system=OS
map:hardware_model=Model
map:serial=Serial Number
map:hardware_uuid=Hardware UUID
config:api=devices
Yes. OnLink can pull any object exposed through the Kolide API and map it to Assets object types.
No. OnLink handles API calls, pagination, scheduling, and field mapping without custom scripting.
Yes. Kolide provides user identifiers that can be used to link People objects to Device objects inside Assets.
You can run manual jobs or configure automated schedules at your preferred frequency.
OnLink updates the existing Assets object as long as the key field (usually id) stays consistent.
If you’re already using Kolide, give OnLink a try and see how much easier your workflow becomes. With support for 50+ data sources, OnLink lets you pull everything into Assets without hopping between apps or writing custom scripts.
Prabhu Palanisamy _Onward_
President
Onward
Ashburn, VA
3 accepted answers
0 comments