ewent
Developers
Attendance, as an API.
Per-attendee checklists and timezone-local reminder scheduling, behind three endpoints. No migration for your customers, no account for their attendees.
Design notes
Things worth knowing before you build.
◴
Scheduling is per attendee
Send us a timezone per attendee and every touchpoint lands in their local morning. The event’s own timezone is only a fallback.
⚿
Signed URLs, not sessions
The checklist URL is the auth. Render it server-side, put it anywhere, and expect it to expire.
⊞
Occurrences, not events
A recurring series is a template with many dated occurrences. Attendees attach to an occurrence.
⊟
Idempotency by email
Re-attaching the same address to the same occurrence returns the existing record rather than duplicating it.
Not available yet: self-serve keys, a sandbox, and outbound
webhooks. Keys are issued by hand today — ask and we will set you up.
Build attendance into your platform.
Three calls, no migration for your customers, and the timezone logic already solved.