Paid API keys
API keys only work for active paid workspaces.
Create meetings, classrooms, attendance reports, meeting outcomes, and scheduling workflows from your own school, HR, CRM, church, or operations platform.
curl https://yourdomain.com/api/v1/meetings \
-H "Authorization: Bearer om_live_..." \
-H "Content-Type: application/json" \
-d '{
"title": "Staff training",
"meeting_type": "training",
"scheduled_at": "2026-07-01T14:00:00Z",
"duration_minutes": 60
}'API keys only work for active paid workspaces.
Raw keys are never stored after creation.
Meetings, classrooms, attendance, and outcomes.
Track calls, routes, status codes, and activity.
Endpoints
/api/v1/meVerify key, workspace, billing status, and plan.
/api/v1/meetingsList meetings in the paid workspace.
/api/v1/meetingsCreate a meeting and receive join links.
/api/v1/meetings/{id}Fetch meeting details, participants, attendance, and meeting notes.
/api/v1/attendanceExport attendance records for a workspace or meeting.
/api/v1/classroomsList classroom programs created in OnadaMeet.
/api/v1/classroomsCreate an online classroom from another system.
The API makes OnadaMeet harder to replace because customers can connect it to the systems they already use every day.
Schools can create classes from their SIS or LMS.
HR tools can create onboarding rooms and pull attendance.
Churches and nonprofits can sync training records.
Sales systems can attach meeting outcomes to customer accounts.
If a workspace cancels or loses active billing, API calls return payment_required until the plan is restored.