Skip to content
Scope an integration

Integrations

Open edX Integration Services

Open edX is flexible because it's open source, which also means every instance is configured differently. We build Open edX integrations and plugins that connect learners, enrolments and results to the rest of your systems.

We build integrations with Open edX instances, self-hosted or run by a hosting provider: SSO, automated enrolment from HRIS, CRM or e-commerce, grade and completion sync, LTI 1.3 tools and custom plugins that extend the platform without forking it. Most single Open edX integrations take 2–8 weeks, depending on the release and instance access.

Who is this for?

  • SaaS vendors whose customers run Open edX. Universities, course providers and corporate academies on Open edX want your tool to work inside their courses and share learner data, usually through LTI or the platform’s APIs.
  • Companies running Open edX. You run Open edX and need it connected to SSO, HR, CRM, payments and reporting, so enrolments and results don’t depend on manual exports.

What do we build?

  • Enrolment automation Learners enrolled in courses from HRIS, CRM or e-commerce events, and unenrolled when access ends.
  • Grades and completion sync Course grades, completions and certificates sent to HRIS, CRM or a data warehouse.
  • Single sign-on Sign-in through your identity provider with SAML or OAuth, using Open edX’s third-party authentication.
  • LTI tools Your product embedded in Open edX courses with LTI 1.3, or external LTI content added to courses.
  • Custom plugins Django app plugins that use Open edX Events and Filters to add behaviour without forking the platform.

Typical data flows

DataDirectionMethodFrequency
Users and enrolmentsSource → Open edXEnrollment API (REST)Event-driven
GradesOpen edX → targetCourse Grades APIHourly or daily
Completions and certificatesOpen edX → targetCompletion and Certificates APIs, or Open edX EventsNear real-time or daily
Learner activityOpen edX → warehouseTracking logs or the event busStreaming or daily

Have an integration request in your backlog?

Send it over. You get a written scope and a fixed quote within 2–3 days.

Scope an integration

How do we approach Open edX?

  • API and authentication Open edX exposes REST APIs from the LMS and related services, authenticated with OAuth 2.0. An admin creates an OAuth application for the integration, which uses the client credentials flow to obtain JWT access tokens tied to a service user with the right permissions.
  • Events and change detection Rather than relying on webhooks, we use Open edX Events, consumed through a small plugin or the event bus, alongside tracking logs. Scheduled API polling for grades and completion acts as a reconcile, so results still arrive if an event is missed.
  • Known gotchas APIs and settings change between named Open edX releases, so we confirm the exact release and any customisations before mapping. Hosted instances may limit Django admin or plugin access, so we check with the hosting provider what can be deployed.

Delivery process

  1. Scoping (2–3 days) Systems, fields and edge cases mapped; written scope and fixed quote.
  2. Build (2–5 weeks) Senior-reviewed build with weekly demos.
  3. Reconcile and launch Dry run, source-vs-target report, cutover.
  4. Run and maintain Monitoring, alerts and fixes when APIs change.

Proof

Related work. Our LMS work includes the custom LMS that became the core product of Cyber Inc., a privacy and security awareness training company, with interactive video, multi-tenancy, gamification and white-label B2B distribution. As a LearnUpon Professional Partner, we also connect LearnUpon enterprise customers’ HRIS, CRM and SSO systems. Open edX projects use the same enrolment, reconciliation and monitoring patterns. See our case studies.

FAQ

Frequently asked questions

Can't find your question? An integration engineer will answer it.

Last updated

Which Open edX products do you integrate with?

The Open edX platform, including the LMS and Studio, plus related services where your instance runs them. We also build LTI 1.3 integrations and Django plugins that use Open edX Events and Filters.

How long does an Open edX integration take?

Most single Open edX integrations take 2–8 weeks. A plugin or LTI tool can take longer if it has to support several Open edX releases.

Can you maintain it after launch?

Yes. We offer monitoring, alerting and ongoing support, or a full handover with documentation.

Scope your Open edX integration in 30 minutes.

Tell us what needs to connect and get a clear plan.