Hi,

I am doing couple of tests to integrate PRTG with Kaseya REST API. I could get HTTP REST API sensor working but having a problem with generating access token from Kaseya automatically while querying.

Below is steps to reproduce issue:

  1. . Create a HTTP REST API Sensor to request an Access Token from Kaseya server
  2. . Create another HTTP REST API Sensor to actually query including the Access Token (obtained from step 1) in Header field
  3. . With Access Token having validity of 25 minutes, next time the sensor queries with last Access Token value, it gets rejected.

I need to have arrangement where we can automatically get same REST API Sensor to request Access Token and query REST API seamlessly without having to generate access token manually now and again.

Your help will be highly appreciated.

Thanks and regards, Shishir

Article Comments

Hi there,

I'm afraid this won't be possible out of the box. You would need to build your own script that performs the necessary tasks and in the end returns a result like "value:message", which then could be used with an EXE/Script sensor to read that result and display it in a channel.

Kind regards,

Erhard


Nov, 2016 - Permalink

Hi Erhard,

Thanks for your quick reply. I will try EXE/Script sensor for this.

Cheers, Shishir


Nov, 2016 - Permalink

Can you provide a simple example of this script? Making web requests is a very common thing to do. Even if they have tokens. Is there any work being done to accommodate a simpler solution in the future?


Jul, 2020 - Permalink