Grow LMS API Documentation
Grow by Plenum — Community & Social Learning
An optional engagement layer — discussion spaces alongside your training — and how to read it programmatically.
Beyond formal courses, Grow includes a community capability: discussion spaces where learners can post, comment, and interact. It’s optional — most compliance programs don’t require it — but where peer discussion or a Q&A space adds value, this document covers the structures involved and how to access them through the API.
Every call uses the Pl-Client header and Authorization: Bearer <ACCESS_TOKEN> from Authentication & Access Setup. <SCHOOL_ID> is your environment.
1. The building blocks
| Structure | What it is |
|---|---|
| Space | A discussion area. Access can be public, private, or standalone. A space can be attached to a course/unit or stand on its own. |
| Post | A message within a space or a course, by an author, with text, user mentions, and likes. |
| Collection | A named grouping of spaces, with a display_order, used to organize the community sidebar. |
2. Spaces
A CommunitySpace carries id, title, description, an access level (public / private / standalone), an owner (the creator), and usages describing where the space is surfaced (e.g. attached to a particular courseId / unitId). You can list spaces, read a single space, and retrieve its members — useful for reporting on who participates in which discussion area.
3. Posts
A CommunityPost carries id, a posted_in reference (whether it was made in a space or a course, and which one), the author user, the text, plus mentions and likes. Pulling posts lets you measure engagement (volume, participation) or surface activity into your own dashboards.
4. Collections
A CommunityCollection (id, name, description, display_order, space_ids, created, modified) groups spaces together for navigation. It’s the organizational layer above individual spaces.
5. How to think about it for a compliance program
- Optional, not core. None of your completion, certification, or audit data depends on community. Treat it as an engagement add-on.
- Engagement signal. Where you do use it, community activity (posts, participation) is a soft signal of how engaged a cohort is — pullable into the same reporting as everything else.
- Governance. Spaces have access levels (
public/private), so participation can be scoped; membership is queryable for oversight.
If community isn’t part of your program, you can ignore this document entirely — nothing else in the integration depends on it.
6. Where to go next
- Pull-Based Data Access — the general pattern for retrieving and paginating these records.
- Provisioning & Workforce Management — the groups and tags that can mirror community membership.
Prepared by Plenum Solutions for your evaluation. “Grow by Plenum” is operated and supported by Plenum on your behalf. Exact endpoint paths are confirmed for your environment during onboarding. For integration design support, contact your Plenum engagement lead.
