Skip to content
Error codes · Status pages & incidents

RU-5005: Inbound incident payload not understood

The body of an inbound incident webhook could not be read as any supported shape: not JSON, or missing the fields the generic shape requires (key and status), or an Alertmanager/Grafana body with no alerts. The `error` field says which.

On the wire

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

Common causes

  • A custom webhook template that does not emit `key` and `status`.
  • Sending form-encoded or plain-text bodies instead of JSON.
  • A `?source=` query value naming an adapter the body does not match.

How to fix it

  1. Read the `error` field for the missing field.
  2. Compare the body against the generic shape in the API docs under Inbound incident webhook.
  3. For Alertmanager and Grafana, use their built-in webhook receiver unchanged; no template is needed.

Related codes

  • RU-5004: Inbound incident webhook token not recognized
  • RU-5006: Inbound incident signature missing or wrong

Still stuck?

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