Chat now with support
Chat with Support

KACE Systems Management Appliance 14.0 Common Documents - API Reference Guide

KACE SMA Service Desk API Examples

KACE SMA Service Desk API Examples

This section provides examples for adding attachments to Service Desk tickets using the KACE SMA API.

Upload an attachment as a ticket change:

Start by executing a multipart/form-data request on the ticket. In the Tickets section the array of one ticket object with the ticket updates includes the change group that has the requirements for the ticket change. The attachmentSet field inside the change group declares what parts to pull in as attachments for the ticket. The brackets in the name of the attachment part ("INVENTORY_FILE[]") allow you us to have multiple parts with the same name, so you can embed up to five attachments in one ticket change.

Determine what attachments are available with a ticket:

Retrieve an attachment:

To retrieve an attachment, you must provide the ticket ID, change ID, and attachment ID. These values can be obtained using the above example, Determine what attachments are available with a ticket:.

User Notification Reference

User Notification Reference

KACE SMA User Notification API Reference

Overview

Version information

Version : 14.0

URI scheme

BasePath : /api/user_notifications

Consumes

Produces

Paths

POST /api/user_notifications/notification_controller/delete

Description

Delete a set of user notifications

Parameters

Type
Name
Schema

Body

notificationData required

notificationData

notificationData

Name
Schema

NotificationIDs optional

< integer > array

Responses

HTTP Code
Schema

200

string

POST /api/user_notifications/notification_controller/mark_as_read

Description

Mark a set of user notifications as read

Parameters

Type
Name
Schema

Body

notificationData required

notificationData

notificationData

Name
Schema

NotificationIDs optional

< integer > array

Responses

HTTP Code
Schema

200

string

GET /api/user_notifications/notifications

Description

Retrieves user notifications for the logged in user

Responses

HTTP Code
Schema

200

Response 200

Response 200

Name
Schema

UserNotifications optional

< user_notification > array

Definitions

user_notification

Name
Schema

body optional

string

new optional

integer

notification_id optional

string

notification_type optional

string

time_started optional

integer

timestamp optional

integer

title optional

string

About us

About us

Quest creates software solutions that make the benefits of new technology real in an increasingly complex IT landscape. From database and systems management, to Active Directory and Office 365 management, and cyber security resilience, Quest helps customers solve their next IT challenge now. Around the globe, more than 130,000 companies and 95% of the Fortune 500 count on Quest to deliver proactive management and monitoring for the next enterprise initiative, find the next solution for complex Microsoft challenges and stay ahead of the next threat. Quest Software. Where next meets now. For more information, visit www.quest.com.

Technical support resources

Technical support resources

Technical support is available to Quest customers with a valid maintenance contract and customers who have trial versions. You can access the Quest Support Portal at https://support.quest.com.

The Support Portal provides self-help tools you can use to solve problems quickly and independently, 24 hours a day, 365 days a year. The Support Portal enables you to:

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating