← all problem types

invalid_alert_delay

422 Unprocessable Content   The requested alert delay is not one of the supported values.

When you get it

The requested alert delay is not one of the supported values. 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:

value

The value the request sent, echoed back so the caller can see what was read.

allowed

The complete set of values this field accepts. Send one of these.

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/invalid-alert-delay",
  "title":  "The requested alert delay is not one of the supported values.",
  "status": 422,
  "code":   "invalid_alert_delay",
  "errors": [
    { "value": …, "allowed": … }
  ]
}