Calendar API
I have python code that pulls upcoming assignments from a couple of websites and puts them into my current calendar. This current calendar is google but thanks to you all I am moving away from the ever seeing eye of google. It would be nice to have an API for adding events to my calendar programmatically.
-
jdsika
commented
I strongly support an official Proton Calendar API. I would like to highlight a requirement complementary to the proposed local CalDAV Bridge: secure, standards-based integration with hosted applications, business automation platforms and AI agents, without compromising Proton Calendar's end-to-end encryption.
1. The requirement: authorized remote interoperability
A local CalDAV Bridge would solve desktop and locally hosted integrations, but it does not fully address applications running in the cloud.
Business applications need to perform operations such as:
- Query authorized calendar availability.
- Create, update, reschedule and cancel appointments.
- Manage attendees and invitations.
- Retrieve selected events when explicitly authorized.
- Detect calendar changes through synchronization or event notifications.
- Create or attach Proton Meet links when scheduling meetings.These capabilities are necessary for booking systems, workflow automation, enterprise applications and AI assistants.
2. Rely on established standards
Please prioritize existing protocols rather than introducing an entirely proprietary integration model:
- CalDAV (RFC 4791) and iCalendar (RFC 5545) for calendar interoperability.
- iTIP/iMIP (RFC 5546/6047) for scheduling and invitation workflows.
- OAuth 2.0 with PKCE or equivalent standardized delegated authorization.
- Standardized incremental synchronization and conflict detection.
- A documented client SDK where cryptographic operations cannot safely be performed by a conventional server-side API.An eventual JMAP Calendars implementation could also provide a modern JSON-oriented interface as that standard matures.
3. Preserve E2EE by design
The API should not require Proton's servers to decrypt private calendar data.
Instead, please evaluate complementary integration models:
A. Limited cloud-accessible operations
Expose narrowly scoped capabilities such as authorized Free/Busy queries or appointment scheduling, without disclosing unrelated event titles, descriptions or attendee information.
These operations should remain opt-in because even availability metadata can reveal sensitive information.
B. Trusted client-side SDK
Provide an official SDK capable of handling encryption, decryption and authorized calendar operations within a user-controlled environment.
Applications requiring decrypted information would explicitly become trusted endpoints. Proton should document this trust boundary and avoid exporting private keys to unrelated third-party services.
C. Secure organizational automation
Support carefully scoped, revocable integration credentials and approved automation identities, with transparent auditing and explicit organizational controls.
Unattended integrations should have a supported authentication and key-management model rather than relying on undocumented APIs or storing ordinary user login credentials.
4. Apply least-privilege authorization
Ideally, applications could request separate permissions for:
- Free/Busy information only.
- Read access to selected calendars.
- Creating events.
- Updating or deleting authorized events.
- Managing meeting invitations.Users and administrators should be able to review and revoke these permissions independently.
5. Why this matters
Organizations considering migration from Google Workspace or Microsoft 365 need to preserve their existing integration capabilities.
For example, Haven Evergreen is an enterprise knowledge-management application that could benefit from user-authorized calendar and scheduling integrations. The same requirement applies to many independent productivity and automation tools.
Without an official integration mechanism, organizations must choose between maintaining their existing workflows and adopting Proton's privacy-focused ecosystem.
Recommendation: Deliver the local CalDAV Bridge for conventional clients and a complementary, officially supported developer SDK or constrained API for secure remote automation.
Interoperability and E2EE should be complementary design objectives, not mutually exclusive choices.
-
Ben
commented
Proton Calendar is lacking an API. We really need this for integration and automation!
-
Regs
commented
No Public API for basic functionalities in 2026 is a bit odd.
Is there anything that is stopping it from the technical side?
-
Arthur
commented
Come on proton, you know your user base are tech aware people.
That I cant have any automations is embarrassing.Did anyone try https://github.com/roman-16/proton-cli ?
-
TPDog
commented
I don’t know why we bother. I have monitored this topic for months and have NEVER seen one response from anyone from Proton. Really frustrating.
-
Frederick
commented
I use Proton precisely because my calendar and files aren't owned by an ad company — that's why I left Google and won't go back.
What blocks me today: there's no API or connector to let Proton Calendar and Proton Drive talk securely to external tools. Every morning an AI assistant builds me a day-brief from my calendar, email and tasks. Everything connects except the calendar, because Proton is the one service that can't. The same gap hits automation tools like n8n and Home Assistant.
I'm not asking for less privacy. I'm asking for a Proton-controlled, opt-in API — via Proton Bridge or CalDAV if that's cleaner — so I decide what I expose. Without that bridge I'm forced to choose between my privacy and my workflow, and I shouldn't have to.
-
Ian
commented
Trying to persuade business contacts to Proton as their platform of choice, away from Google. I have hundreds of users of an application in daily use that currently offers Google calendar sync. If I had an API, my customers would be in a much better position to ditch Google and its invasive practices.
-
Pierre C. DANIEL
commented
J'ai plusieurs site WEB qui s'appuient sur l'API Google pour gérer les RDV, c'est bien dommage que je ne puisse pas passer par Proton pour mon application peropnnelle.
Je n'utilise presque plus Proton Calendar à cause de cela. Il n'y a que la possibilité d'avoir une page de gestion de RDV pour un compte familial. Et l'intégration de cette page dans mes sites n'est pas OK -
Tom Singleton commented
Throwing my vote in here for this as well. Without a way to use other apps/tools to automatically handle the calendar I can't use this service.
-
JJ
commented
Please. I have a self hosted Calendar for my business for meetings. I also like other people have jumped the google ship but my proton calendar is severely missing its API to make the meetings via api.
-
Joost
commented
The future is all API, so this is a blocker for me is there no ways to interact with API's.
-
Adam
commented
Something like proton mail bridge, but supporting CalDAV would be ideal. I'd like to be able to connect trusted productivity tools into the calendar.
-
Imre Antalfy
commented
I would move to Proton with the whole company if if this exists. i really want the local automation, and if i cant make calendar entries, its a part missing!
-
ProtonUser
commented
It would be good to be able to choose either an e2ee calendar, or a calendar with API integration. Maybe both is possible (although tricky, no doubt), but that choice would seem reasonable.
-
Marios
commented
Would love this to be available for local AI calendar management.
-
Nick Haslam
commented
This would be a really useful feature, for many who self host, to increase privacy. If a proton hosted API isn’t possible, could the calendar be added to the proton email bridge?
-
Oliver Hansen
commented
I need this to integrate with my home assistant so the family can know my schedule.
-
Denix
commented
I love automations and I would love to use my home assistant to automagically add events to my calendar. please take this into consideration
-
G
commented
I would love to create my own privately hosted automations with my calendar
-
Mazda
commented
Proton calendar is useless unless they do this