Skip to content
Error codes · realuptime errors ingest

RU-4007: Invalid errors API request

A parameter on a realuptime errors API request failed validation: for example an ID that is not a UUID, an out-of-range query parameter, or a request body the endpoint cannot accept. The `error` field names the failing parameter.

Where it is raised

  • POST /api/v1/errors/projects
  • GET /api/v1/errors/projects/{id}
  • GET /api/v1/errors/projects/{id}/issues
  • GET /api/v1/errors/issues/{id}
  • PATCH /api/v1/errors/issues/{id}
  • POST /api/v1/errors/releases
  • Keyed MCP endpoint, Errors tools

What triggers it

Path ids are checked as UUIDs before any lookup, project names must be 1 to 120 characters, and the release route names invalid fields by their schema name. A previousRelease equal to the release being registered is refused here too.

Example response

GET /api/v1/errors/issues/{id}
HTTP 400

{
  "error": "issueId must be a valid UUID.",
  "code": "RU-4007"
}

Common causes

  • An ID that is not a valid UUID.
  • A query parameter outside its allowed range.
  • A request body that is not JSON, names a field the endpoint does not read, or sends a `status` other than open, resolved or ignored.

How to fix it

  1. Fix the parameter named in the `error` field, then resend.
  2. Copy IDs from API list responses rather than constructing them.
  3. Send exactly the fields the endpoint documents. To reopen an issue, send `status: "open"`.

Related codes