learnhive

LHxAPI · By request

LHxAPI: custom integrations for LearnHive communities

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

A clear path through the layers.

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.

Request ↓ Response ↑ (only allowed data)
01

1 · Your site or app

Where members use the integration, such as your LMS, website or the LearnHive app.

02

2 · Permission check

Checks who is asking, their role, and whether they're allowed to see this data.

03

3 · LHxAPI connector

Sends only the data needed for the agreed purpose. Nothing else.

4a · LearnHive data

Accounts, courses, groups and progress. The data stays in LearnHive.

4b · Other systems (optional)

Added only after a separate review.

LearnHive (WordPress) is the source of truth for accounts and permissions. Every request is checked.

02 / The capabilities

Eight parts of one connected experience.

Each capability area helps define the scope of a custom integration.

01

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.

02

Accounts & access

LH Identity

Recognize members across their journey while the authoritative account and source permissions determine who may see or do what.

03

People & conversation

LH Connect

Support profiles, groups, activity, relationships and messaging with visibility rules that distinguish public discussion from member-only spaces.

04

Discovery into practice

LH Learn

Connect learners with course discovery and selected account-linked progress so a learning journey can continue across useful experiences.

05

Knowledge in circulation

LH Content

Make editorial knowledge, media, selected events and member contributions easier to find while keeping review and publishing decisions visible.

06

Learning meets possibility

LH Opportunity

Present career and other opportunities alongside the learning and community context that helps members discover what might come next.

07

Selected systems together

LH Exchange

Route agreed information between experiences and selected systems through reviewed adapters, without granting blanket access to connected services.

08

Trust across every connection

LH Governance

Keep authorization, privacy, moderation, ownership and operational responsibilities in view from the first request through ongoing maintenance.

03 / Practical uses

Example integrations

These examples can be discussed and scoped for a requested project.

Talk through a use case
  • A

    Single sign-on with a school LMS

    Review how school accounts could access an agreed LearnHive community.

    Learning
  • B

    Course progress sync

    Share selected progress records between authorized learning systems.

    Community
  • C

    Embedding community feeds

    Show permitted community activity inside a school website or LMS.

    Discovery

04 / In practice

The LearnHive community is a working foundation.

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

Clear boundaries make useful connections trustworthy.

An integration plan covers access, operating responsibilities and recovery before systems are connected.

01

Check the source, every time

Validate permissions at the source, including direct access, search, media, notifications, reporting and caches.

02

Grant only what the use case needs

Agree a narrow purpose and least-privilege scope. Review credential handling, data minimization, privacy expectations and how access can be revoked.

03

Keep ownership and review visible

Agree data and content ownership, retention, contribution review, and how third-party terms affect the selected service.

04

Plan the real operating environment

Review hosting boundaries, administrators, monitoring, backups, recovery, geography, capacity and who is responsible for ongoing operations.

Bring us the use case

Start with a boundary. Build from there.

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.

Request an integration call

New Report

Close