The versioned REST API that powers our own applications is the one you integrate: OAuth2 authentication, websockets for real time, OpenAPI documentation generated from the code.
curl https://api.bifrost.events/api/v1/events/42/attendees \
-H "Authorization: Bearer $ACCESS_TOKEN" \
-H "Accept-Language: fr"The foundation
The platform's technical building blocks, as they exist in the code.
An API organized by audiences — admin, organizer, attendee, hostess — under a single versioned prefix.
OAuth2 via Laravel Passport for integrations, Sanctum tokens for mobile applications.
Swagger/OpenAPI specification generated from the code, complemented by a Scribe integration guide.
Websocket broadcast channels: attendance, activity results, livestream status.
Badges carry an encrypted payload, verified on scan at check-in.
The platform is trilingual end to end, including AI-generated content.
Real time
During an event, state changes continuously. Instead of polling the API, subscribe to broadcast channels and receive updates as they happen.
Integration
What you need to connect your systems to the platform.
Explore the endpoints in Swagger and follow the Scribe guide for your first calls.
docs.bifrost.eventsOne versioned API base: your integrations don't break when the API evolves.
api.bifrost.events/api/v1Each organization can get a dedicated instance: an isolated environment to integrate, test, then go to production.
Tell us about your use case and the systems you want to connect.