> For the complete documentation index, see [llms.txt](https://docs.snyk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snyk.io/scan-fix-and-prevent/scan-with-snyk/snyk-api-web/review-and-fix/overview-reports/generate-csv-coverage-report.md).

# Generate CSV coverage report

How to generate a CSV coverage report in Snyk API & Web

{% hint style="info" %}
**Snyk is rolling out a new navigation.** The steps on this page describe the classic interface. If your view looks different, visit [Navigate the Snyk Web UI](https://docs.snyk.io/navigate-the-snyk-web-ui#where-things-moved) to map these options to the new interface.
{% endhint %}

## Generate CSV coverage report

To verify that your target was scanned in full and that the scan covered all URLs, Snyk API & Web lets you download a CSV coverage or crawling report. This report shows a list of all the URLs that Snyk visited while the scan was running.

There are a few different ways to generate a CSV coverage report:

* From a target's Scan Activity.
* From the global Scan Activity.
* From a target's scan results.

This article describes each way in detail.

### From a target's Scan Activity

Follow this procedure to generate a crawling report from the Scan Activity of a target.

1. In the **Targets** section, click the target name to show its details.
2. Click the **Scan Activity** tab. A **Reports** button appears next to each scan.
3. Click the button and choose the **Crawling report** to generate the report.

### From the global Scan Activity

Follow this procedure to generate the crawling report from the global Scan Activity in your account.

1. Access the **Scans** section. The **Scan Activity** tab displays a **Reports** button next to each scan.
2. Click the button and choose the **Crawling report** to generate the report.

### From a target's scan results

Follow this procedure to generate the scan report from the details of a target's scan results.

1. Navigate to the **Targets** section and click the target name to show its details.
2. Click the **Scan Activity** tab.
3. In the scans listed in the **Scan Activity** tab, click the row of the scan to view the scan details.
4. Download the **Crawling report** either from the **Status** section or from the **Reports** button.

If you open the full view of the scan details, you see the same two options.

After you request the report, Snyk downloads the CSV file automatically. The file lists all the endpoints Snyk accessed during that target scan.

Visit [Coverage report](/scan-fix-and-prevent/scan-with-snyk/snyk-api-web/review-and-fix/overview-reports/coverage-report.md) to learn how to read and interpret the CSV coverage report.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.snyk.io/scan-fix-and-prevent/scan-with-snyk/snyk-api-web/review-and-fix/overview-reports/generate-csv-coverage-report.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.