Every modern browser has a built-in error reporting system: the W3C Reporting API. CSP violations, deprecation warnings, and browser interventions are already being detected. Without a destination, those reports are lost. Reporting API App gives them one.
What you get
01 · INGEST
Add two HTTP response headers and modern browsers start sending reports automatically. No JavaScript bundle, no extra weight.
Response headers
Reporting-Endpoints
Report-To
Content-Security-Policy
NEL
02 · COVERAGE
CSP, integrity, network errors, crashes, deprecations, interventions — every standard W3C report routed for you.
03 · HOSTING
Servers and report data run on Hetzner in Falkenstein, Germany. Operated by BauCloud GmbH from Munich. No US cloud dependency.
04 · ROUTING
Forward reports to AppSignal, any webhook endpoint, or Google Chat. The integrations your team already trusts.
Quickstart
Add two response headers and browsers start sending reports automatically. No SDK, no client-side code.
Tell browsers where to send reports with the
Reporting-Endpoints
response header.
Reporting-Endpoints: default="https://reporting-api.app/browser-reports/YOUR-ENDPOINT-UUID"
Add a report-to
directive to your
CSP
(or any other browser policy header) and you're done.
Content-Security-Policy: default-src 'self'; report-to default
Browsers detect the violation, send a structured report, and Reporting API App routes it to AppSignal, Google Chat, or any webhook you configure. Setup takes less than five minutes.
Hosted in the EU. Designed for GDPR. No tracking, no cookies, no third-party scripts.
Start capturing browser reports today. Setup takes less than 5 minutes.