Tickets & QR codes

What is in the QR code

The bare registration id, as a plain string — for example pNd1m0TRqN8Hx5a1QopI. No URL, no JSON, no signature. Just the id.

Where to get the id

• registrationId from POST /events/{id}/register
• registrationId from the registration.confirmed webhook
• id on each row of GET /events/{id}/registrations

Rendering it

Any QR library will do. This is exactly what our own mailer runs, so a code you draw this way scans in the Vihaya check-in app identically to one we sent.

import QRCode from 'qrcode';

const png = await QRCode.toBuffer(registrationId, {
  type: 'png', width: 480, margin: 1, errorCorrectionLevel: 'M',
});

The scanner additionally parses {"eventId":"…","registrationId":"…"} if you would rather encode JSON. A bare id is what Vihaya itself emits.

Sending your own ticket email

Vihaya’s ticket email is not customisable — there is no template uploader and no per-organiser branding. You do not have to use it. Everything needed to send your own already crosses the wire, so it becomes your template, your domain and your sender reputation.

1. Point a webhook at your server. Set the URL and secret in the dashboard, then verify the signature on every delivery — see Webhooks.
2. Read the attendee off the payload. name, email, eventTitle, ticketType and quantity are all in data. A standard ticket needs no follow-up call.
3. Render the QR yourself from data.registrationId, as above.
4. Send from your own domain. Your ESP, your template, your branding. Nothing in this step touches Vihaya.
5. Ask support to switch ours off. This is the one step you cannot self-serve: sendTicketEmails is fixed in Firestore rules so an organiser cannot silence their own attendees’ tickets by accident. Until support flips it, the attendee receives both emails.