Short answer (updated November 17, 2026)
Cubite LMS includes a headless REST API, webhooks and an MCP server in its Growth plan, at $290 a month or $2,900 a year. A site admin creates API keys under Integrations, each with only the scopes it needs and, if you want, an IP allowlist and an expiry date; every request sends the key in the X-Cubite-Key header. Webhooks post 20 kinds of events, signed with HMAC-SHA256, to a URL you subscribe. There is no OpenAPI document yet, and webhooks are set up in Admin only.
The API reference at cubite.io/developers lists every public route under /api/v1 with the scope it needs: 126 endpoint rows across 25 resources, among them courses and course content, pages and blog posts, site settings and the homepage, users, enrollments, groups, learning paths, certificates, grading, reports and the learner transcript.
Bodies and responses are JSON, and list endpoints take limit and offset. One call to POST /api/v1/enrollments enrolls one learner or up to 100 at once.
The REST API referenceA worked example: SureCart to Cubite enrollment
A site admin subscribes a URL in Admin, under Integrations, Webhooks, to the event types it needs or to all of them, and can add custom headers. Cubite generates a signing secret and shows it once. A subscription can be paused and sent a test event, and its delivery log lists each delivery.
Each delivery is a POST with a JSON body, any custom headers you added and three Cubite headers: X-Cubite-Event, X-Cubite-Signature (sha256= followed by the hex HMAC-SHA256 of the raw body, keyed with the secret) and X-Cubite-Delivery-Id. Recompute the HMAC over the raw body and compare it in constant time. A delivery your endpoint fails is sent again, so use the delivery id to skip one you already handled.
The 20 event types: enrollment.created, course.completed, certificate.issued, certificate.revoked, certificate.expiring, certificate.expired, quiz.passed, quiz.failed, form.submitted, assignment.submitted, assignment.passed, assignment.failed, assignment.returned, open_response.submitted, open_response.self_assessed, open_response.peer_assessed, open_response.staff_assessed, open_response.passed, open_response.failed, open_response.retried. As of November 17, 2026, do not count on certificate.expiring and certificate.expired yet: like the certificate expiry emails, they come from a daily certificate job.
Any public endpoint that accepts a JSON POST can receive them, such as an automation tool's incoming-webhook trigger or your own backend. Webhooks are set up in Admin only: the API and the MCP server can read subscriptions and their delivery log (webhooks:read) but cannot create or change them, because a subscription keeps sending after the key that made it is revoked.
Cubite LMS Growth also includes signed-token sign-in: your own portal or app signs a learner in to your Cubite site with a short-lived signed token that can name the learner's groups, so learners need no second password. It is not SAML or SCIM.
Turn it on in Admin, under Integrations, Signed-token sign-in. The secret is shown once, and the API reference documents the token.
As of November 17, 2026:
Yes. Cubite LMS includes a headless REST API under /api/v1, with HMAC-signed webhooks and an MCP server, in its Growth plan at $290 a month or $2,900 a year. The API reference at cubite.io/developers lists every endpoint with the scope it needs.
Yes. Give a Cubite LMS API key an IP allowlist of single addresses or CIDR ranges, IPv4 or IPv6, and requests from anywhere else are refused with 403. A key can also carry an expiry date and only the scopes it needs.
Cubite LMS sends these 20 event types: enrollment.created, course.completed, certificate.issued, certificate.revoked, certificate.expiring, certificate.expired, quiz.passed, quiz.failed, form.submitted, assignment.submitted, assignment.passed, assignment.failed, assignment.returned, open_response.submitted, open_response.self_assessed, open_response.peer_assessed, open_response.staff_assessed, open_response.passed, open_response.failed, open_response.retried. Subscribe a URL to the ones you need, or to all of them; each delivery is signed with HMAC-SHA256. Do not count on certificate.expiring and certificate.expired yet: like the certificate expiry emails, they come from a daily certificate job.
Yes, with signed-token sign-in, included in Cubite LMS Growth: your own portal or app signs a learner in to your Cubite site with a short-lived signed token that can name the learner's groups, so learners need no second password. It is not SAML or SCIM; SAML SSO and SCIM are Enterprise, on request and scoped with your contract.
Not yet. The Cubite LMS API reference at cubite.io/developers lists every endpoint with its scope, plus the authentication, error, rate-limit and webhook conventions; request and response schemas and an OpenAPI document are later steps.
Send us a message and we'll get back to you shortly.