---
title: "Configure or Replace Message Signature"
method: PUT
path: "/targets/{id}/signature/"
tags: ["Targets"]
---

# Configure or Replace Message Signature

`PUT /targets/{id}/signature/`

Creates a new signature configuration or completely replaces an existing one 
for the specified target. Enabling is implicit on successful creation/replacement.

## Path parameters

- `id` string, required

## Request body

- SignatureConfigRequestSerializerBase — Base serializer for signature configuration requests.
  - `signature_method` string, required — The signature method to configure. Must be one of: xpay, http-v1, jwt-v1.

## Response `200`

- SignatureConfigResponseBase — Base serializer for signature configuration response.
  - `configured` boolean, required — Indicates if message signature is configured for the target.
  - `enabled` boolean, required — Indicates if message signature is currently enabled for the target.
  - `signature_method` string, nullable, required — The signature method configured for the target. Returns null if signature is not configured.

## Other responses

- `400`
- `401`
- `403`
- `404`
- `500`

---

[API](https://skmtc.net/probely/apis/snyk-api-web-s-api-reference-documentation.md) · [All operations](https://skmtc.net/probely/apis/snyk-api-web-s-api-reference-documentation/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/probely/snyk-api-web-s-api-reference-documentation/versions/e29879bff01b/schema)