Skip to main content
Developer documentation

Build against the contracts Connect ships today.

Follow the account-to-launch quick start, then use the interactive OpenAPI UI and machine-readable contracts to verify exact methods, payloads, and response shapes.

Start here

  • Quick start

    Get up and running in minutes with the getting-started path: account, package, session, and reports.

  • Interactive API reference

    OpenAPI 3.1 API explorer — review endpoints, filters, and schemas in the browser.

  • Code examples

    Ready-to-use samples and patterns for common integrations.

Suggested order: Quick start → architecture → your integration path (LMS, dispatch, or WordPress) → security → webhooks. Narrative docs explain behavior and edge cases; OpenAPI and contract routes describe the exact surface area.

Browse by job to be done

Every published guide is listed once. Start with the workflow you need, then validate the final request in OpenAPI.

All 31 guides

31 of 31 guides

Machine-readable contracts

Product updates

  • v2026.10.1 · · Fixed

    If you belong to several workspaces and switch workspace in one browser tab, your other open tabs now say so and ask you to reload or switch back. A change submitted from a tab that still shows the previous workspace is refused, with nothing saved. A bulk dispatch action now changes every dispatch you selected or none. Reading pages is not affected, and neither are API keys, xAPI credentials or learner launch links.

  • v2026.10.1 · · Added

    A reviewer can now say how the skill is demonstrated and how much it demands. The highest level a score can prove is worked out from those answers. Content with nothing set is scored as before. API: demandRatings, demonstrationMode, passMarkScaled; GET /api/v1/capability/evidence-framework, PUT /api/v1/capability/mappings/{mappingId}/evidence-attributes.

  • v2026.10.0 · · Changed

    Uploading a course, the SCORM validator, Quick Publish, test launches, opening a learner session from the Player page and recording a VR outcome are now for workspace owners and admins. Other roles still see courses, delivery and reports. With several workspaces, these work in your active workspace only. API keys and learner launch links are not affected.

Ready to build?

Ready to build?

Get your workspace and API keys, then upload packages and validate launches end to end.