/build/static/layout/Breadcrumb_cap_w.png

Systems Management Question


API Support

03/10/2017 896 views
Is Kace going to support an API functionality anytime soon?  We need it for our Service Desk to feed how many tickets are being worked on and other situations like that.
Answer Summary:
1 Comment   [ + ] Show comment

Comments

  • This doesn't directly answer your question but one thing I've done to get around this is query the database. If you're tickets are only in an open status while they're actively being worked on then this works. This means that all your techs change status to open while they're working and then set it to stalled (ex: waiting on user) when they are not working on it. Then whatever program you create could re-query every minute or so and always have an up-to-date view of the number of active tickets.

    I've done the same thing to get patch statistics and device info as well.

Answer Chosen by the Author

0
Well, the appliance supports a fully featured API, but what you want is a different thing and it is built in since years:
1. reporting (built in, build your own reports and run them or send them regulary to anyone you like)
2. database access: https://support.quest.com/kb/114992
3. custom ticket rules (do whatever you want with your tickets, there are people who run their SD with this feature completely different than it is meant)
Answered 03/13/2017 by: Nico_K
Red Belt

  • the API documentation can be found here:
    http://support-public.cfm.quest.com/39143_K1000_7.0_API_Reference_en-US.pdf

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ