Skip to content
Error codes · Status pages & incidents

RU-5008: Invalid status page request

The request body for creating or updating a status page or one of its components was refused: not JSON, failing field validation, a reserved or malformed slug, a non-https link, an unknown theme/font/locale, or a check that cannot be published (an agent-bound monitor). The `error` field says which.

On the wire

Ships with HTTP status 400, carrying "code": "RU-5008" in the response body alongside the human-readable error message. Existing fields are never replaced by the code: it is additive.

Common causes

  • A slug with uppercase letters, spaces, or a leading/trailing hyphen, or one of the reserved words.
  • A logo, homepage or support URL that is not https, or resolves to a private address.
  • Publishing an agent-bound monitor as a component: those are private by design.

How to fix it

  1. Read the `error` field for the failing field.
  2. Compare your payload against the API docs at /docs/api, "Status pages".

Related codes

  • RU-5009: Status page or component not found
  • RU-5010: Status page slug already taken

Still stuck?

Ask support and mention RU-5008: the code pins down the exact refusal path, so you skip the diagnostic back-and-forth.