Skip to content
Get Started Free

Public setup wizard

ErrorNotifier setup instructions for humans and AI agents

This page is intentionally public so an AI coding agent can open the URL, read the steps, and install monitoring on a site without needing your ErrorNotifier login. Logged-in users see a real browser project key; visitors see an obvious placeholder.

ErrorNotifier human and agent setup wizard
Browser SDK keyPlaceholder
Replace enpk_your_public_project_key with the public key from App > Projects.
Server secretNever Public
Server-side releases, deploys, artifacts, and automated tests need a secret key created inside App > Projects.
REST endpointReady
Use the WordPress REST namespace at https://errornotifier.com/wp-json/errornotifier/v1.
Domain proofAutomatic Or DNS
The browser SDK can verify a domain automatically. Sites without the SDK can use DNS TXT or CNAME proof.

Agent task brief

  1. Identify the site technology and the public production URL.
  2. Add the browser SDK snippet before the closing body tag or through the site asset pipeline.
  3. Set the project key to enpk_your_public_project_key.
  4. Set the endpoint, feedback endpoint, and verification endpoint exactly as shown.
  5. Deploy to a page on the real domain so ErrorNotifier can see SDK verification traffic.
  6. Create or confirm a monitor in ErrorNotifier for the root URL or health URL.
  7. For CI, create a server secret in App > Projects and post automated test runs to the test-runs endpoint.

Browser SDK snippet

<script src="https://errornotifier.com/wp-content/plugins/errornotifier-core/assets/js/errornotifier-sdk.js"></script>
<script>
ErrorNotifier.init({
  projectKey: "enpk_your_public_project_key",
  endpoint: "https://errornotifier.com/wp-json/errornotifier/v1/store",
  feedbackEndpoint: "https://errornotifier.com/wp-json/errornotifier/v1/feedback",
  verificationEndpoint: "https://errornotifier.com/wp-json/errornotifier/v1/sdk-verify",
  environment: "production",
  release: "1.0.0",
  reportBug: true
});
</script>

.NET and CI example

Project key for browser pages: enpk_your_public_project_key
Server secret placeholder: ensk_your_server_secret_from_app_projects

curl -X POST "https://errornotifier.com/wp-json/errornotifier/v1/test-runs" \
  -H "Authorization: Bearer ensk_your_server_secret_from_app_projects" \
  -H "Content-Type: application/json" \
  -d "{\"run_uid\":\"dotnet-ci-1\",\"provider\":\"dotnet\",\"suite_name\":\"unit\",\"status\":\"passed\",\"total_tests\":42,\"passed_tests\":42,\"failed_tests\":0}"

Manual monitor checklist

  1. Open App > Monitors and add the production HTTPS URL.
  2. Choose the expected HTTP status and optional keyword check.
  3. Open App > Domains to confirm SDK or DNS proof.
  4. Open App > Alerts and add email, Slack, or webhook destinations.
  5. Run a manual check from the Monitors table.