Changelog
What changed in LIVCK Cloud — new features, improvements, fixes and announced deprecations.
2026.10.3
Webhooks following Standard Webhooks
Webhooks can now be verified with any Standard Webhooks library.
New
Every webhook now carries the headers
webhook-id,webhook-timestampandwebhook-signature.X-Signature-256stays.LIVCK now generates the secret and shows it to you once. Webhooks without a secret get one automatically. When you renew it, the old one keeps signing
webhook-signaturefor 24 hours.X-Signature-256switches right away.Every delivery shows its event ID and, on failure, the reason, such as timeout or DNS. Retries carry the same ID, so you can spot duplicate deliveries. Webhooks of your subscribers are now retried on failure too.
Fixed
A webhook now only counts as delivered when your endpoint answers with 2xx. Until now a redirect counted too, although your endpoint never got anything. We no longer follow redirects. If your endpoint redirects, enter the target address directly.
Test now sends a signed sample alert in the real format. Until now it sent an unsigned message that receivers checking the signature rejected.
2026.07.2
On-call scheduling
Who gets paged at night now follows a schedule instead of a list.
New
Duty rotates daily, weekly or on a pattern of your own. Absences and stand-ins go into the same schedule. If a period ends up unstaffed, the schedule flags it on its own.
Every alert carries a link that works without signing in. One tap stops the escalation.
Your own shifts as a calendar subscription — in Outlook, Google Calendar or Apple Calendar.
Fires a real alert through every configured channel, so a wrong phone number turns up now rather than during a real incident.
An overview of who was on duty for how long.
Improved
Previously the organisation's language applied.