Eric
My feedback
2 results found
-
304 votes
An error occurred while saving the comment Eric
supported this idea
·
-
12 votesEric
supported this idea
·
Description:
Proton Pass recently launched an open API, and it's fantastic. It would be incredibly valuable to have the same for Proton Mail.
What I'm asking for: A documented, officially supported REST API for Proton Mail that allows authenticated users to programmatically interact with their own mailbox. Core functionality would ideally include:
Listing/reading messages and threads
Sending messages
Managing labels and folders
Search
Marking read/unread, archiving, deleting
Webhook or polling support for new mail notifications
Why this matters:
Right now, the only programmatic options are IMAP via Proton Bridge (desktop only, not cloud-friendly, requires local app running) or screen-scraping (fragile, breaks on UI changes, violates spirit of the product).
An API would unlock legitimate use cases that Bridge can't serve:
Server-side automation (auto-filing receipts, parsing statements, ticketing workflows)
Integration with personal productivity tools, dashboards, and AI assistants
Cross-platform apps and custom notification pipelines
Reliable backup and archival solutions
Business workflow integrations (CRM, helpdesk, etc.)
Proton already proved the model works with the Pass API. Mail is arguably the more requested use case across the community. I'd happily accept scoped, read-only or rate-limited access as a starting point, similar to how Pass rolled out incrementally.
The security model is well within Proton's wheelhouse. Signed/encrypted API calls, OAuth-style scoped tokens, per-app passwords, and audit logging are all established patterns that would preserve Proton's privacy guarantees while opening the door for developers who want to build on top of their own data.