Developers
Call the ClassroomIO API, connect MCP or Token Auth, self-host the stack, or contribute to the codebase.
You’re here to build something on top of ClassroomIO, not run an academy in it: calling the API from your own app, connecting an agent client or an SSO-style handoff, running the stack on your own infrastructure, or working on ClassroomIO’s own code.
curl https://api.classroomio.com/public-api/v1/courses \
-H "Authorization: Bearer cio_api_your_key_here"const res = await fetch('https://api.classroomio.com/public-api/v1/courses', {
headers: { Authorization: 'Bearer cio_api_your_key_here' }
});
const { data } = await res.json();Full endpoint reference, request/response schemas, and how to get a key: API.
Connect
Bring an agent client or an existing sign-in flow into ClassroomIO instead of calling the REST API directly.
MCP
Connect Claude Code, Codex, Cursor, or other MCP clients for course authoring.
Token Auth
Sign users in to ClassroomIO from your own app with a short-lived JWT.
Self-hosting
Run the full stack on your own infrastructure.
Self-Hosting
Docker, Railway, Coolify, or Dokploy — server requirements and install steps.
Architecture
The services in the stack — dashboard, api, jobs worker, Postgres, Redis, object storage — and how they talk to each other.
Contributing
ClassroomIO is open source. These guides cover getting the project running on your machine, the conventions we follow, and the infrastructure behind the platform.
