---
title: "Endpoint to generate and explain signature details"
method: POST
path: "/api/v1/webhooks/get-signature-detail"
tags: ["Webhooks"]
---

# Endpoint to generate and explain signature details

`POST /api/v1/webhooks/get-signature-detail`

Required scope: `manage-webhooks:read`.<br/>*Note that this endpoint is only for debugging purposes, is not stable and should not be used in production.*<br/>Read more here: https://docs.partner-api.monta.com/reference/generating-the-signature-example.

## Query parameters

- `includeSecrets` boolean
- `webhookSecret` string

## Request body

- object[]

## Response `200`

Debug output to explain signature based on your payload.

- SignatureExplanation
  - `receivedPayloadString` string, required — The processed payload as string
  - `receivedPayloadBytes` string, required — The processed payload as bytes (hex)
  - `webhookSecret` string, required — The secret used to sign the payload
  - `webhookSecretBytes` string, required — The secret used to sign the payload as bytes (hex)
  - `signatureAlgorithm` string, required — The algorithm used for generating the signature
  - `signature` string, required — The resulting signature
  - `signatureWithPrefix` string, required — The resulting signature including prefix

## Other responses

- `400` — The request is invalid
- `401` — Consumer with provided credentials was not found
- `403` — Operator doesn't have access to resource
- `404` — Entity with the provided id was not found

---

[API](https://skmtc.net/monta/apis/monta-partner-api.md) · [All operations](https://skmtc.net/monta/apis/monta-partner-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/monta/monta-partner-api/revisions/517e18f11015/schema)