Developer infrastructure for events
APIs for registrations, tickets, Apple Wallet passes, check-in and webhooks.
After Hours / Sydney
Admit one.
Maya Chen
07 Nov 2026 · 19:00
General admission
01 / The layer underneath
Build what your users see. We’ll handle the event infrastructure they don’t.
Your website or app
You build the experience
Registration
Your form. Your checkout.
Tickets
Your design. Your brand.
At the door
Your scanner. Your interface.
Eventlayer
We keep the event state correct
Registrations
Events and attendee records
Ticket lifecycle
Issue, assign and cancel
Apple Wallet
Signed passes and updates
Check-in
One ticket, one admission
Webhooks send changes to your backend
Your stack
02 / Build with the API
Create an event, register an attendee, issue a ticket and add Wallet. Use the typed SDK from your backend.
Read the quickstart ↗Create an event with its local start time and timezone.
import { Eventlayer } from "eventlayer";
// Reads EVENTLAYER_KEY from your server environment.
const eventlayer = new Eventlayer();
const { data: event, error } = await eventlayer.events.create({
name: "After Hours",
startAt: { utc: "2026-11-07T08:00:00Z", timezone: "Australia/Sydney" },
});
if (error) throw error;
console.log(event.id);An event and its default General Admission ticket type.
Set EVENTLAYER_KEY in your server environment.
Explore events03 / The work behind the ticket
Creating a ticket is simple. Keeping tickets, Wallet passes, check-ins and the rest of your stack correct as things change is where it gets complicated.
The part you can see
tickets
id · attendee_id · status
Below the surface
04 / Product primitives
Six product primitives, connected through one API.
Ticket lifecycle · interactive illustration
From any existing ticket
↓ remove access
Cancelled / deleted
A registered Wallet device keeps a cancelled record so the pass can be invalidated. Otherwise, the ticket is deleted.
Select an operation to explore the ticket lifecycle.
Event
After Hours
Date
07 Nov 2026 19:00
Location
Sydney
Two scanners. One admission. · illustrated race
Scanner A
POST /v1/tickets/tkt_123/check-in
Ready to scan the same ticket
Scanner B
POST /v1/tickets/tkt_123/check-in
Ready to scan the same ticket
Your scanner. Eventlayer underneath.
At-least-once delivery. Deduplicate by event ID in your consumer.
Event time · response excerpt
"start_at": {
"local": "2026-11-07T19:00:00",
"timezone": "Australia/Sydney",
"utc": "2026-11-07T08:00:00Z"
}05 / In production
Two requests → one admission
A second scanner receives TICKET_ALREADY_CHECKED_IN.
503 → retry → 200
Inspect attempts and replay a delivery after recovery.
422 · VALIDATION_FAILED
Field details and a request ID give you the next step.
19:00 Sydney → 08:00 UTC
Keep the local event time and the instant it represents.
Connect your registration form to Eventlayer, offer Apple Wallet passes in your app, and use webhooks to update your CRM and email service. Follow the step-by-step integration guides in our docs.
Explore the integration guidesEventlayer / Start building
Create an event and issue your first ticket through the API.