1. Create a webhook under Errors > Settings, on the project
Each errors project gets its own webhook, next to its ingest key. The URL (which contains the token) is shown once; rotate or revoke it from the same row if it leaks.
2. Add it in Vercel's project Settings > Webhooks
Paste the URL, select the Deployment Succeeded event, and save. An Integration Console webhook works the same way if you're shipping a Vercel integration rather than configuring one project by hand.
3. That's it: no template, no CI step
Vercel's own documented event body is read as-is. The release registered is the deployment's URL; the commit sha and repository link are filled in automatically when Vercel's deployment carries GitHub, GitLab or Bitbucket metadata, and left blank for a deploy with no linked repo -- realuptime never guesses one.
4. It is the same write POST /errors/releases makes
Idempotent on (project, release): a webhook Vercel redelivers re-registers the same row rather than creating a duplicate. If you already call POST /errors/releases from CI for other metadata (a build number, a staging environment), both can point at the same project without conflicting.
Go deeper
The full reference lives in the docs: Inbound release webhook reference. Error codes named above are each explained in the error-code reference.