> 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/configure-api-targets/configure-signed-requests.md).

# Configure signed requests

Configure signed requests to ensure data integrity and authenticity for your API targets in Snyk API & Web.

Signed requests are a security practice used in APIs to ensure the integrity and authenticity of data transmitted between a client and a server. They contain digital fingerprints, often using algorithms like HMAC-SHA256, JSON Web Tokens (JWTs), or custom algorithms, to confirm the sender and prevent attacks by validating specific header fields or the entire request body. This practice is crucial for securing sensitive financial or data operations.

## Prerequisites

To configure signed requests, you must have:

* `change_target_settings` permission

Additional requirements:

* Signed requests feature enabled for your organization (Contact Snyk Sales)

## Configure signed requests

If your target requires requests to be signed, configure the signature in the target Signature settings.

1. In Snyk, navigate to the **Targets** page.
2. Identify the target you want to configure and click the **gear** icon to access the target settings.
3. Click the **Signature** tab and identify the **SIGNATURE** module.
4. Select the **Signature** you want to use and complete the form accordingly.
5. Click **Save**.

<figure><img src="/files/xfidwfYTpRMPfFvGQpnS" alt="Signature settings page showing signature type dropdown and configuration fields"><figcaption></figcaption></figure>

## Verify signed requests

After you save the configuration, signed requests are enabled. The next time you run a scan against this target, Snyk automatically uses the configured signature.

{% hint style="info" %}
For your security, all sensitive fields (such as certificates and shared secrets) are obfuscated after they are saved and cannot be viewed or retrieved again.
{% endhint %}

## Manage signed requests

You can manage these settings at any time from your target **Signature** tab:

* To temporarily disable a setting, use the **Off/On** toggle.
* To permanently remove a configuration, use the **Delete** button.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.snyk.io/scan-fix-and-prevent/scan-with-snyk/snyk-api-web/configure-targets/configure-api-targets/configure-signed-requests.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.