Member-facing journeys
LH Experience
Bring selected community, learning and opportunity services into a coherent branded experience, with web journeys shaped around the people using them.
LHxAPI · By request
Available by request. No public endpoints yet.
LHxAPI is our name for this integration layer. It is not the Experience API (xAPI) standard.
01 / Conceptual architecture
This conceptual model shows how a request is checked against identity and source authorization before Exchange routes it. A response returns only what that source permits.
Where members use the integration, such as your LMS, website or the LearnHive app.
Checks who is asking, their role, and whether they're allowed to see this data.
Sends only the data needed for the agreed purpose. Nothing else.
Accounts, courses, groups and progress. The data stays in LearnHive.
Added only after a separate review.
LearnHive (WordPress) is the source of truth for accounts and permissions. Every request is checked.
02 / The capabilities
Each capability area helps define the scope of a custom integration.
Member-facing journeys
Bring selected community, learning and opportunity services into a coherent branded experience, with web journeys shaped around the people using them.
Accounts & access
Recognize members across their journey while the authoritative account and source permissions determine who may see or do what.
People & conversation
Support profiles, groups, activity, relationships and messaging with visibility rules that distinguish public discussion from member-only spaces.
Discovery into practice
Connect learners with course discovery and selected account-linked progress so a learning journey can continue across useful experiences.
Knowledge in circulation
Make editorial knowledge, media, selected events and member contributions easier to find while keeping review and publishing decisions visible.
Learning meets possibility
Present career and other opportunities alongside the learning and community context that helps members discover what might come next.
Selected systems together
Route agreed information between experiences and selected systems through reviewed adapters, without granting blanket access to connected services.
Trust across every connection
Keep authorization, privacy, moderation, ownership and operational responsibilities in view from the first request through ongoing maintenance.
03 / Practical uses
These examples can be discussed and scoped for a requested project.
Talk through a use caseReview how school accounts could access an agreed LearnHive community.
Share selected progress records between authorized learning systems.
Show permitted community activity inside a school website or LMS.
04 / In practice
LearnHive is a volunteer-run learning community where CMS hosting, member participation and selected learning experiences illustrate how these foundations can work together. Each organization’s configuration and services are scoped separately.
Organizations can begin with a focused experience and make scope explicit: which source owns the information, what a member may access, who reviews contributions and who operates each connected service.
05 / Responsible deployment
An integration plan covers access, operating responsibilities and recovery before systems are connected.
Validate permissions at the source, including direct access, search, media, notifications, reporting and caches.
Agree a narrow purpose and least-privilege scope. Review credential handling, data minimization, privacy expectations and how access can be revoked.
Agree data and content ownership, retention, contribution review, and how third-party terms affect the selected service.
Review hosting boundaries, administrators, monitoring, backups, recovery, geography, capacity and who is responsible for ongoing operations.
Bring us the use case
Tell us who the experience serves, which sources matter and what must stay private. We can talk through what is already a foundation and what would need review or implementation.