API for Programmatic Proton Meet Room Creation (Independent of Booking System)
I am requesting a public API endpoint to programmatically create unique Proton Meet rooms and retrieve their join URLs. This is essential for developers building self-service scheduling applications that need to generate dynamic, isolated meeting links for every event.
My application allows users to schedule meetings programmatically and sends calendar invitations (.ics) via Proton SMTP. To make these invites functional, the .ics file requires a specific URL property pointing to a unique meeting room.
Currently, Proton Meet rooms can only be created manually via the web interface. There is no API to:
- Trigger the creation of a new, unique room.
- Retrieve the resulting join URL.
"Proton Booking" is Not the Solution: I am aware of the existing Proton Booking feature. However, it is not suitable for my use case because:
Scope Mismatch: The Booking feature is designed for a specific "booking flow" (availability slots, booking pages, confirmation emails) which includes logic and UI elements that are not needed for my application.
Flexibility: My application manages its own scheduling logic, database, and notification flows. I do not want to force my users into the rigid Proton Booking workflow or expose my internal scheduling data to the Booking system.
Granularity: I need to create a meeting link only when a specific event is triggered in my app, independent of any public availability calendar or booking page.
What I Need: A simple, authenticated API call (e.g., POST /api/meet/create) that:
- Generates a unique room ID.
- Returns the full join URL (e.g., https://meet.proton.me/xyz123).
- Allows me to inject this URL directly into the URL: field of a custom .ics file.
Impact: This feature would unlock programmatic integration for Proton Meet, allowing it to compete with other providers (Zoom, Google Meet) that offer room creation APIs. It would enable privacy-first developers to build custom scheduling tools, CRM integrations, and automated workflows without compromising on the "zero-access" security model.