Chat now with support
Chat with Support

Quest has tools and processes in place to identify, protect, detect, and remediate vulnerabilities and incidents when they occur, including external security partners. As part of our standard security operations, Quest does not use CrowdStrike in any of our operations. We are reviewing our third parties, and so far, there is minimal affect. It is Quest's policy not to provide further technical details unless they directly impact customer data.

KACE Systems Management Appliance 14.0 Common Documents - API Reference Guide

Update a location example

Update a location example

Syntax:

•
Type: PUT
•
URL: {host}/api/asset/assets/{id}
•
Headers:
◦
Content-Type:application/json
◦
Accept:application/json
◦
x-kace-api-version:5
•
Body:

{

"Assets" : [ {

“name” : “{Location name}"

} ]

}

* 
NOTE: The location fields "description", "webSite", "address", "phoneNumber" are not available on the API. However, any other asset custom fields defined for the Location asset type are editable.

Fetch locations example

Fetch locations example

Syntax:

•
Type: GET
•
{host}/api/asset/assets?filtering=asset_type_id eq 1
•
Headers:
◦
Content-Type:application/json
◦
Accept:application/json
◦
x-kace-api-version:5

Create an inventory example

Create an inventory example

Syntax:

•
Type: POST
•
URL: {host}/api/inventory/machines
•
Headers:
◦
Content-Type:application/json
◦
Accept:application/json
◦
x-kace-api-version:5
•
Body:

{

"Machines": [

{

"Name":"{system name}",

"Ip":"{ip address}",

"Os_number":"{os number}",

"User":"{user}",

"Cdrom_devices":"{cd rom device}",

"Os_name":"{os name}",

"Ram Total":"{ram total}",

"Ram_used":"{ram used}",

"Pagefile_max_size":"{pagefile max size}",

"Ram_max":"{ram max}",

"Bios_identification_code":"{bios id code}",

"Monitor":"{monitor}",

"Sound_devices":"{sound device}",

"Video_controllers":"{video controller}",

"Pagefile_size":"{pagefile size}"

}

]

}

Example:

* 
NOTE: This example creates a machine in the inventory given the field values below.
•
Type: POST
•
URL: k1000/api/inventory/machines
•
Headers:
◦
Content-Type:application/json
◦
Accept:application/json
◦
x-kace-api-version:5
•
Body:

{

"Machines": [

{

"Name":" Workstation 123",

"Ip":"192.168.101.110",

"Os_number":"10.0.14393",

"User":"user1",

"Cdrom_devices":"NECVMWar VMware SATA CD01",

"Os_name":"Microsoft Windows 10 Pro x64",

"Ram Total":"2048 Bytes",

"Ram_used":"1324.1",

"Pagefile_max_size":"385",

"Ram_max":"33792",

"Bios_identification_code":"",

"Monitor":"Generic Non-PnP Monitor",

"Sound_devices":"High Definition Audio Device",

"Video_controllers":"VMware SVGA 3D:1024 MB",

"Pagefile_size":"385"

}

]

}

Query examples

Query examples

For reference, here is an example of a query that uses most of the parameters described in this section.

/machines?shaping=machine all,software
limited&sorting=software.name
desc&use_count=false&filtering=id lt 1000&paging=limit
1

To retrieve tickets, along with their submitter and owner details (if available):

GET /api/service_desk/tickets?shaping=
hd_ticket regular,owner limited,submitter limited

To retrieve ticket changes and comments, including attachment IDs, and author comments:

GET /api/service_desk/tickets/24/changes?shaping=
hd_ticket_change regular,attachments regular,user limited

To retrieve an attachment associated with a ticket change:

GET /api/service_desk/tickets/24/changes/26/
attachments/18
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating