unsupported_monitor_type
422 Unprocessable Content This operation is not available for this monitor type.
When you get it
This operation is not available for this monitor type. It is always answered with HTTP 422 - one code means one status, so a client may key its handling on either.
Fields it carries
Inside each errors[] entry, beside pointer:
type- The monitor or contact type the rule applies to.
supported- The values this endpoint supports.
A field is omitted when the server genuinely does not know it - an absent member is never the same as an empty one.
How to fix it
The request was well-formed but a value is not acceptable. The fields above name the offending value and what would be accepted - fix the request and retry.
Shape
{
"type": "https://api2.host-tracker.com/problems/unsupported-monitor-type",
"title": "This operation is not available for this monitor type.",
"status": 422,
"code": "unsupported_monitor_type",
"errors": [
{ "type": …, "supported": … }
]
}