Skip to main content

Webhook signature verifier (HMAC) API

Paste the raw body, your webhook secret and the signature you received. The page computes the HMAC in your browser, tells you whether it matches and, when it doesn't, which usual mistake would make it match.

  • Endpoint: POST https://postboost.co/app/api/tools/webhook-signature-verifier (operationId verifyWebhookSignature)
  • Web tool: postboost.co/tools/webhook-signature-verifier
  • Token: optional (limits)
  • MCP: tool verify-webhook-signature on https://postboost.co/mcp/tools

Request​

FieldTypeDefaultDescription
bodystringThe raw request body exactly as received (up to 64 KB). Use a test payload, not production data.
secretstringThe webhook secret. Use a test secret: never send a production secret to any third-party service.
signaturestringThe received signature header value, e.g. X-Signature.
algorithmstring: sha256, sha1, sha512"sha256"
encodingstring: hex, base64"hex"
prefixstring""A prefix the sender puts before the signature, e.g. "sha256=" (GitHub).

Call it​

curl -X POST https://postboost.co/app/api/tools/webhook-signature-verifier \
-H 'Content-Type: application/json' \
-d '{"body":"{\"event\":\"post.published\",\"data\":{\"uuid\":\"0b8f1c2e-6c1d-4f7a-9a51-3d1e2f4a5b6c\"}}","secret":"whsec_test","signature":"a27f6d074108ea6b5df903d3ad4520113a47aa3710cb26c24fab7e36457d915a"}'

With a token, send Authorization: Bearer YOUR_API_TOKEN as a default header (how, per SDK).

Response​

{
"valid": true,
"expected": "a27f6d074108ea6b5df903d3ad4520113a47aa3710cb26c24fab7e36457d915a",
"hints": []
}

With MCP​

Connect https://postboost.co/mcp/tools (setup) and ask, for example: Verify an HMAC webhook signature with the PostBoost verify-webhook-signature tool.

Errors​

StatusWhen
401The Authorization header holds an invalid token. Leave it out to call as a guest.
413The JSON body is larger than 128 KB.
422A field is invalid; the body lists the errors per field.
429A limit is reached; see limits.