Zoom API integrations
Conferencing platforms built on the Zoom API
We have built and operated Zoom-based platforms for large institutions since 2016. The pattern is always the same: Zoom runs the meetings, and our software handles identity, scheduling rules, license sharing, recordings, reporting and everything else an organisation needs around them.
Architecture
A gateway between your applications and Zoom
Our conference gateway is a REST service that hides the Zoom REST API behind rooms, meetings, series and participants. Client applications never touch Zoom credentials, and a pool of Zoom accounts is shared across them.
Dynamic account allocation
Licensed Zoom accounts sit in a queue. When a meeting starts, one is taken, the Zoom meeting is created on it, participants are registered, and the account goes back to the pool afterwards.
Named-user management
For platforms that need persistent hosts, Zoom users are created on demand, stripped of their license when idle and expired after a period of inactivity, so seats follow real usage.
Server-to-server OAuth
We use Zoom's server-to-server OAuth apps, multiple credential sets, and master accounts with sub-accounts for organisations that need separation between tenants.
Webhooks and recordings
Meeting lifecycle and recording-completed events are processed asynchronously. Cloud recordings are fetched, stored and offered to the right users under your retention rules.
Reports, polls and surveys
Attendance, call detail records, live polls and post-meeting service-rating surveys are collected per meeting and aggregated into dashboards per institution and department.
Rooms, SIP and dial-in
H.323 and SIP room systems, phone dial-in and live streaming to external platforms are supported alongside desktop and mobile clients.
Identity and policy
Your users, your rules
Institutions do not want to hand out Zoom accounts. They want their staff and students to sign in the way they already do and to be able to schedule meetings within the limits the organisation sets.
The platforms we build sit on top of your identity infrastructure: Shibboleth and SAML federations for academia, GSIS / TaxisNet OAuth2 for the Greek public sector, or plain OAuth2 and local accounts. Organisations are modelled as institutions, departments and users with role-based permissions, approval workflows for elevated rights, and configurable limits on duration, concurrency and participants.
Guests without an account can still be invited, and inactive accounts are anonymised automatically to keep personal data minimal.
- Shibboleth / SAML federated login and local accounts side by side
- GSIS / TaxisNet OAuth2 and civil-servant registry checks for government deployments
- Institution, department and user hierarchy with four-tier roles
- Scheduling limits, maintenance windows and demo rooms
- Real-time statistics with per-institution drill-down
- Automatic anonymisation of inactive users
Beyond meetings
Where we are taking it
AI meeting summaries and transcription
Zoom meeting summaries delivered into your platform, and our own Greek-language transcription pipeline with speaker identification for recordings.
Meeting bots and the Meeting SDK
Headless Meeting SDK participants for recording, captioning and automation where cloud features are not enough.
Alternative engines
The same application layer can drive LiveKit or other WebRTC infrastructure when a project needs self-hosted video.
A note on Zoom licensing
Medion7 does not resell Zoom licenses or subscriptions. We only provide services that use the Zoom infrastructure through our own applications and APIs.
Powered by Zoom. Zoom is a trademark of Zoom Video Communications, Inc.
Planning a Zoom integration?
Whether you need a full conferencing platform or a thin integration into an existing application, we can show you working systems and discuss the right shape for yours.