Build · developer platformLive

A Learning Record Store that passes every test.

Our xAPI 2.0 (IEEE 9274.1.1) Learning Record Store passes 1,435 / 1,435 checks of the open ADL Conformance Test Suite. Statements, documents, signed data, and queries behave exactly as the spec demands — so content and tools from any vendor read and write cleanly. Most LRSs claim xAPI support; we publish the test run.

2.0-native Accepts xAPI 1.0.0–1.0.3 Reproduce it yourself
1435/1435  100%
ADL LRS Conformance Suite · v2_0
Spec
IEEE 9274.1.1
Result
0 failing
Suite commit
5bc232d
Run date
2026-06-06
1435/1435
ADL suite checks passing
xAPI 2.0
IEEE 9274.1.1
v2_0 @ 5bc232d
Suite version · dated run
1.0.01.0.3
Legacy clients still accepted
NEW TO THIS? START HERE

What's a Learning Record Store?

An LRSis the system of record for learning activity — a database that stores every “who did what” event as a structured xAPI statement (“Maria completed Fire Safety, scored 92%”). Conformance means we implement that standard completely, so data written by one tool is read correctly by another. When an LRS is only partlyconformant, that’s where integrations quietly break — a signature that won’t validate, a query that returns the wrong set. Passing all 1,435 checks is how you know it won’t.

WHAT IT DOES

Everything the spec asks for — and the edges that usually break.

Statements API

Store, void, and query statements with full filter and paging semantics — verbs, objects, results, and 2.0 context agents/groups.

Document resources

State, Activity Profile, and Agent Profile documents with correct merge, list, and delete behaviour.

Signed statements (JWS)

Validates JWS signature attachments and X.509 certificates so tamper-evident records verify correctly.

Attachments

multipart/mixed transport with SHA-2 integrity hashing and fetch-on-request — large evidence handled cleanly.

Document concurrency

ETag generation with If-Match / If-None-Match preconditions, so concurrent writers never clobber each other.

2.0-native context

contextAgents and contextGroups, ISO 8601 precision, and version negotiation built in from the start.

THE PROOF — NOT A BADGE

We publish the actual test run.

xAPI has no certifying authority — IEEE owns the standard, ADL provides one open suite every LRS runs against itself. That's the industry standard, and it's how the whole field proves conformance. We run all 1,435 checks, pass every one, and publish the results, the suite commit, and the method so you can run it against our live endpoint yourself.

1435/1435
100%
Suite
ADL v2_0 @ 5bc232d
Verified
2026-06-06
Spec
IEEE 9274.1.1
Failing
0
FOR THE TECHNICAL BUYER

Point your content at the endpoint.

A standard xAPI 2.0 endpoint with Basic and OAuth auth, version negotiation, and the full Statement, State, Activity Profile, Agent Profile, Activities, Agents, and About resources. Map the Basic password to a Connect API key and you’re writing statements.

  • Endpoint: /api/lrs/xapi · Basic & OAuth · scoped authority
  • X-Experience-API-Version negotiation on every request
  • Statements mirror in from SCORM dispatch & the hosted player
  • Reproduce conformance against the live prod endpoint
REPRODUCE THE RUN
# open ADL suite → live endpoint
git clone github.com/adlnet/\
  lrs-conformance-test-suite

LRS_ENDPOINT=https://www.\
  allureconnect.com/api/lrs/xapi \
node bin/console_runner.js \
  -e "$LRS_ENDPOINT" -a -x 2.0.0

  1435 passing (100%)
     0 failing
See the full methodology

Point your xAPI content at a conformant LRS.

Get a sandbox endpoint in 30 seconds, send real statements, then run the suite against us yourself.

Get a sandbox keySee the full test results