Developer platform

Integrations

Connect SIS, LMS, payment gateways, and identity providers.

Developer portal Marketplace story
APIOpen integration surface
WebhooksEvent-driven automations
SandboxPreview before publish

Build loop

Design app -> test in sandbox -> submit for review -> install through governed marketplace.

SDK Webhooks Governed review

LTI 1.3

LTI launch and deep linking; readiness at /api/interop/lti13/.

OneRoster

OneRoster API and CSV; readiness at /api/interop/oneroster/.

Ed-Fi & CEDS

Ed-Fi and CEDS endpoints for student and grade data.

Why this matters for the platform story

  • Developer enablement is part of platform seriousness, not an afterthought.
  • Apps, integrations, and custom extensions should feel curated and safe, not bolted on.
  • Sandbox and governance turn experimentation into something schools can trust.

Conversion path

If you are building on RunMyCampus, you need a credible story around APIs, webhooks, marketplace review, and preview-before-commit. This page is designed to make that story visible.