Skip to content
Error codes · Monitors, checks & agents

RU-3001: Invalid monitor request

A monitor request was refused before anything changed: the body was not JSON, failed field validation, or a query value on a monitor route was malformed. The `error` field carries the first problem's own message.

Where it is raised

  • Checks: 8 routes
  • Incidents: 1 route
  • Errors: 1 route
  • Agents: 3 routes
  • The agent maintenance window routes on the ingest service (the same code, with the first failing hosts or field named)

What triggers it

The first validation step on every monitor route: the body is read as JSON and checked against the route's schema, and the first issue becomes the message. Query problems use it too: limit outside 1 to 500 and a before that is not an ISO 8601 timestamp on the runs route, and a format that is not csv or json on the exports.

Example response

POST /api/v1/checks
HTTP 400

{
  "error": "Request body must be valid JSON.",
  "code": "RU-3001"
}

Common causes

  • A missing required field (name, url, intervalSeconds, regions).
  • A value outside its allowed range, or the wrong type.
  • A request body that isn't valid JSON.

How to fix it

  1. Read the `error` field: it names the failing field and the rule it broke.
  2. Compare your payload against the API docs at /docs/api.
  3. Send the corrected request; nothing was created or changed by the refused one.

Related codes