← all problem types

invalid_url

422 Unprocessable Content   The url is not usable for this check.

When you get it

The url is not usable for this check. 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:

pointer

RFC 6901 JSON Pointer to the offending value in the request body.

value

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

reason

The machine-readable sub-case, when one code covers several. Branch on it.

allowed

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

detail

Human-readable detail for this one occurrence. Never the only place remediation appears.

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-url",
  "title":  "The url is not usable for this check.",
  "status": 422,
  "code":   "invalid_url",
  "errors": [
    { "pointer": …, "value": …, "reason": …, "allowed": …, "detail": … }
  ]
}