Moodle Marketplace

Developer Tools

Moodle Pty Ltd · Developer tools & code hosting

Best for: Moodle plugin developers, education-technology vendors, and higher-education, school, government, or corporate-learning providers seeking official ecosystem discovery for native extensions, LTI, authentication, payments, analytics, content, AI, or web-service integrations.

Overview

Moodle Marketplace is the official discovery and distribution channel for Moodle plugins and integrations, replacing the former Plugins Directory. Its catalog helps educators, institutions, administrators, and Moodle sites find solutions by plugin type, supported Moodle version, price, and Moodle certification. Listings can present descriptions, compatibility, release information, installation counts, pricing, and certification or partner status where applicable. The taxonomy spans activities, content, administration, grades, courses, themes, messaging, reports, authentication, enrolment, payment gateways, LTI, web-service protocols, repositories, media, AI providers, and other external-service integrations. Developers build with Moodle’s PHP-based plugin architecture and documented core APIs, while external systems can use Moodle’s Web Service and External Services frameworks. Commercial terms and current submission requirements should be confirmed through the provider documentation.

How to build & ship

  1. 1Choose the appropriate Moodle plugin type or integration surface for the intended functionality.
  2. 2Implement the extension with relevant Moodle core APIs, plugin conventions, compatibility declarations, upgrades, privacy handling, testing, and documentation.
  3. 3For an external integration, define or consume Moodle Web Service and External Services functions, endpoints, and site-level configuration as applicable.
  4. 4Prepare version compatibility information, documentation, screenshots, a code repository, and a public issue or bug-reporting mechanism.
  5. 5Follow the current Moodle Marketplace provider workflow to publish and maintain the listing; legacy Plugins Directory contribution guidance is not valid for new Marketplace submissions.

Key APIs & SDKs

Access API
Data manipulation API
File API
Privacy API
OAuth 2 API
Web services and External Services APIs

Authentication & security

  • Primary auth: Moodle plugin and integration authentication is implemented within the Moodle platform; the marketplace does not prescribe one universal authentication method for every listing.
  • Also supports: OAuth 2 for configuring and managing external systems, Moodle web-service tokens and enabled web-service protocols, subject to site and implementation configuration, LTI, SSO, or vendor-specific authentication for particular listings where supported
  • Security review: Not publicly specified
  • Not publicly specified for the current Moodle Marketplace. The marketplace exposes Moodle certification filters, but reviewed current sources do not publish a universal security-review policy or control checklist; legacy Plugins Directory review guidance is explicitly not current Marketplace guidance.
  • The current Marketplace invites providers to share free or paid plugins and links to a quick guide and provider documentation. The reviewed current sources do not expose the full submission workflow, acceptance criteria, review timing, security checks, or appeal process. Legacy Plugins Directory guidance describes upload, validation, approval, feedback, and release steps but expressly states that it is legacy and should not be used for new Marketplace submissions.
  • Not publicly specified. Moodle documents a Web Service and External Services framework, including standard and file-handling endpoints, but no universal marketplace or API rate limit was identified.

Monetization

Onboarding
Not publicly specified
Commission
Not publicly specified
Merchant of Record
Not publicly specified

Pros & cons for builders

Pros

  • Official Moodle ecosystem placement with direct discovery by administrators and institutions.
  • Supports free and paid listings with filters for version, category, price, and certification.
  • Broad plugin taxonomy and extensive developer/API documentation support native extensions and integration-oriented solutions.

Cons

  • The current Marketplace provider workflow and detailed policy requirements are not fully visible in reviewed public pages.
  • Marketplace-wide fees, commissions, payment settlement, merchant-of-record arrangements, and onboarding charges are not publicly specified.
  • Building robust extensions can require specialist Moodle/PHP knowledge and careful management of compatibility, privacy, testing, and external dependencies.

Frequently asked questions

How do I get my app approved on Moodle Marketplace?

The current Marketplace invites providers to share free or paid plugins and links to a quick guide and provider documentation. The reviewed current sources do not expose the full submission workflow, acceptance criteria, review timing, security checks, or appeal process. Legacy Plugins Directory guidance describes upload, validation, approval, feedback, and release steps but expressly states that it is legacy and should not be used for new Marketplace submissions.

What authentication does Moodle Marketplace use?

Moodle Marketplace apps primarily authenticate with Moodle plugin and integration authentication is implemented within the Moodle platform; the marketplace does not prescribe one universal authentication method for every listing., also supporting OAuth 2 for configuring and managing external systems, Moodle web-service tokens and enabled web-service protocols, subject to site and implementation configuration, LTI, SSO, or vendor-specific authentication for particular listings where supported.

How is Moodle Marketplace monetized?

Moodle Marketplace supports Free, Paid app. Typical commission: Not publicly specified. Onboarding fee: Not publicly specified.

Is a security review required to list on Moodle Marketplace?

Moodle Marketplace's public materials do not specify a universal security-review requirement. Not publicly specified for the current Moodle Marketplace. The marketplace exposes Moodle certification filters, but reviewed current sources do not publish a universal security-review policy or control checklist; legacy Plugins Directory review guidance is explicitly not current Marketplace guidance.