What's changed since the v1 specification
Learn what's different in version 2.0 of the Empath webhooks specification compared with the v1 document from September 2026.
This article lists what's new or corrected in version 2.0 of this specification (September 2026), compared with the v1 document.
What changed?
tenantIdis in every payload. v1 said there was no company ID.- Slack is supported. A Payload format option sends Slack-formatted messages. v1 said Slack URLs wouldn't work.
- Completions from SCORM, AICC, Microsoft Learn and manual completion all send
course.completed, first completion only. v1 said some might not. - Content published covers courses, knowledge checks and pathways. Progress resets no longer send it.
- Duplicate windows are fixed blocks of time (e.g. a UTC day), not rolling periods.
- Webhooks don't depend on email or bell activity. They aren't skipped because an email or bell notification already went out.
- Delivery IDs now end with a time-window part.
- The wizard's test sends the first event you ticked, not the first in list order.
- The wizard has three steps: Endpoint (name, URL, payload format, custom header), Events, Review & test.
- Only managers and admins can create, edit, test or delete webhooks.
- The unhealthy alert goes to managers and admins, not only owners.
- Screen labels changed: e.g. Create webhook, Test webhook, Healthy, Delivered, Failed, Last delivery, Completions & knowledge checks, New content.
- Invalid custom header names are silently dropped, not rejected, and private addresses fail when sending rather than when saving.
Still need help?
Reach out to your Partner Success Manager, or email us at support@empathmsp.com. We’re happy to help!
Related articles
- Payload reference
- The four events and when they're sent