API and integrations: REST API keys, webhooks, signed-token sign-in and what is not offered

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.

What the REST API covers

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

API keys

  • A site admin creates a key in Admin, under the site's Integrations tab, API keys. The secret is shown once; if it is lost, create a new key and revoke the old one.
  • Each key carries only the scopes you give it, out of 37, such as courses:read, enrollments:write or reports:read. A write scope also covers the matching read, except forms:write, which reads form templates but not form responses.
  • IP allowlist, optional: one IP address or CIDR range per line, IPv4 or IPv6, and requests from any other address get 403. Add my IP adds the address you are on.
  • Expiry, optional: the key stops working at the end of the day you pick; left blank, it works until you revoke it. A key's name, scopes, allowlist and expiry can be changed later; its secret cannot.
  • Send the key in the X-Cubite-Key header on every request to https://cubite.io/api/v1/. The key, not the host, picks the site: a key acts on the one site it was created for.
  • Each key has a per-minute limit on reads and a lower one on writes; a request past it gets 429 with a Retry-After header.
  • Write requests are logged with the key, the site, the method, the path and the source IP; reads are not. Admin shows when each key was last used.

Webhooks

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.

Webhook payloads, signatures and every event

Signed-token sign-in

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.

Other integrations

  • Sign-in on Cubite LMS: SSO with Google, GitHub or Facebook sign-in is included at $290; SAML SSO and SCIM are Enterprise, on request and scoped with your contract.
  • Payments: course checkout on your own Stripe or Kushki account, set up in the site's Payments tab.
  • In the Integrations tab: Google Analytics and Tag Manager IDs and Google Search Console, IndexNow, Bunny Stream video, an embed snippet for a course or a blog post, and an AI provider key, your own Anthropic or OpenAI key, which Draft with AI, the editor's AI assists and Repurpose run on.
  • AI assistants: Claude, ChatGPT and other MCP clients connect through Cubite's MCP server, with the permissions you approve.

Connect Claude to Cubite LMSCubite's MCP server

What is not offered

As of November 17, 2026:

  • An OpenAPI document or a request-and-response schema reference: not yet. The API reference lists every endpoint with its scope, and the authentication, error, rate-limit and webhook conventions.
  • Webhook setup through the API or the MCP server, and an API for creating API keys: both stay in Admin.
  • SAML SSO and SCIM are Enterprise, on request and scoped with your contract, and the REST API has no SCIM endpoint.
  • LTI on Cubite LMS: its plan lists none, its courses cannot be added to another LMS as an LTI tool, and the REST API has no LTI endpoint. Managed Open edX includes LTI 1.1 and 1.3 tools inside your courses; your courses inside Canvas, Blackboard or Brightspace over LTI 1.1 (LTI 1.3 as scoped work). Managed Moodle Growth ($1,190 a month) includes LTI tools inside your courses, and your courses published to other LMSs as an LTI tool.

Does Cubite LMS have a public REST API?

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.

Can a Cubite LMS API key be limited to our own servers?

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.

Which events can Cubite LMS send to a webhook?

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.

Can Cubite LMS sign learners in from our own portal without SAML?

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.

Is there an OpenAPI document for the Cubite LMS API?

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.

Talk to a person

Book a 30-minute call, or email amir@cubite.io.

Support

How can we help?

Send us a message and we'll get back to you shortly.

We typically respond within 24 hours