We are evaluating Proton Workspace as a privacy-first alternative to Microsoft 365 and Google Workspace for our organization.

One important requirement is the ability to integrate Proton Meet with external enterprise knowledge management systems without relying on third-party meeting bots or compromising Proton's end-to-end encryption.

We would therefore like to request an official, documented Proton Meet Developer API and/or client-side SDK.

Requested capabilities

1. Meeting management and metadata

• Programmatically create and schedule meetings and retrieve their join URLs.
• Access meeting identifiers, titles, timestamps and available participant information, subject to appropriate authorization and privacy controls.
• Integrate meetings with external scheduling and business applications.

1. Recording lifecycle integration

• Allow authorized hosts to configure recording preferences or initiate recordings through supported clients.
• Provide client-side events or callbacks when a recording starts, stops, fails or becomes available.
• Make completed recordings accessible to authorized integrations, preferably through a secure handoff to Proton Drive.
• Never allow silent recording or bypass participant notifications.

1. Recording and transcript export

• Provide an authorized interface to retrieve recordings stored in Proton Drive.
• Support structured transcript export when Proton Meet transcription becomes available.
• Ideally support timestamps, speaker attribution and interoperable formats such as JSON, VTT or plain text.
• Allow integrations to ingest recordings independently when Proton transcription is unavailable.

1. Event-driven integrations

• Provide webhooks for privacy-preserving lifecycle events where technically appropriate.
• Alternatively, expose client-side SDK events to avoid disclosing sensitive metadata to Proton's servers.
• Support reliable processing through event identifiers, retry handling and idempotency.

1. Secure authentication and authorization

• Provide OAuth 2.0/OIDC-based delegated access with granular scopes, or an equivalent secure integration mechanism.
• Support organizational controls and revocation.
• Preserve Proton Meet's end-to-end encryption and zero-access principles.

Privacy and encryption requirements

We explicitly do not request that Proton introduce server-side access to decrypted meeting content.

Since Proton Meet uses end-to-end encryption, a client-side integration may be the preferable architecture.

An official SDK could allow the authorized meeting host's device to access a finalized recording, encrypt it for Proton Drive and notify an approved integration that the file is available.

This would preserve the existing security model while enabling enterprise automation.

Our use case: Haven Evergreen

We are developing Haven Evergreen, an enterprise knowledge management platform that ingests source material, transcribes meeting recordings and creates structured, permission-aware knowledge.

Our envisioned integration is:

Proton Meet → Proton Drive → Evergreen → Transcription and structured enterprise knowledge

Organizations could define separate Proton Drive folders for public, internal, project-specific and confidential recordings. Evergreen would synchronize authorized source folders into corresponding access-controlled knowledge areas.

The system would preserve source provenance and apply its own authorization policies independently of Proton Drive.

Why this matters

An official integration interface would make Proton Workspace significantly more attractive to organizations migrating from Microsoft Teams and Google Meet.

It would enable an ecosystem of privacy-preserving applications for knowledge management, documentation, compliance and workflow automation.

We would be interested in participating in an early developer program or discussing technical requirements with Proton's engineering team.

Related requests:

• "Programmatic Proton Meet room creation" (https://protonmail.uservoice.com/forums/967618-proton-meet/suggestions/51284719-api-for-programmatic-proton-meet-room-creation-in)
• "Native Proton Meet transcription" (https://protonmail.uservoice.com/forums/967618-proton-meet/suggestions/51213211-add-transcriptions-in-meet)