`invalid_range`

422 Unprocessable Content The requested time range is not valid.

When you get it

The requested time range is not valid. 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:

parameter: The query parameter the failure is about - the query-side twin of `pointer`.
from: The start of the requested time range, Unix seconds.
to: The end of the requested time range, Unix seconds.
maxSpan: The widest time range this endpoint serves, in seconds.
suggestedBucket: A bucket granularity that would make the requested range fit.
reason: The machine-readable sub-case, when one code covers several. Branch on it.
value: The value the request sent, echoed back so the caller can see what was read.
min: The smallest value this field accepts, inclusive.
max: The largest value this field accepts, inclusive.
buckets: How many time buckets the requested window and bucket size produce over the requested range.
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-range",
  "title":  "The requested time range is not valid.",
  "status": 422,
  "code":   "invalid_range",
  "errors": [
    { "parameter": …, "from": …, "to": …, "maxSpan": …, "suggestedBucket": …, "reason": …, "value": …, "min": …, "max": …, "buckets": …, "detail": … }
  ]
}