Unified.to expands LMS API
Unified.to expanded its LMS API to support activity objects (course completion) and content objects (videos, PDFs), enabling progress tracking and embedded training — a technical upgrade that matters for accessibility reporting and analytics. That API change makes it easier for platforms to surface completion and content‑level accessibility metadata to downstream systems.
Unified's February product update on March 3, 2026 announced the LMS API expansion that added Content and Activity objects to the platform. unified.to The Activity object was designed to normalize disparate LMS progress models by exposing completion flags, duration values and timestamped activity records for deterministic reconciliation. unified.to The Content data model explicitly includes a media array, duration_minutes, collection_ids, localizations and a raw field that surface per-item metadata for videos, PDFs and other assets. docs.unified.to Unified lists support for major LMS providers such as Canvas, Moodle, Coursera, D2L Brightspace, Google Classroom, LinkedIn Learning and SAP SuccessFactors, and the platform advertises “410+ integrations” across categories. docs.unified.to The platform executes real-time, pass-through reads without persisting customer data and regionalizes traffic to US/EU/AU, while objects without webhook support are handled via incremental polling. unified.to Documentation and API surfaces include writable/custom fields and unified metadata endpoints that enable attaching content‑level attributes (for example accessibility descriptors) to content objects and propagating them to downstream systems. unified.to Implementation guides and code examples for fetching course trees, content items and activity records were published in February 2026 (including a February 19, 2026 content-access guide) and accompany the progress-tracking guidance. unified.to
