> 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/configure-targets/test-target-configuration.md).

# Test target configuration

How to test a target configuration 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 %}

## Test target configuration

Test your target configuration before running a scan to avoid common issues that lead to failed scans or incomplete results.

Test the configuration to:

* Confirm Snyk API & Web can access your target.
* Verify login credentials work as expected.
* Identify whether a web application firewall (WAF) or other security measures block traffic.
* Verify the validity of your API schema or collection.
* Discover extra hosts that you need to add to your target.

### Prerequisites

To test target configuration, you must have these permissions:

* `view_target`
* `change_target_settings`
* `start_scan`

### Test configuration from the Targets list

1. Navigate to **Targets** and locate the target to test.
2. Open the **Scan** button dropdown.
3. Select **Test configuration**.

### Test configuration from Target settings

1. Navigate to the target settings page.
2. Click **Test configuration** in the **Login Configuration** or **API Target Authentication** module, or at the top of the page.

### Review test results

After starting the test, a side panel opens to display test progress in real time.

Snyk API & Web provides feedback on these areas:

* **Connectivity**: Confirms Snyk API & Web can reach the URL
* **WAF Detection**: Alerts you if a firewall can interfere with the DAST scan
* **Authentication**: Validates that credentials successfully grant access to the target
* **Schema Validity**: Verifies the schema provided for API targets
* **Extra Hosts**: Identifies additional domains the web application relies on that you need to add to the target settings

If a check fails or requires further configuration, the side panel provides a call to action to help resolve the issue. You can also review connectivity details and, if applicable, a video of the login attempt.

Examples:

<figure><img src="https://2730497224-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBJO0IZx7zB6bOkotxQP2%2Fuploads%2Fgit-blob-d28bff2069d4da29f3bb9c38c945251ef89c7d87%2Ftest-target-configuration-results.png?alt=media" alt="Test configuration results showing connectivity check, WAF detection, authentication validation, and extra hosts discovery"><figcaption></figcaption></figure>

|

<figure><img src="https://2730497224-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBJO0IZx7zB6bOkotxQP2%2Fuploads%2Fgit-blob-677628f7a4c58a9efd0a16f76940f61a8a752bce%2Ftest-target-configuration-error-example.png?alt=media" alt="Test configuration error example with call to action to resolve the issue"><figcaption></figcaption></figure>

\---|---


---

# 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/configure-targets/test-target-configuration.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.
