API reference

1. Browser and public SDK calls use X-ErrorNotifier-Key with the project public key.
2. Server-side release, deploy, artifact, and automated-test calls use Authorization: Bearer <secret key>.
3. REST namespace: /wp-json/errornotifier/v1.
4. Create reusable domain proof with POST /domain-verifications, GET /domain-verifications/{id}, and POST /domain-verifications/{id}/check.
5. Verify a running browser SDK with POST /sdk-verify. The response includes per-domain feature flags and basic SDK statistics.
6. Create events with POST /store or /envelope.
7. Create visitor bug reports with POST /feedback when bug reports are enabled for the domain.
8. Create releases with POST /releases and deploys with POST /deploys.
9. Create automated unit-test and CI results with POST /test-runs using a server secret key.
10. Successful write responses return JSON with accepted identifiers such as event_id, issue_id, or test_run_id depending on endpoint.
11. Error responses are JSON with a WordPress REST error code, message, and HTTP status such as 400, 401, 403, 404, or 429.
12. Rate limits are enforced for sensitive public surfaces and project-key ingestion; back off and retry later on HTTP 429.

curl -H "X-ErrorNotifier-Key: enpk_xxx" -H "Content-Type: application/json" -d '{"message":"test","platform":"javascript"}' https://errornotifier.com/wp-json/errornotifier/v1/store

Example response:
{"accepted":true,"event_id":"evt_123","issue_id":42}

Example error:
{"code":"rest_forbidden","message":"Invalid or missing project key.","data":{"status":401}}