Skip to content
Error codes · Status pages & incidents

RU-5004: Inbound incident webhook token not recognized

The token in the POST /api/v1/incidents/inbound/<token> URL does not match a live inbound webhook on any account, or has been revoked or rotated. An unknown and a revoked token are refused the same way, so this response does not confirm whether a guessed token ever existed.

On the wire

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

Common causes

  • The token was rotated or revoked under Account settings > Integrations and the alerting tool still has the old URL.
  • The URL was copied incompletely.

How to fix it

  1. Open Account settings > Integrations > Inbound incident webhooks and compare the token prefix shown there with the URL your tool calls.
  2. If it was rotated, paste the new URL into the alerting tool; the old one stops working the moment a new one is minted.

Related codes

  • RU-5005: Inbound incident payload not understood
  • RU-5006: Inbound incident signature missing or wrong

Still stuck?

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