Skip to content
Public demo modeRead-only mock data for demo.errornotifier.com, shop.demo.errornotifier.com, api.demo.errornotifier.com, docs.demo.errornotifier.com, and hooks.demo.errornotifier.com. Placeholder secrets such as ensk_demo_placeholder_do_not_use are fake and cannot write data.
Create a real workspace

Simulated incident story

This demo data is read-only and follows one deploy from failing tests to recovery.

Simulated
  1. Bad deployStorefront release 2026.05-demo shipped with a checkout regression.
  2. Failed CI/test runGitHub Actions posted a failed unit test run with two checkout failures.
  3. Latency spikeAPI checks degraded while checkout health checks started returning errors.
  4. Confirmed incidentErrorNotifier opened a critical incident after repeated external failures.
  5. Alert routedEmail, Slack, and a signed automation webhook received delivery records.
  6. ResolutionThe deploy was rolled back, recovery was confirmed, and the report budget was updated.

Releases and deploys

Foundation is implemented with database tables, REST routes, and docs. This page now shows the feed contract, current records, and the next setup action.

API docs

Copyable per-project release endpoints

Use a server secret from App > Projects for the project you are deploying. Do not put server secrets in browser code.

Project: Browser storefront
Secret placeholder: ensk_demo_placeholder_do_not_use

Release endpoint: POST https://errornotifier.com/wp-json/errornotifier/v1/releases
Deploy endpoint: POST https://errornotifier.com/wp-json/errornotifier/v1/deploys
Authorization: Bearer ensk_demo_placeholder_do_not_use
Project scope comes from the server secret; keep version, environment, and dist stable across releases, deploys, errors, and tests.
1. Create releaseServer Secret
Record version, environment, dist, commit, repository, and commit range metadata.
2. Record deployServer Secret
Record when that release reached an environment and who or what deployed it.
3. Correlate evidenceAutomatic
Error events, test runs, and incident reviews can reference the same release string.
4. Deploy visibilityThis Screen
Use deploy counts and latest deploy timestamps to spot missing deploy records.

Release feed example

curl -X POST https://errornotifier.com/wp-json/errornotifier/v1/releases \
  -H "Authorization: Bearer ensk_demo_placeholder_do_not_use" \
  -H "Content-Type: application/json" \
  -d '{"version":"web-2026.06.07.1","environment":"production","commit_sha":"abc123","dist":"build-417"}'

curl -X POST https://errornotifier.com/wp-json/errornotifier/v1/deploys \
  -H "Authorization: Bearer ensk_demo_placeholder_do_not_use" \
  -H "Content-Type: application/json" \
  -d '{"release_version":"web-2026.06.07.1","environment":"production","actor":"github-actions"}'
Visible releases2
With deploys2
Deploy gaps0
ProjectVersionEnvironmentDeploy visibilityCommitCreated
Browser storefront2026.05.18.4no distproduction72 deploys2026-07-27 18:02:17 by demo deployer9e2ad412026-07-28 00:02:17
Public APIapi-2026.05.18.2no distproduction73 deploys2026-07-27 18:02:17 by demo deployera18cb772026-07-28 00:02:17