API Development for UK EdTech — ICO AADC Built In

LTI 1.3 Integration — EdTech Interoperability Standard

LTI 1.3 (Learning Tools Interoperability): IMS Global standard for connecting external tools to LMS platforms. LTI 1.3 launch flow: (1) LMS (Canvas, Moodle, Blackboard, D2L) creates LTI 1.3 launch JWT, (2) tool verifies JWT signature (LMS public key via JWKS endpoint), (3) tool receives learner context (user ID, course ID, role, locale), (4) tool grants access based on LTI claims (no separate login required). LTI Advantage extensions: Assignment and Grade Services (LTI AGS — tool writes scores back to LMS gradebook), Deep Linking (tool returns content URL to LMS), Names and Role Provisioning (NRPS — tool queries course roster). UK EdTech LTI: ClickMasters has built LTI 1.3 integrations for Canvas (Russell Group universities), Moodle (FE colleges), and D2L Brightspace (further education trusts).

xAPI (Tin Can) — Learning Analytics API

xAPI (Experience API, also known as Tin Can): standard for recording learning experiences (statements). xAPI statement: actor (learner) + verb (completed, passed, failed, experienced) + object (learning activity ID). LRS (Learning Record Store): stores xAPI statements. UK EdTech xAPI use cases: (1) simulation-based assessment (flight simulators, medical training simulators send xAPI statements to LRS), (2) mobile learning (offline learning — statements queued locally, sent to LRS on reconnect), (3) learning analytics (LRS data → data warehouse → visualisations for educators). GDPR Article 9: xAPI statements about learner performance are personal data — explicit consent required for under-18 learners (AADC). xAPI statements pseudonymised by default in ClickMasters EdTech platforms (actor.mbox = hashed email — not raw email).

DfE Data Standards for Schools API Integration

DfE (Department for Education) data standards: (1) UPN (Unique Pupil Number — permanent pupil identifier across all schools in England), (2) CBDS (Common Basic Data Set — DfE standard data fields for pupil records), (3) CTF (Common Transfer File — XML format for pupil data transfer between schools), (4) School Census (Termly data submission to DfE — pupil numbers, characteristics, attendance, exclusions). API integration: ClickMasters EdTech platforms implement UPN as primary learner identifier (not email — email changes, UPN does not), CTF import for new pupil intake, and automated DfE School Census data extract. ICO AADC: UPN is a unique identifier for under-18 learners — classified as personal data, special handling required.

SCORM to xAPI Migration for UK EdTech

SCORM (Sharable Content Object Reference Model): legacy e-learning standard (SCORM 1.2 and 2004) — still widely deployed in UK FE and HE. SCORM limitations: browser-based (cannot track offline learning), limited data (completion, score, time spent), and requires LMS. xAPI advantages: any environment (mobile, simulation, games), rich data (verb + object + extensions), LRS stores data independently of LMS. Migration approach: (1) SCORM content package → Articulate Storyline re-publish to xAPI (most SCORM content was built in Storyline or Lectora — one-click re-publish), (2) LRS deployment (SCORM Cloud LRS or open-source LRS — Learning Locker), (3) xAPI data → analytics pipeline (LRS API → S3 → dbt → analytics dashboard). Timeline: SCORM to xAPI migration for 200-course library: 4–8 weeks.

ICO AADC

UK GDPR

DfE standards

Ofqual

LTI 1.3

SCORM

xAPI (Tin Can)