How do I export findings as JSON?

Steps

1. Choose Issues from the sidebar.
2. Set the view you want. Use the search box, the four filters and the triage chips to shape the list.
3. Press Export JSON at the top of the page, beside Export CSV.
4. Open the downloaded file in a code editor, or feed it to the tool that needs it.

Good to know

JSON keeps structure, so it suits other tools and scripts. For a spreadsheet, export to CSV instead.

Export from a script

The API Reference lists GET /api/export/issues, described as "Export issues as JSON or CSV with filters". Pass ?format=json to choose the format. Authenticate with a Bearer API token. The route checks the issue:export permission, so the token's owner must hold it. Our guide to authenticating API requests shows the header.

Field	What to enter
Path	/api/export/issues
Format	?format=json
Permission	issue:export

Open a sample export and check its fields before you build anything on them. Findings can include requests and responses, so store the file with care. Before you share the file with anyone outside your team, think about who needs it, what the findings reveal about your systems, and whether a PDF report would serve them better. A short, clear answer beats a data dump. The tutorial on exporting findings goes further. If the export fails, contact us.

Related questions

• How do I export findings to CSV?
• How do I export my list of targets?
• How do I authenticate requests to the Cyberlop API?
• How do I find the endpoint I need and the permission it requires?
• Why does my findings export include only some of my findings?

Full tutorial

How to export vulnerability findings to CSV or JSON

Step-by-step, with annotated screenshots.

Updated 8 October 2026 · Back to the help centre