This isn't a question email, this is a brag email. I thought I'd drop a note to show how we've been able to use the alfio API to create a "participant portal" for our event.
This pure JavaScript application fetches a ticket object from
/api/v2/public/${event}/ticket/${ticket} and an event schedule from a static YAML file. It updates the "Happening Now" card every minute, to reflect where a participant needs to go, along with links to the rooms or whatever. Just last night I finally read up on
alf.io extensions, so now the "Join Event" button in the ticket email directs to the portal, sending the event short name and ticket uuid in the request.
We're using the ticket uuid internally as a participant identifier for our home-built training software, and to track surveys. The link URLs in the static file are templates that get filled in, so we can send folks off to partially pre-filled forms.
This portal runs entirely client-side. The only server change was to add a proxy configuration to our nginx server to skirt around the lack of a CORS header in the one API call we use.
I'm very excited that this is all coming together so nicely. I know a lot of commercial offerings, and even odoo, want to provide the entire schedule and speakers and everything in-app, but this solution actually works much better for us.
Thank you for creating such a great system!