Skip to content

Existing integrations

Several delivery and enrolment platforms already work with Cognassist out of the box. These are partner-built: the partner built the connection into Cognassist against the Public API, Cognassist did not ship them. If your provider already runs one of these systems, a learner's cognitive profile can appear alongside their records without you writing any code.

This page covers the partner connectors that exist today. If there is no packaged connector for your system, the common case for an on-premises FE management-information system (MIS), you do not need to wait for one: the same Public API powers a standard, self-serve integration. See Planning your integration to plan your own.

Partner-built integrations

If your provider already runs one of the platforms below, the connection is built for you. Every one follows the same shape: a learner is created and invited from inside the partner platform, completes the assessment in Cognassist, and their cognitive profile flows back into the record your staff already work in.

Partner Category What you get out of the box Their integration docs
OneFile Apprenticeship / WBL e-portfolio Live, two-way. Create and invite the learner from OneFile; the returned profile appears in the OneFile record. Matched on email; sync is poll-based. Cognassist integration guide
Bud Apprenticeship delivery Live, two-way. Cognassist's first delivery-platform integration (Bud Premium tier). Learner created and invited in Bud; result flows back to the Bud record. Cognassist assessments integration
OneAdvanced ePortfolio (Smart Assessor) Apprenticeship e-portfolio Live, two-way. Learner created and invited from the ePortfolio; results surface in the tutor's view. Owned by OneAdvanced, the same vendor as the ProSolution / ProMonitor MIS. developer.oneadvanced.io, account-gated
Aptem Apprenticeship delivery Live, partner-built. Same create, invite, and return flow into the Aptem learner record. Integrating with Cognassist

Each partner controls its own developer documentation, and most of it sits behind a request or an account, so a link above asking you to sign in or request access is expected, not a broken door. Cognassist did not author those docs, so treat the partner's own documentation as authoritative for their side. The join key that keeps the same person from being created twice is clientReference; where a partner reconciles against the paged learner list instead, that list matches on email. Both are defined once in Core concepts.