> 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/discover-new-targets/scan-cloudflare-connection-asset-discovery.md).

# Scan a Cloudflare connection for asset discovery

How to scan a Cloudflare connection for asset discovery 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 %}

## Scan a Cloudflare connection for asset discovery

Organizations often lack visibility into all their assets (web applications and APIs), which can lead to overlooked vulnerabilities and inadvertent security exposure. With Snyk API & Web asset discovery, you can identify your organization's assets and protect them before they become a liability.

Scanning a Cloudflare connection for asset discovery involves two steps:

1. Obtain the Cloudflare API Token.
2. Add the Cloudflare connection.

### Obtain the Cloudflare API Token

To add a Cloudflare connection, you need the Cloudflare API Token. To obtain it, follow these steps:

1. Navigate to your Cloudflare account, click **My Profile**, and then click **API Tokens** to access the **User API Tokens** tab.

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>Account API Tokens do not work in this scenario.</p></div>
2. Click **Create Token** and then click **Get Started** in the **Create Custom Token** configuration.
3. Under the **Permissions** section, select the **Zone** permission group, the item **Zone**, and the **Read** access permission. Then, add another **Zone** permission with the item **DNS** and the **Read** access permission as well.
4. Under the **Zone Resources** section, select the zones you want to include in the scan. Snyk recommends selecting **All zones** to include current and future zones from your Cloudflare account.
5. Click **Continue to summary** to review the details and then click **Create Token**.
6. After Cloudflare creates the token, it displays the token value. Copy the token and store it securely, because you cannot view it again. You need this token value in the next step.

### Add the Cloudflare connection

In Snyk API & Web, add a Cloudflare connection for asset discovery:

1. Select the **Discovery** page and click **Add source** to open the configuration.
2. Select **Connect with Cloudflare** and click **Next**.
3. Paste the Cloudflare API Token (obtained in the previous step) into the **Cloudflare API Token** field and click **Connect**.

After successfully connecting with Cloudflare, Snyk starts running regular discovery scans automatically on your Cloudflare account. In Snyk, check the **Discovery** page. After the asset discovery finishes, Snyk adds all newly found assets to the list. At the top of the page, Snyk displays information about the number of newly found assets. Click it to filter the list.

To update or remove the Snyk connection to Cloudflare, navigate to the **Integrations** page in Snyk.


---

# 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/discover-new-targets/scan-cloudflare-connection-asset-discovery.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.