Skip to content
Error codes · realuptime errors ingest

RU-4013: Inbound release webhook token not recognized

The token in the POST /api/v1/errors/releases/inbound/<token> URL (the Vercel deploy-hook connector) does not match a live inbound release 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-4013" 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 the errors project's settings and the deploy platform still has the old URL.
  • The URL was copied incompletely into Vercel's webhook configuration.

How to fix it

  1. Compare the token prefix shown in the project's settings with the URL configured in Vercel.
  2. If it was rotated, paste the new URL into Vercel's webhook settings; the old one stops working the moment a new one is minted.

Related codes

  • RU-4014: Inbound release payload not understood
  • RU-4015: Inbound release signature missing or wrong

Still stuck?

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