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 BETA Postdata no Content-Type: text/xml possible



Your Vote:



Hi there,

and once again stress with the custom sensor. In the postdata there is no <> allowed?

my postdata will be malformed to {} style. But my endpoint will not accept that because it has to be text/xml.

"Using HTTP POST When sending configurations and commands to the codec, it is important that the HTTP header Content-Type is set to text/xml, i.e. Content-Type: text/xml. The body of the POSTshould contain the XML content."

Custom HTTP Headers = Content-Type: text/xml

Any ideas?


http-xml-rest-value-sensor postdata rest-api-sensor

Created on Mar 14, 2019 3:00:21 PM by  sbendzus (0) 1

1 Reply



Your Vote:



Yeah we don't allow < and >, as it would mess around with our XML configuration, unfortunately. You'd need to use a PowerShell script instead to make these kinds of queries :( But the result evaluation needs to be done within that one as well. Sorry to be the bearer of bad news here.

PRTGapi | Feature Requests | WMI Issues | SNMP Issues

Kind regards,
Stephan Linke, Tech Support Team

Created on Mar 15, 2019 11:52:46 AM by  Stephan Linke [Paessler Support]

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.