Errors
Errors are RFC 9457 problem documents, sent with content-type: application/problem+json:
{ "type": "https://holemonitor.live/docs/errors#validation", "title": "Validation failed", "status": 422,
"detail": "url: must use https", "errors": [{ "field": "url", "message": "must use https" }] }
bad-request
- The body is not valid JSON, or a header is malformed.
unauthorized
- No credentials, or the API key is invalid or revoked.
forbidden
- The key lacks
writescope, the route needs a dashboard session, the account is suspended, or a plan limit was reached. A plan-limit problem hastitle"Plan limit reached" and alimitfield naming the limit:terms,endpoints,broad_filters,api_keys.
not-found
- The object does not exist or belongs to another account.
conflict
- An
Idempotency-Keywas reused for a different request, or the object's state does not allow the change.
gone
- The object existed and was removed.
too-large
- The request body is too large.
validation
- The body failed validation.
errorslists each field and message.
rate-limited
- Too many requests. Wait for
retry-afterseconds.
internal
- An unexpected error. Retrying with the same
Idempotency-Keyis safe.
unavailable
- A dependency is unavailable. Retry later.