Webhook payload conventions - Zapnito Docs

Payload formats aren’t yet consistent across events. The details below come from the example payload on each event page, so check the example for the event you’re handling and parse values defensively.

Timestamps

Format	Example	Events
Date and time without a time zone	`2026-03-02 09:15`	User registered, User updated
ISO 8601 in UTC	`2026-03-10T13:52:06Z`	Content published, Content updated, Content viewed, Discussion created, Discussion reply created, Event RSVP reply
ISO 8601 with a UTC offset	`2026-03-12T08:40:35+00:00`	Document downloaded
RFC 2822-style	`Wed, 18 Mar 2026 10:01:28 UTC +00:00`	Course participation updated

IDs

Strings: the IDs in User added to group, User removed from group, Content viewed, Discussion created and Discussion reply created, and room.id in the content payloads.
Integers: the IDs in Document downloaded, Course participation updated and Event RSVP reply.

If you handle more than one event, convert IDs to a single type before you compare or store them.

Booleans

The confirmed field in the User registered and User updated payloads is the string "true", not a boolean. The room flags in the content payloads (open, secret and private) are booleans.

Personal data

User-related payloads include names and email addresses. The User deleted payload still contains the deleted user’s name, email address and professional registration number. Treat these payloads as personal data when you log or store them.