`package_interval_conflict`

403 Forbidden No check interval satisfies both this monitor type and the account's plan.

When you get it

No check interval satisfies both this monitor type and the account's plan. It is always answered with HTTP 403 - 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.
minInterval: The shortest check interval this monitor type supports, in seconds.
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 understood and refused. Retrying it unchanged will fail identically - change the token, the rights, or the plan named in the fields above.

Shape

{
  "type":   "https://api2.host-tracker.com/problems/package-interval-conflict",
  "title":  "No check interval satisfies both this monitor type and the account's plan.",
  "status": 403,
  "code":   "package_interval_conflict",
  "errors": [
    { "type": …, "minInterval": …, "allowed": … }
  ]
}