Myabsorb Absorb LMS API

Name: Absorb LMS API
Brand: Absorb LMS API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentEducationLmsbearer13 EndpointsREST

For Agents

Manage Absorb LMS users, courses, enrollments, and departments through the Absorb REST API. Returns user, course, enrollment, and department records across 13 operations.

Install Jentic One Beta

Connect the Absorb LMS API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Absorb LMS API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Absorb LMS API.

Authenticate against an Absorb tenant to obtain an access token

List learners in the LMS and read individual user profiles

Create new learner accounts with role and department assignments

GET STARTED

Start building with Absorb LMS API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for Absorb LMS API, keeping it validated and agent-ready. The Absorb LMS API exposes the core resources for managing a corporate or institutional learning program: users, courses, enrollments, and departments. It supports authentication, listing and creating users, browsing the course catalog, enrolling learners in courses, and managing the department structure that organizes those learners. Together the 13 endpoints cover the day-to-day operations of an Absorb LMS tenant.

Use Cases

Patterns agents use Absorb LMS API for, with concrete tasks.

★ New Hire Onboarding Automation

Automatically create an Absorb learner record and enroll the new hire in the required onboarding courses on day one. The integration calls POST /users to create the account, then POST /enrollments for each required course. This collapses an HR onboarding step that L&D teams traditionally handle manually for every new starter.

On a new hire event, call POST /users to provision the learner, then POST /enrollments for each course in the onboarding bundle and confirm each enrollment was created.

Compliance Training Tracking

Track which employees have completed mandatory compliance courses and surface gaps to managers. The integration lists enrollments via GET /enrollments filtered to compliance courses, joins the results to /users to read department, and outputs a completion report. This replaces manual spreadsheet tracking that compliance teams maintain alongside the LMS.

Page through GET /enrollments for the compliance course IDs, group by department from /users, and emit a list of incomplete learners per department.

Department Restructure Sync

Reflect a corporate org-structure change in Absorb so reporting and assignment rules continue to map correctly. POST /departments creates the new units; GET /users plus PUT /users/{userId} reassigns affected learners. Doing this through the API keeps Absorb in sync with the system of record without admin clicks per user.

Create new departments via POST /departments, then for each affected user PUT /users/{userId} with the new departmentId.

Course Catalog Surface

Surface the Absorb course catalog in an internal portal or chat tool so employees can browse and self-enroll without logging into the LMS. GET /courses returns the catalog; GET /courses/{courseId} returns detail; POST /enrollments enrolls the requesting user. This pattern improves discoverability for L&D content that often gets ignored in the LMS UI.

Render results from GET /courses in an internal portal; on click, call POST /enrollments with the user ID and courseId to self-enroll.

AI Agent Learning Assistant

Equip a Jentic-driven assistant that recommends and enrolls employees in Absorb courses based on a development conversation. The agent searches Jentic for 'enroll a learner in an Absorb course', loads POST /enrollments, and creates the enrollment. Jentic injects the bearer token at execution time so the agent never sees the LMS credential.

Through Jentic, search for 'enroll a learner in a course', load POST /enrollments, and submit the user and course identified during the development conversation.

Key Endpoints

13 endpoints — jentic publishes the only available openapi specification for absorb lms api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/authenticate

Authenticate and obtain a token

GET

/users

List users

POST

/users

Create a user

PUT

/users/{userId}

Update a user

GET

/courses

List courses

GET

/enrollments

List enrollments

POST

/enrollments

Create an enrollment

GET

/departments

List departments

POST

/authenticate

Authenticate and obtain a token

GET

/users

List users

POST

/users

Create a user

PUT

/users/{userId}

Update a user

GET

/courses

List courses

GET

/enrollments

List enrollments

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Absorb tenant credentials and the bearer tokens issued from /authenticate are stored encrypted in the Jentic vault. Tokens are refreshed automatically and applied at execution time, so agents never see raw LMS credentials.

Intent-based discovery

Agents search Jentic with intents like 'enroll a learner' or 'list courses' and Jentic returns the matching Absorb operation with its input schema, so the agent can call it without browsing Absorb's docs portal.

Time to first call

Direct integration including authenticate-and-refresh handling and pagination typically takes 1-2 days. Through Jentic the search, load, execute flow runs in under an hour.

FAQs

Specific to using Absorb LMS API through Jentic.

Why is there no official OpenAPI spec for Absorb LMS API?

Absorb LMS does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Absorb LMS API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Absorb LMS API use?

Absorb uses HTTP bearer authentication. Clients first call POST /authenticate with tenant credentials to obtain a token, then send it on subsequent requests. Through Jentic, the credentials and token rotation are handled in the Jentic vault, so agents never hold raw secrets.

Can I enroll learners with the Absorb LMS API?

Yes. POST /enrollments creates an enrollment for a user in a specific course. Use GET /enrollments to verify the enrollment was created and read its progress.

How do I list users through Jentic?

Through Jentic, search for 'list Absorb learners', load GET /users, and call it with optional filters. Jentic forwards the bearer token from its vault and returns the user list to your agent.

What are the rate limits for the Absorb LMS API?

Rate limits are not declared in the OpenAPI spec. Absorb enforces tenant-level limits at the gateway; respect 429 responses and the Retry-After header when running bulk syncs.

Can I create departments via the Absorb LMS API?

Yes. POST /departments creates a new department, and GET /departments lists existing departments. Use PUT /users/{userId} to reassign learners as the org structure changes.

Myabsorb Absorb LMS API

Connect the Absorb LMS API to your agent

Capabilities

Start building with Absorb LMS API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs