> 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-message-level-encryption.md).

# Configure message level encryption

Configure message level encryption to provide enhanced end-to-end security for API targets in Snyk API & Web.

Message level encryption provides enhanced end-to-end security for message payloads using JSON Web Encryption (JWE). This security measure is crucial for APIs handling sensitive data such as personally identifiable information (PII) or payment information. Message level encryption operates independently of transport security, making it more robust against insider threats.

## Prerequisites

To configure message level encryption, you must have:

* `change_target_settings` permission

Additional requirements:

* Message level encryption feature enabled for your organization (Contact Snyk Sales)

## Configure message level encryption

If your target requires requests to be encrypted, configure message level encryption in the Encryption tab.

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 **Encryption** tab and configure all fields:
   * Upload a certificate with the server public key
   * Upload a certificate with the client private key
   * Enter the Key ID (KID) to be placed in the JWE header
   * (Optional) Limit the set of URLs to encrypt
4. Click **Save**.

<figure><img src="/files/fm8kHSYScNE0ZwATSu22" alt="Encryption settings page showing certificate upload fields and configuration options"><figcaption></figcaption></figure>

## Verify encryption

After you save the configuration, encryption is enabled. The next time you run a scan against this target, Snyk automatically uses the configured encryption for all requests.

{% 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 encryption settings

You can manage these settings at any time from your target **Encryption** 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-message-level-encryption.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.