Integration guide
Security and support
Keep a small integration boundary and collect only the customer information your application is authorised to handle.
Protect secrets and capabilities
Keep API, provider, service-role, signing, cron and encryption keys in server environments, with separate test/live material. Never prefix secrets NEXT_PUBLIC_, include them in URLs or send them to browser analytics. Rotate exposed secrets and revoke compromised credentials.
Checkout, receipt, invitation and private member-ticket URLs are bearer capabilities. Do not log or publish them. Use HTTPS and private/no-store handling for booking results. Public widget IDs identify an application and do not grant private access.
Minimise attendee information
Default order/ticket reads contain no names/contact/QR. Attendee names and contact have separate opt-in scopes; erased data stays null. Retain only what you need, restrict your own staff and honour erasure and revocation.
Group duplicate-email/phone checks are not verified-human identity. Do not advertise them as protection against a person claiming with two entirely different contacts. Keep claims in the supported buyer/attendee flow.
Investigate an error safely
Keep the request ID, operation, approximate time, environment and safe error code. Do not attach credentials, QR codes, private URLs or buyer/attendee details to a public report.
Unknown-key failures stay in safe server logs; authenticated request counts are retained for about 30 days with bounded cleanup. Admin oversight displays safe activity and exhausted delivery counts. Review application suspension and creator/event permissions before reissuing credentials.