Reporting APIGet started
Get started with the browser Reporting API
The shortest path to a working reporting endpoint, declare an endpoint, point a policy at it, and confirm a first report lands.
Last update:
This section takes you from nothing to a working reporting endpoint: declare an
endpoint with the Reporting-Endpoints header, route a policy to it, and confirm a
report lands. Start in Report-Only so nothing breaks while you learn.
Prerequisites
You need three things before you start:
- An HTTPS site. The browser only delivers reports to a secure (HTTPS) endpoint and silently ignores a non-secure one.
- The ability to set response headers. Reporting is configured entirely through headers, so you need access to your server, framework, or CDN config.
- An endpoint URL to receive the reports. This is any URL that accepts an HTTP
POST. CentralCSP gives you a ready one, or you can use your own.
In this section
Quickstart
The three steps to your first report.
Choose an endpoint
Where reports go, and build vs buy.
Next steps
- Follow the end-to-end walkthrough in how to set up the Reporting API.
- Understand the delivery format in how the Reporting API works.
- Wire each policy: Content Security Policy, COOP, NEL.