Latest News from the Applivery team
Improvement
App Distribution
Device Management

🔐 Stronger, Lighter Signatures for Applivery Webhooks

Karla avatar
Shared by Karla •

If you use webhooks to connect Applivery with your ITSM, automation tools, or internal systems, you need to know that every call really comes from Applivery. Until now, the applivery-signature header carried the whole event inside it. With large events, that header could grow so big that some proxies and servers rejected the request.

That's why Applivery webhooks now include a new signature header: applivery-signature-v2.

✨ What's New

The new header is still an HS256 JWT signed with your webhook token, the same one you already use. Instead of the whole event, it only carries a SHA-256 hash of the request body and an expiry time. Your request body and your token don't change.

⚙️ Key Capabilities

  • Small, fixed-size header: it stays the same size regardless of the size of the event, so proxies and servers no longer reject large calls.
  • Stronger integrity check: the signature covers the exact bytes of the body you receive, so any change to the body is detected.
  • Replay protection: each signature expires 5 minutes after it's sent, so a captured call can't be replayed later.

🔄 Nothing Breaks Today

During the transition, every webhook call carries both applivery-signature and applivery-signature-v2, so your current integrations keep working as they are. The old applivery-signature header is now deprecated and will be removed in a future release. We'll announce the removal date in advance.

📌 What You Need to Do

  1. Update your webhook receivers to verify applivery-signature-v2.
  2. Once it works, stop reading applivery-signature.

You'll find the step-by-step verification process and a Node.js example in the documentation for Device Management webhooks and App Distribution webhooks.