What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions!

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
300.000 administrators have chosen PRTG to monitor their network. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags


View all Tags

REST custom - 400 bad response error

Votes:

0

Your Vote:

Up

Down

Hi,

I'm building an API monitoring sensor for the first time and getting the error "Cannot load endpoint

https://**REDACTED**/MGRESTService.svc/json/idoinfo/BGTaskHistories?readonly=true&rowcap=1: expected status 200 OK but got 400 Bad Request."

I'm using postman to manually query the same API, so am confident the URL is correct. The sensor doesn't automatically get a token, so I'm manually pasting this into settings at the moment. I've tried passing the token as a custom HTTP header also. If I take the URL (which I've deliberately redacted here) from the error and paste it back into postman it functions correctly. I see the colon appended to the URL, which I assume is PRTG formatting the error - or is this relevant?

The sensor is configured with the 'channeldiscovery' REST template.

Any help appreciated. Thanks.

api json rest

Created on Mar 13, 2021 6:51:29 PM by  chrisbailey (0) 1

Last change on Mar 15, 2021 7:23:45 AM by  Felix Wiesneth [Paessler Support]



Replies

Nobody has replied yet

Why not be the first?

Please log in or register to enter your reply.


Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.