Q: Will it support HTTPS?
A: Yes, if the certificate of the URL is valid.
Q: Will it result in a HTTPS post with data like that in an email?
A: It will result in a POST with the following data:
array (
'id' => '<id>', // unique identifier of the check
'status' => '<status>', // status = 2 means OK, status = 7 means error
'message' => 'Not matched', // result message, in this case it is error message
'since' => '<date_time>', // since this time the monitor is in error
'errors' => '<errors>', // number of consequent errors
'rid' => '<rid>', // monitor ID
'uid' => '<uid>', // user ID
'name' => '<monitor_name>', // monitor name
'type' => 'https', // <monitor_type>
'host' => '<host>', // host name (depends on the monitor type)
'port' => '443',
'path' => '/<path>', // depends on monitor type
'cloudmonitor' => '',
)
Q: What does the post data look like? Is it a JSON format?
A: the header is:
Content-type: application/x-www-form-urlencoded; charset=UTF-8
Q: I assume there’s no authentication or login support. Or can be embedded in the URL?
A: No authentication support. If the authentication were included in the URL it would be visible in contacts, logs etc. which is not secure. There are even no action URL parameters supported (we plan to revise it in the future)