Apache OpenMeetings
Apache OpenMeetings is a web conferencing and collaboration tool that provides video conferencing, instant messaging, white board, collaborative document editing, and other groupware tools. It offers integration APIs for LMS platforms.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Apache OpenMeetings the way a machine reads it — 146 machine-readable artifacts across 1 API, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Apache OpenMeetings scores 33.6/100 (thin), with a separate agent-readiness read of 17/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-10 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Apache OpenMeetings's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/apache-openmeetings/"
title="Apache OpenMeetings on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/apache-openmeetings.svg"
alt="Apache OpenMeetings Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/apache-openmeetings/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/apache-openmeetings/"
title="Apache OpenMeetings on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/apache-openmeetings/card.svg"
alt="Apache OpenMeetings Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Apache OpenMeetings
Each block below is one kind of artifact we hold for Apache OpenMeetings. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 10
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Apache OpenMeetings CalendarService API
The CalendarService API from Apache OpenMeetings — 8 operation(s) for calendarservice.
Apache OpenMeetings ErrorService API
The ErrorService API from Apache OpenMeetings — 2 operation(s) for errorservice.
Apache OpenMeetings FileService API
The FileService API from Apache OpenMeetings — 8 operation(s) for fileservice.
Apache OpenMeetings GroupService API
The GroupService API from Apache OpenMeetings — 5 operation(s) for groupservice.
Apache OpenMeetings InfoService API
The InfoService API from Apache OpenMeetings — 3 operation(s) for infoservice.
Apache OpenMeetings NetTestService API
The NetTestService API from Apache OpenMeetings — 1 operation(s) for nettestservice.
Apache OpenMeetings RecordingService API
The RecordingService API from Apache OpenMeetings — 4 operation(s) for recordingservice.
Apache OpenMeetings RoomService API
The RoomService API from Apache OpenMeetings — 11 operation(s) for roomservice.
Apache OpenMeetings UserService API
The UserService API from Apache OpenMeetings — 5 operation(s) for userservice.
Apache OpenMeetings WbService API
The WbService API from Apache OpenMeetings — 4 operation(s) for wbservice.
Scroll within the panel for all 10 ·
Open Collections 12
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONApache OpenMeetings REST CalendarService API
OPEN COLLECTIONApache OpenMeetings REST CalendarService ErrorService API
OPEN COLLECTIONApache OpenMeetings REST CalendarService FileService API
OPEN COLLECTIONApache OpenMeetings REST CalendarService GroupService API
OPEN COLLECTIONApache OpenMeetings REST CalendarService InfoService API
OPEN COLLECTIONApache OpenMeetings REST CalendarService NetTestService API
OPEN COLLECTIONApache OpenMeetings REST API
OPEN COLLECTIONApache OpenMeetings REST CalendarService RoomService API
OPEN COLLECTIONApache OpenMeetings REST CalendarService UserService API
OPEN COLLECTIONApache OpenMeetings REST CalendarService WbService API
OPEN COLLECTIONScroll within the panel for all 12 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Apache Openmeetings Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Features 8
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Video Conferencing
HTML5-based audio/video conferencing with multi-resolution camera support
Screen Sharing
Full screen sharing and recording capabilities
Whiteboard
Multi-instance collaborative whiteboard with document import
File Management
Advanced file explorer with drag-and-drop for private and public drives
Calendar Integration
Meeting planning with email invitations and secure hash links
Recording
Session recording to MP4 with audio and video capture
REST API
Full REST API for programmatic management of rooms, users, and recordings
SOAP API
Legacy SOAP API for integrations requiring XML-based communication
Scroll within the panel for all 8 ·
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Apache Openmeetings Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Apache OpenMeetings API Rules
SPECTRALApache OpenMeetings API Rules
SPECTRALJSON Schema 32
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
Address
JSON SCHEMAAppointmentDTOListWrapper
JSON SCHEMAAppointmentDTO
JSON SCHEMAAppointmentDTOWrapper
JSON SCHEMAExternalUserDTO
JSON SCHEMAFileExplorerObject
JSON SCHEMAFileExplorerObjectWrapper
JSON SCHEMAFileItemDTOListWrapper
JSON SCHEMAFileItemDTO
JSON SCHEMAFileItemDTOWrapper
JSON SCHEMAGroupDTOListWrapper
JSON SCHEMAGroupDTO
JSON SCHEMAHealth
JSON SCHEMAHealthWrapper
JSON SCHEMAInfo
JSON SCHEMAInfoWrapper
JSON SCHEMAInvitationDTO
JSON SCHEMAMeetingMemberDTO
JSON SCHEMARecordingDTOListWrapper
JSON SCHEMARecordingDTO
JSON SCHEMARoomDTOListWrapper
JSON SCHEMARoomDTO
JSON SCHEMARoomDTOWrapper
JSON SCHEMARoomFileDTO
JSON SCHEMARoomOptionsDTO
JSON SCHEMAServiceResult
JSON SCHEMAServiceResultWrapper
JSON SCHEMAUserDTOListWrapper
JSON SCHEMAUserDTO
JSON SCHEMAUserDTOWrapper
JSON SCHEMAUserSearchResult
JSON SCHEMAUserSearchResultWrapper
JSON SCHEMAScroll within the panel for all 32 ·
JSON Structure 32
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Apache Openmeetings Address Structure
JSON STRUCTUREApache Openmeetings Appointment Dto Structure
JSON STRUCTUREApache Openmeetings Appointment Dto Wrapper Structure
JSON STRUCTUREApache Openmeetings External User Dto Structure
JSON STRUCTUREApache Openmeetings File Explorer Object Structure
JSON STRUCTUREApache Openmeetings File Item Dto List Wrapper Structure
JSON STRUCTUREApache Openmeetings File Item Dto Structure
JSON STRUCTUREApache Openmeetings File Item Dto Wrapper Structure
JSON STRUCTUREApache Openmeetings Group Dto List Wrapper Structure
JSON STRUCTUREApache Openmeetings Group Dto Structure
JSON STRUCTUREApache Openmeetings Health Structure
JSON STRUCTUREApache Openmeetings Health Wrapper Structure
JSON STRUCTUREApache Openmeetings Info Structure
JSON STRUCTUREApache Openmeetings Info Wrapper Structure
JSON STRUCTUREApache Openmeetings Invitation Dto Structure
JSON STRUCTUREApache Openmeetings Meeting Member Dto Structure
JSON STRUCTUREApache Openmeetings Recording Dto List Wrapper Structure
JSON STRUCTUREApache Openmeetings Recording Dto Structure
JSON STRUCTUREApache Openmeetings Room Dto List Wrapper Structure
JSON STRUCTUREApache Openmeetings Room Dto Structure
JSON STRUCTUREApache Openmeetings Room Dto Wrapper Structure
JSON STRUCTUREApache Openmeetings Room File Dto Structure
JSON STRUCTUREApache Openmeetings Room Options Dto Structure
JSON STRUCTUREApache Openmeetings Service Result Structure
JSON STRUCTUREApache Openmeetings Service Result Wrapper Structure
JSON STRUCTUREApache Openmeetings User Dto List Wrapper Structure
JSON STRUCTUREApache Openmeetings User Dto Structure
JSON STRUCTUREApache Openmeetings User Dto Wrapper Structure
JSON STRUCTUREApache Openmeetings User Search Result Structure
JSON STRUCTUREApache Openmeetings User Search Result Wrapper Structure
JSON STRUCTUREScroll within the panel for all 32 ·
Examples 32
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Scroll within the panel for all 32 ·
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 4
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
LMS Integration
Integrate OpenMeetings with Moodle, Sakai, and other LMS platforms
Corporate Conferencing
Host virtual meetings and webinars for distributed teams
Remote Education
Deliver interactive online courses with whiteboard and screen sharing
Custom Conferencing Portal
Build branded conferencing portals using the REST API
Integrations 7
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Moodle
Official Moodle plugin for LMS integration
Sakai
Sakai CLE integration for academic conferencing
LDAP/Active Directory
Enterprise authentication via LDAP and ADS
OAuth2
Social login via OAuth2 providers
Asterisk/VoIP
VoIP integration via Asterisk for phone conferencing
CalDAV
Calendar synchronization via CalDAV protocol
Kurento Media Server
WebRTC media server for streaming and recording
Scroll within the panel for all 7 ·
Resources
Every other property we hold for Apache OpenMeetings — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 1
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 3
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Company 1
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/apache-openmeetings · machine-readable index on apis.io
This is an independent, third-party profile of Apache OpenMeetings, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.