[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Absorb LMS API and MCP server

> Absorb LMS has an Integration API, a REST API with JSON for learners, courses, departments and grades, but it needs a private key tied to your portal that your Absorb account team provides, and your own code (checked 20 Oct 2026). Absorb's Aura MCP for Claude and ChatGPT is planned for 27 Oct 2026 and is read and answer only.

Learning management system for companies: an Admin Experience with Users, Courses and Reports, and a Learner Experience with a Catalog and My Courses.

## What is the Absorb LMS API?

Cotlet's Absorb LMS API exposes 14 endpoints for your own Absorb LMS account: list users, list courses, list course enrollments, list user enrollments, list course activity, list course approval requests, list certificates, approve enrollment requests, decline enrollment requests, enroll users, unenroll user, message users, create user and set user status. The list_users endpoint returns users of the portal with department, roles and status, from the Users report. Each endpoint takes simple JSON inputs like course_id, department or status and works both as an operation of the absorb_lms_read or absorb_lms_write MCP tool for agents and as a REST call for scripts.

- **Category:** [Courses & training](https://cotlet.dev/integrations/category/courses-training.md)
- **Endpoints:** 14 (7 read, 7 write)
- **Updated:** 2026-10-18

Absorb LMS has an Integration API, a REST API with JSON for learners, courses, departments and grades, but it needs a private key tied to your portal that your Absorb account team provides, and your own code (checked 20 Oct 2026). Cotlet is a hosted MCP server and REST API for Absorb LMS with 14 endpoints (7 read, 7 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does Absorb LMS have an official API?

Absorb LMS has an Integration API, a REST API with JSON for learners, courses, departments and grades, but it needs a private key tied to your portal that your Absorb account team provides, and your own code (checked 20 Oct 2026). Absorb's Aura MCP for Claude and ChatGPT is planned for 27 Oct 2026 and is read and answer only.

| Task | Absorb LMS official | Cotlet |
|---|---|---|
| List users with department and status | Partly: Integration API with a private key; Aura MCP answers admin questions only | Yes |
| Enrollments and progress per course or user | Partly: Integration API with a private key; Aura MCP answers questions only | Yes |
| Overdue learners in an Online Course | Partly: Answers from Aura MCP, no list to act on | Yes |
| Approve or decline enrollment requests | No: The Aura MCP cannot act; the Integration API is not documented publicly for approvals | Yes |
| Enroll users in a course | Partly: Integration API with a private key and your own code | Yes |
| Message selected learners | No: The Aura MCP cannot act; messages are sent from the Admin Experience | Yes |
| Create users with roles | Partly: Integration API with a private key and your own code | Yes |
| Activate or deactivate users | Partly: Integration API with a private key and your own code | Yes |

Sources: [Absorb Help: October 2026 Aura Release, Connect Aura with Claude and ChatGPT](https://support.absorblms.com/hc/en-us/articles/55635088123667-October-2026-Aura-Release-Connect-Aura-with-Claude-and-ChatGPT), [Absorb Help: Getting Started with the Absorb Integration API](https://support.absorblms.com/hc/en-us/articles/222482188-Getting-Started-with-the-Absorb-Integration-API), [Absorb API Documentation](https://docs.myabsorb.com/)

## For AI agents

```text
Absorb LMS has an Integration API, a REST API with JSON for learners, courses, departments and grades, but it needs a private key tied to your portal that your Absorb account team provides, and your own code (checked 20 Oct 2026). Absorb's Aura MCP for Claude and ChatGPT is planned for 27 Oct 2026 and is read and answer only.
Cotlet provides a hosted MCP server and REST API for Absorb LMS: 14 tools (7 read, 7 write).
Access       Sign up at https://cotlet.dev/app/signup?app=absorb-lms, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    absorb_lms_read, absorb_lms_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/absorb-lms, each operation at its own route, e.g. POST /api/v1/absorb-lms/users
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one. Over MCP the input schemas come with sign-in.
Operations   list_users, list_courses, list_course_enrollments, list_user_enrollments, list_course_activity, list_course_approvals, list_certificates, approve_enrollment_requests, decline_enrollment_requests, enroll_users, unenroll_user, message_users, create_user, set_user_status
Confirm      approve_enrollment_requests, decline_enrollment_requests, enroll_users, unenroll_user, message_users, create_user, set_user_status (by default the user approves each call; the user can switch this off per tool, e.g. for scheduled automations)
Markdown     https://cotlet.dev/integrations/absorb-lms-api-mcp-server.md

How access works:
1. The user signs up at https://cotlet.dev/app/signup?app=absorb-lms, requests Absorb LMS in the Cotlet console and creates an API key there.
2. The user signs in to Absorb LMS once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables Absorb LMS for agents. An agent cannot do this step.
3. The API key goes into the MCP client or the REST call as a bearer token.

Fits: people who want a hosted Absorb LMS server that someone else maintains, including non-developers.

Policy: Cotlet never stores passwords, never solves CAPTCHAs, never bypasses MFA.
Company: legal details in the Terms of service at https://cotlet.dev/terms. Contact contact@cotlet.dev.
Sign-in: the user signs in to Absorb LMS in their own Cloud Browser, a Chrome Cotlet runs for them in the EU; password saving is off, the profile is AES-256-GCM encrypted, and agents get Absorb LMS only after the user enables it. Calls are requests from that browser's IP with its cookies, each listed in the user's Background activity. Disable for agents, signing out in the browser or Reset browser cuts access. Cotlet is run by Take Group sp. z o.o. (EU VAT PL6342984273).
API key: holds no Absorb LMS login or cookies, only asks Cotlet to run a tool. Each key is scoped to chosen apps and tools, read only or read and write. Actions that reach other people wait for the user's approval by default, so a leaked key cannot post or message as the user. Every call is in the activity log; deleting the key ends access at once.
Terms: the user stays responsible for following Absorb LMS's terms; Cotlet is not affiliated with Absorb LMS.
```

## What can an AI agent do in Absorb LMS?

Cotlet is best for Absorb LMS admins who run enrollments, approvals and reminders by hand and want an AI agent to do them without running or fixing a server.

- **[Approve course enrollment requests](https://cotlet.dev/integrations/absorb-lms-api-mcp-server/approve-course-enrollment-requests.md)** (runs: daily): "Go through the pending course approvals. Approve Finance requests for Data Privacy Essentials, decline requests from inactive users, and leave the rest for me with a one-line reason." → `list_course_approvals`, `approve_enrollment_requests`, `decline_enrollment_requests`
- **[Chase overdue training](https://cotlet.dev/integrations/absorb-lms-api-mcp-server/chase-overdue-training.md)** (runs: weekly): "Every Monday, find learners in Warehouse Safety Basics who are overdue and not finished, and message them that it is due. Show me the list first." → `list_courses`, `list_course_activity`, `message_users`
- **[Enroll new hires in onboarding courses](https://cotlet.dev/integrations/absorb-lms-api-mcp-server/enroll-new-hires-in-onboarding.md)** (runs: weekly): "Find users created this week in the Warehouse department and enroll the ones missing Warehouse Safety Basics." → `list_users`, `list_user_enrollments`, `enroll_users`
- **Weekly completions and certificates report** (runs: weekly): "Every Friday, tell me who completed Warehouse Safety Basics this week and which certificates were awarded." → `list_course_enrollments`, `list_certificates`
- **Deactivate leavers**: "Deactivate the users on this list of leavers and tell me which ones were not found." → `list_users`, `set_user_status`

## Can Absorb LMS automations run on a schedule in n8n, Make or Zapier?

Yes. Cotlet does not replace your automation platform: it gives it a Absorb LMS connection it does not have, with the same API key as your agent. Write actions ask for your OK by default; switch that off in your dashboard for the tools you choose, for example to approve course enrollment requests, and the schedule runs on its own. Cotlet runs in the cloud, so it keeps going while your computer is off.

| Where | How to connect | How to schedule |
|---|---|---|
| Your AI agent | Add https://cotlet.dev/mcp/v1 with your API key. | A scheduled agent run, for example a Claude Code routine. |
| n8n | MCP Client node with https://cotlet.dev/mcp/v1, or an HTTP Request node with the endpoint's method and URL, such as GET https://cotlet.dev/api/v1/absorb-lms/course-approvals. | Schedule Trigger node. |
| Make | HTTP module: the endpoint's method and URL with an Authorization: Bearer header, and a JSON body for POST, PUT and PATCH. | Scenario schedule. |
| Zapier | Webhooks by Zapier, Custom Request: the same method, URL, header and body. | Schedule by Zapier trigger. |
| Your own script | GET https://cotlet.dev/api/v1/absorb-lms/course-approvals with your API key. | cron or GitHub Actions. |

## Tools

**For AI agents:** Every endpoint and its schema is public. The 14 endpoints on this page, with parameters and example responses, can be listed without an account. Calling one returns 401 without an API key and 403 while the key has no access to Absorb LMS.

### list_users

Users of the portal with department, roles and status, from the Users report. Access: read. REST: `GET /api/v1/absorb-lms/users`. MCP: `absorb_lms_read → list_users`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `query` | string | no | Part of a name, username or email. |
| `department` | string | no | Department name as shown in the profile. |
| `status` | enum | no | active (default) or inactive. |
| `limit` | integer | no | Rows to return. |

Returns users the way the Users report (User Administration) shows them. Only Active users appear unless you pass status inactive, as in Absorb's default view. Search by name, username or email, and narrow by department. user_id goes into list_user_enrollments, enroll_users, message_users and set_user_status. You see only the users your Admin role allows.

Example response:

```json
{
  "users": [
    {
      "user_id": "4f1c2a7e-8b3d-4c1a-9e55-0a6d3b7c1201",
      "name": "Dana Reyes",
      "username": "dreyes",
      "email": "dana.reyes@example.com",
      "department": "Warehouse",
      "roles": [
        "Learner"
      ],
      "status": "Active"
    },
    {
      "user_id": "9b7e5d10-2c44-4f0b-8a31-6e2f9c4d7702",
      "name": "Omar Haddad",
      "username": "ohaddad",
      "email": "omar.haddad@example.com",
      "department": "Warehouse",
      "roles": [
        "Learner"
      ],
      "status": "Active"
    }
  ]
}
```

### list_courses

Online Courses, Instructor Led Courses, Curricula and Course Bundles from the Courses report. Access: read. REST: `GET /api/v1/absorb-lms/courses`. MCP: `absorb_lms_read → list_courses`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `query` | string | no | Part of the course title. |
| `type` | enum | no | online_course, instructor_led_course, curriculum or course_bundle. |
| `status` | enum | no | active (default) or inactive. |
| `limit` | integer | no | Rows to return. |

Returns training the way the Courses report lists it, with its Course ID (a GUID), type and status. Filter by type and by Active or Inactive. course_id goes into list_course_enrollments, list_course_activity and enroll_users. Inactive courses are hidden from learners but keep their enrollment records.

Example response:

```json
{
  "courses": [
    {
      "course_id": "c2d6a1f4-5b8e-4a37-9d02-7f1e3c5b8a10",
      "title": "Warehouse Safety Basics",
      "type": "Online Course",
      "status": "Active"
    },
    {
      "course_id": "e8b3c7d9-1a52-4f6e-b0c4-2d9a6e1f3b21",
      "title": "Onboarding Path",
      "type": "Curriculum",
      "status": "Active"
    }
  ]
}
```

### list_course_enrollments

Who is enrolled in one course, with progress, status, due date and enrollment method. Access: read. REST: `GET /api/v1/absorb-lms/course-enrollments`. MCP: `absorb_lms_read → list_course_enrollments`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `course_id` | string | yes | Course ID from list_courses. |
| `completion` | enum | no | not_started, in_progress or completed. |
| `department` | string | no | Department name as shown in the profile. |

Returns the Course Enrollments report for one course: Absorb returns active users and active training only. Each row has % (Progress), the course status of the learner, Date Enrolled, Due Date, Days until due and the Enrollment Method (Admin, Automatic and others). Filter by completion or department. Absorb groups large changes and processes them at 10 minute intervals, so a fresh enrollment can take a few minutes to show.

Example response:

```json
{
  "course": "Warehouse Safety Basics",
  "enrollments": [
    {
      "user_id": "4f1c2a7e-8b3d-4c1a-9e55-0a6d3b7c1201",
      "name": "Dana Reyes",
      "department": "Warehouse",
      "status": "In Progress",
      "progress_percent": 80,
      "date_enrolled": "2026-10-05",
      "due_date": "2026-10-19",
      "enrollment_method": "Admin"
    },
    {
      "user_id": "9b7e5d10-2c44-4f0b-8a31-6e2f9c4d7702",
      "name": "Omar Haddad",
      "department": "Warehouse",
      "status": "Not Started",
      "progress_percent": 0,
      "date_enrolled": "2026-10-05",
      "due_date": "2026-10-19",
      "enrollment_method": "Automatic"
    }
  ]
}
```

### list_user_enrollments

Every course one user is enrolled in, from the User Enrollments report. Access: read. REST: `GET /api/v1/absorb-lms/user-enrollments`. MCP: `absorb_lms_read → list_user_enrollments`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `user_id` | string | yes | User ID from list_users. |
| `include_history` | boolean | no | Add historic enrollments. Default: false. |

Returns the User Enrollments report for one user: course, progress, status, dates and enrollment method. Use it before enroll_users to skip courses a person already has, and before unenroll_user to see what the enrollment holds. include_history adds historic enrollments.

Example response:

```json
{
  "user": "Dana Reyes",
  "enrollments": [
    {
      "course_id": "c2d6a1f4-5b8e-4a37-9d02-7f1e3c5b8a10",
      "course": "Warehouse Safety Basics",
      "status": "In Progress",
      "progress_percent": 80,
      "date_enrolled": "2026-10-05",
      "enrollment_method": "Admin"
    },
    {
      "course_id": "e8b3c7d9-1a52-4f6e-b0c4-2d9a6e1f3b21",
      "course": "Onboarding Path",
      "status": "Completed",
      "progress_percent": 100,
      "date_enrolled": "2026-09-02",
      "enrollment_method": "Automatic"
    }
  ]
}
```

### list_course_activity

Progress of learners in one Online Course, with certificate and overdue flags, from the Course Activity report. Access: read. REST: `GET /api/v1/absorb-lms/course-activities`. MCP: `absorb_lms_read → list_course_activity`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `course_id` | string | yes | Course ID of an Online Course from list_courses. |
| `completion` | enum | no | not_started, in_progress or completed. |
| `overdue` | boolean | no | true returns only enrollments past their due date. |

Returns the Course Activity report for one Active Online Course, all enrollments whatever their status: progress, number of times accessed, Attained Certificate, Certificate Date, Due Date and Overdue. Overdue is true when the Due Date has passed, whatever the completion status, so pair overdue with completion not_started or in_progress to list who still owes the course. Instructor Led Courses and Curricula are not in this report.

Example response:

```json
{
  "course": "Warehouse Safety Basics",
  "rows": [
    {
      "user_id": "9b7e5d10-2c44-4f0b-8a31-6e2f9c4d7702",
      "name": "Omar Haddad",
      "department": "Warehouse",
      "completion": "Not Started",
      "progress_percent": 0,
      "due_date": "2026-10-19",
      "overdue": true,
      "attained_certificate": false
    },
    {
      "user_id": "4f1c2a7e-8b3d-4c1a-9e55-0a6d3b7c1201",
      "name": "Dana Reyes",
      "department": "Warehouse",
      "completion": "In Progress",
      "progress_percent": 80,
      "due_date": "2026-10-19",
      "overdue": true,
      "attained_certificate": false
    }
  ]
}
```

### list_course_approvals

Pending enrollment requests waiting for approval, from the Course Approvals report. Access: read. REST: `GET /api/v1/absorb-lms/course-approvals`. MCP: `absorb_lms_read → list_course_approvals`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `type` | enum | no | online_course, instructor_led_course or curriculum. |
| `department` | string | no | Department name as shown in the profile. |

Returns the Course Approvals report: enrollment requests from learners who self-enrolled in a course that needs approval. Each row has request_id, learner, department, course title and type (Online Course, Instructor Led Course or Curriculum). The report includes active and inactive users, so check the status column. You see only the rows your Admin permissions allow. Pass request_id to approve_enrollment_requests or decline_enrollment_requests.

Example response:

```json
{
  "requests": [
    {
      "request_id": "a41f8c2d-6e07-4b93-8d15-3c7e9a2b5f01",
      "learner": "Priya Nair",
      "user_status": "Active",
      "department": "Finance",
      "course": "Data Privacy Essentials",
      "type": "Online Course"
    },
    {
      "request_id": "b52a9d3e-7f18-4ca4-9e26-4d8f0b3c6a12",
      "learner": "Luis Ortega",
      "user_status": "Active",
      "department": "Warehouse",
      "course": "Data Privacy Essentials",
      "type": "Online Course"
    },
    {
      "request_id": "c63b0e4f-8029-4db5-8f37-5e901c4d7b23",
      "learner": "Chen Wei",
      "user_status": "Inactive",
      "department": "Finance",
      "course": "Data Privacy Essentials",
      "type": "Online Course"
    }
  ]
}
```

### list_certificates

Certificates awarded on course completion, from the Certificates report. Access: read. REST: `GET /api/v1/absorb-lms/certificates`. MCP: `absorb_lms_read → list_certificates`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `course_id` | string | no | Only certificates of this course. |
| `certified_since` | date | no | Only certificates awarded on or after this date. |

Returns the Certificates report: course, learner, Certification Date and Certificate Issuer (the admin who awarded it by hand, if any). The report includes active and inactive users and only users inside your permission scope. Filter by course or by date.

Example response:

```json
{
  "certificates": [
    {
      "learner": "Dana Reyes",
      "course": "Onboarding Path",
      "certification_date": "2026-10-09",
      "issuer": ""
    },
    {
      "learner": "Omar Haddad",
      "course": "Warehouse Safety Basics",
      "certification_date": "2026-10-12",
      "issuer": "Mia Cole"
    }
  ]
}
```

### approve_enrollment_requests

Approve pending course enrollment requests, one or many. Access: write, asks the user first. REST: `POST /api/v1/absorb-lms/enrollment-requests/approve`. MCP: `absorb_lms_write → approve_enrollment_requests`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `request_ids` | array | yes | request_id values from list_course_approvals. |

Approves the listed requests as the Approve and mass Approve actions of the Course Approvals report do. The learner gets access to the course and Absorb sends its standard Enrollment message. Requests that were handled meanwhile are skipped and listed. Available actions depend on your Admin role. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "approved": [
    {
      "request_id": "a41f8c2d-6e07-4b93-8d15-3c7e9a2b5f01",
      "learner": "Priya Nair",
      "course": "Data Privacy Essentials"
    },
    {
      "request_id": "b52a9d3e-7f18-4ca4-9e26-4d8f0b3c6a12",
      "learner": "Luis Ortega",
      "course": "Data Privacy Essentials"
    }
  ],
  "skipped": []
}
```

### decline_enrollment_requests

Decline pending course enrollment requests, one or many. Access: write, asks the user first. REST: `POST /api/v1/absorb-lms/enrollment-requests/decline`. MCP: `absorb_lms_write → decline_enrollment_requests`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `request_ids` | array | yes | request_id values from list_course_approvals. |

Declines the listed requests as the Decline action of the Course Approvals report does. Absorb sends the learner its Approval Denied message. Requests handled meanwhile are skipped and listed. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "declined": [
    {
      "request_id": "c63b0e4f-8029-4db5-8f37-5e901c4d7b23",
      "learner": "Chen Wei",
      "course": "Data Privacy Essentials"
    }
  ],
  "skipped": []
}
```

### enroll_users

Enroll users in one course as an admin. Access: write, asks the user first. REST: `POST /api/v1/absorb-lms/courses/{course_id}/users/enroll`. MCP: `absorb_lms_write → enroll_users`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `course_id` | string | yes | Course ID from list_courses. |
| `user_ids` | array | yes | user_id values from list_users. |
| `re_enroll` | boolean | no | true creates a new assignment for users who completed the course. Default: false. |

Enrolls the listed users in one course through the Enroll User action of the Users report, so the Enrollment Method is Admin and the course approval step does not apply. Absorb often sends its enrollment message to the learner. A user who already completed the course needs re_enroll true, as Absorb asks for Re-Enroll in that case. Absorb processes large batches at 10 minute intervals, so check with list_course_enrollments a little later. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "course": "Warehouse Safety Basics",
  "enrolled": [
    {
      "user_id": "4f1c2a7e-8b3d-4c1a-9e55-0a6d3b7c1201",
      "name": "Dana Reyes"
    },
    {
      "user_id": "9b7e5d10-2c44-4f0b-8a31-6e2f9c4d7702",
      "name": "Omar Haddad"
    }
  ],
  "skipped": []
}
```

### unenroll_user

Remove one user's enrollment in one course. Access: write, asks the user first. REST: `POST /api/v1/absorb-lms/courses/{course_id}/users/{user_id}/unenroll`. MCP: `absorb_lms_write → unenroll_user`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `user_id` | string | yes | User ID from list_users. |
| `course_id` | string | yes | Course ID from list_courses. |

Removes the enrollment through the Un-enroll action of the Course Enrollments report. Read the enrollment with list_user_enrollments first. Completions that already happened stay on the transcript. The learner can no longer open the course. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "unenrolled": {
    "user_id": "9b7e5d10-2c44-4f0b-8a31-6e2f9c4d7702",
    "name": "Omar Haddad",
    "course": "Warehouse Safety Basics"
  }
}
```

### message_users

Send an Absorb message to selected users. Access: write, asks the user first. REST: `POST /api/v1/absorb-lms/users/message`. MCP: `absorb_lms_write → message_users`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `user_ids` | array | yes | user_id values from list_users or list_course_activity. |
| `subject` | string | yes | Message subject. |
| `body` | string | yes | Message text. |

Sends a message from the Message User workspace of the Users, Course Activity and Course Approvals reports to the users you name. Absorb delivers it to the learners. Write the subject and body plainly; the tool sends what you give it. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "sent_to": [
    {
      "user_id": "9b7e5d10-2c44-4f0b-8a31-6e2f9c4d7702",
      "name": "Omar Haddad"
    },
    {
      "user_id": "4f1c2a7e-8b3d-4c1a-9e55-0a6d3b7c1201",
      "name": "Dana Reyes"
    }
  ],
  "subject": "Warehouse Safety Basics is overdue"
}
```

### create_user

Add one user to the portal with a role and department. Access: write, asks the user first. REST: `POST /api/v1/absorb-lms/users`. MCP: `absorb_lms_write → create_user`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `first_name` | string | yes | First name. |
| `last_name` | string | yes | Last name. |
| `username` | string | yes | Login name. |
| `email` | string | no | Email address. |
| `department` | string | no | Department name. |
| `roles` | array | no | learner (default), reviewer, manager, instructor, creator or administrator. |

Creates a user through the Add User action of the Users report. The account is a Learner unless you pass roles; Absorb allows several roles per user (Learner, Reviewer, Manager, Instructor, Creator, Administrator). Fields that Absorb marks as required must be given, and the tool returns an error naming any that are missing. It creates an account other people sign in with. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "user_id": "7d2e9b41-3a60-4e8c-b5d7-1f4a8c6e9303",
  "name": "Sofia Marin",
  "username": "smarin",
  "department": "Finance",
  "roles": [
    "Learner"
  ],
  "status": "Active"
}
```

### set_user_status

Activate or deactivate users. Access: write, asks the user first. REST: `PUT /api/v1/absorb-lms/user-status`. MCP: `absorb_lms_write → set_user_status`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `user_ids` | array | yes | user_id values from list_users. |
| `status` | enum | yes | active or inactive. |

Sets the listed users to Active or Inactive, like the Activate Users and Deactivate Users mass actions. An Inactive user cannot take part in or record new training, and their enrollment records, scores and history stay in reports. One call with the opposite status undoes it. It changes who can sign in, so it asks first. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "updated": [
    {
      "user_id": "9b7e5d10-2c44-4f0b-8a31-6e2f9c4d7702",
      "name": "Omar Haddad",
      "status": "Inactive"
    }
  ]
}
```

## How do I connect Absorb LMS to Claude Code, Codex or Cursor?

Connecting Absorb LMS takes three steps: sign up, sign in to Absorb LMS once in your Cloud Browser and enable it for agents, then add one MCP server or call the REST API with the same key.

### Connect Absorb LMS to your agent.

1. **Create an account** Sign up and add Absorb LMS in the console. Your API key is there too.

2. **Sign in to Absorb LMS in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to Absorb LMS there yourself, the way you always do, then press Enable for agents, read only or read and write. We never save your password, and your agent keeps working even when your computer is off.

3. **Add Cotlet to your agent** Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

   Claude Code:

```
claude mcp add --transport http cotlet \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"
```

   Cursor:

```
{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": {
        "Authorization": "Bearer ${COTLET_API_KEY}"
      }
    }
  }
}
```

   Codex:

```
# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
```

4. **Ask your agent** Ask in plain words. Your agent finds the Absorb LMS tools on the server and calls them for you; anything that reaches other people waits for your OK unless you switch that off for a tool.

```
Go through the pending course approvals. Approve Finance requests for Data Privacy Essentials, decline requests from inactive users, and leave the rest for me with a one-line reason.
```

### Call Absorb LMS from your scripts.

1. **Export your API key** Your scripts use the same API key as your agent. Keep it in an environment variable, never in your code.

```
export COTLET_API_KEY="cotlet_..."
```

2. **Call a tool** Every tool is an endpoint under /api/v1/absorb-lms with its own method and path, listed with the endpoints above. Path parameters go in the URL; the other parameters go in the query for GET and DELETE and in a JSON body otherwise.

```
curl -X POST https://cotlet.dev/api/v1/absorb-lms/users \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"first_name":"Sofia","last_name":"Marin","username":"smarin","email":"sofia.marin@example.com","department":"Finance","roles":["learner"]}'
```

3. **Read the result** You get plain JSON back, ready for your script. A failed call costs nothing.

```
{
  "user_id": "7d2e9b41-3a60-4e8c-b5d7-1f4a8c6e9303",
  "name": "Sofia Marin",
  "username": "smarin",
  "department": "Finance",
  "roles": [
    "Learner"
  ],
  "status": "Active"
}
```

## Why use Cotlet for Absorb LMS?

**Built for agents**

- One MCP server for every app you connect.
- The same tools as a REST API for scripts and cron jobs.
- Works with Claude Code, Codex and Cursor.

**Your login stays yours**

- You sign in to Absorb LMS yourself, in your own Cloud Browser. We never save your password; the profile is encrypted with AES-256-GCM, the cipher 1Password uses.
- A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory.
- The model never sees a login.
- No stored passwords, no CAPTCHA solving, no MFA bypass.

**You stay in control**

- Scope each API key: its apps, its tools, read only or read and write.
- Anything that reaches other people waits for your OK, so a leaked key cannot post or message as you.
- Every background request listed in your Background activity. Disable for agents in one click.

**Kept working for you**

- We test every integration every 6 hours.
- When Absorb LMS changes, the tool pauses until we fix it.
- Failed calls cost nothing.

## Is it safe to connect Absorb LMS to Cotlet?

Yes. You sign in to Absorb LMS yourself, in your own Cloud Browser, and we never save your password. Your agents only get Absorb LMS once you enable it, and every background request is listed. The browser profile is stored encrypted with AES-256-GCM, the same cipher 1Password uses for its vaults and Apple for iCloud Keychain. Independent public scanners grade cotlet.dev A+ and find it clean; click a result to rerun it yourself.

- **A+ on Qualys SSL Labs**: Encryption in transit: TLS setup and certificates, on all four server addresses. [Live result](https://www.ssllabs.com/ssltest/analyze.html?d=cotlet.dev)
- **A+ on securityheaders.com**: Browser protections sent with every page, all six headers present. [Live result](https://securityheaders.com/?q=cotlet.dev&followRedirects=on)
- **A+ on Mozilla Observatory**: Mozilla's web security baseline: score 120 of 100, 12 of 12 tests passed. [Live result](https://developer.mozilla.org/en-US/observatory/analyze?host=cotlet.dev)
- **Clean on Sucuri SiteCheck**: No malware, spam or defacement, and not on any of 9 blocklists, Google Safe Browsing included. [Live result](https://sitecheck.sucuri.net/results/cotlet.dev)

[How Cotlet protects your access](https://cotlet.dev/security.md)

### Common concerns

**Who runs Cotlet?**

Cotlet is run by Take Group, a Polish software company working since 2019. Take Group runs about 3,200 websites on its own systems and has its own DevOps team for infrastructure security. We built and used integrations like this inside the company for years before opening them as Cotlet.

**Is this an official Absorb LMS integration?**

No, Cotlet is independent of Absorb LMS. Absorb LMS's own API is too limited for this work. Cotlet works through your own Absorb LMS account, the way you use Absorb LMS in the browser, so you need no partner approval and no developer setup.

**What about client data and GDPR?**

Cotlet is run from the EU and follows the GDPR. Cloud Browsers run in Finland, a Tier 1 country in the ITU Global Cybersecurity Index 2024. Data passes through a call and is not kept after it.

**Can I start with read only?**

Yes. Enable the app for agents as read only, or make the API key read only, and anything that reaches other people waits for your OK unless you switch that off per tool.

**Is it reliable?**

Every Cotlet service is checked every 3 minutes from Europe, North America, Asia and Australia. The live results and any outage are public at status.cotlet.dev.

**How do I stop?**

Press Disable for agents next to Absorb LMS in your console: your agents lose access at once and you stay signed in. Signing out of Absorb LMS in the browser works too, and Reset browser deletes the whole profile.

## Is there a Absorb LMS MCP server on GitHub?

No open-source Absorb LMS MCP server is known. The realistic option is the Integration API: you get a private key from your Absorb account team and write and maintain the code yourself. Cotlet hosts the tools for you and works in your own admin session.

|  | Integration API | Cotlet |
|---|---|---|
| Setup | Ask your Absorb account team for a private key, then write and test the calls | Sign up, sign in to Absorb once, add one MCP server or API key |
| When Absorb changes | You update your code against the API docs and changelog | Our team tests it daily and fixes it for you; failed calls are free |
| Your Absorb access | A private key tied to your portal, stored in your own code or secrets | Your own Cloud Browser in the EU, profile encrypted, only for the apps you enable, disabled for agents in one click |
| When the session expires | Your code signs in again | Your Cloud Browser keeps you signed in; if Absorb logs you out, your agent gets a link to sign in again |
| Upkeep | You host, monitor and debug it; Absorb Support does not review custom code | Nothing to host or update |
| Where it runs | Wherever you deploy your code | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule |
| Price | Access through your Absorb account team, plus developer time | Free 7-day trial, then pay-as-you-go credit packs, no subscription |

### Which one fits you

**Pick Cotlet if**

- you are not a developer, or you do not want to maintain a server
- you need it to keep working when Absorb LMS changes, without checking it yourself
- your agent or a script should run it on a schedule, also while your computer is off

**Pick an open-source server if**

- you are comfortable installing, updating and fixing it yourself
- you want your sign-in to stay on your own computer
- you only need it now and then, from one MCP client

## How much does the Absorb LMS API cost?

Free 7-day trial with 2,000 credits, no card needed. After that, the Absorb LMS API is pay as you go with no limit on apps: Credit packs from $29 for 5,000 credits, one-time, no subscription. A successful call uses 20 to 30 credits (25 for most tools, about $0.10 to $0.15), your Cloud Browser uses 50 credits a day while it has an app enabled for agents, however many apps that is, and an agent driving the browser itself uses 5 credits a minute. Credit packs stay valid for 12 months and stack, so unused credits carry over.

| Credits | Price, one time | Calls at 25 credits | Per 1,000 credits |
|---|---|---|---|
| 5,000 | $29 | 200 | $5.80 |
| 15,000 | $79 | 600 | $5.27 |
| 32,000 | $149 | 1,280 | $4.66 |
| 60,000 | $249 | 2,400 | $4.15 |

Only successful calls use credits; failed calls and timeouts cost nothing. At a balance of 0 calls pause, never a surprise charge. Authenticate with the `Authorization: Bearer` header. [See full pricing](https://cotlet.dev/pricing.md)

## How Cotlet holds your access

Cotlet hosts MCP servers and REST APIs for apps with no usable API. Your agent works in your own Absorb LMS account.

- **Company details:** Cotlet is run by Take Group sp. z o.o., a company registered in Poland. Its full address and registration numbers are in the Terms of service. [Terms of service](https://cotlet.dev/terms)
- **Your sign-in:** You sign in to Absorb LMS yourself, in your own Cloud Browser: a Chrome we run for you in the EU, one per app. We never save your password (password saving is off), the profile is stored encrypted with AES-256-GCM, and your agents get Absorb LMS only after you enable it. When Absorb LMS signs you out, your agent gives you a link to sign in again. [Security](https://cotlet.dev/security.md)
- **Revoking access:** Press Disable for agents next to Absorb LMS, sign out of Absorb LMS in your Cloud Browser, or reset the browser. Every background request is listed in your Background activity. Actions that reach other people wait for your OK unless you switch that off per tool.
- **What we never do:** Store passwords, solve CAPTCHAs or bypass MFA.
- **Absorb LMS's terms:** You use your own Absorb LMS account and stay responsible for following Absorb LMS's terms. Cotlet is independent and not affiliated with Absorb LMS. [Terms](https://cotlet.dev/terms)
- **Contact:** Questions about the company, security or an app: [contact@cotlet.dev](mailto:contact@cotlet.dev)

## Frequently asked questions

**How do I get access?**

Sign up free, open Absorb LMS in the console and press Request access. Then you create your API key and connect Absorb LMS there.

**Do I need to be technical?**

No. You sign in to Absorb LMS once in your Cloud Browser, a normal Chrome you open from the console, and paste one command into your agent, or one URL into n8n. Your agent can walk you through it. There is no server to install, update or fix.

**Is it safe to connect Absorb LMS to Cotlet?**

Yes. You sign in to Absorb LMS yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Absorb LMS once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.

**Is a hosted server safer than a local one? My Absorb LMS sign-in would leave my computer.**

On Cotlet you sign in inside your own Cloud Browser, which only you open, and its profile is stored encrypted with AES-256-GCM in the EU. Agents get only the apps you enable, and every background request is listed. A local server keeps your Absorb LMS cookie in a plain file on your computer, readable by any program you run, and stops when your computer is off.

**Why does Cotlet send requests instead of clicking in my browser?**

To be fast, Cotlet doesn't click through Absorb LMS's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. Absorb LMS sees the same browser and IP you signed in with, and every request is listed in your Background activity.

**What if someone gets my Cotlet API key?**

The key holds no Absorb LMS login or cookies, it only asks Cotlet to run a tool. It can call only the apps and tools you gave it, and a read-only key changes nothing. Anything that reaches other people, like posts, comments or messages, waits for your OK in the dashboard by default, so a leaked key cannot post or message as you. When you switch approval off for a scheduled job, give that job its own key limited to that one tool. Every call is in your activity log, and deleting the key ends access at once.

**Why a signed-in browser and not OAuth, like other integration platforms?**

Absorb LMS offers no OAuth token you can simply grant for these tools: its official API leaves them out or needs a developer app, a plan or an approval first (see the official API section above). That is why Cotlet sets the limits itself: per key, per tool, with your approval before anything reaches other people. Cotlet is run by Take Group sp. z o.o., an EU company (VAT PL6342984273).

**Does Absorb's own Aura MCP replace this?**

Not for actions. Absorb's Aura MCP for Claude and ChatGPT is planned for 27 Oct 2026, stays off until your IT adds the connector, and is read and answer only: no action is taken in the LMS. Use it to ask questions, and Cotlet to approve, enroll, message and deactivate.

**Which Absorb role does my agent need?**

Your own account. The agent sees what you see in Absorb and nothing more, and the actions it can take follow your Admin role permissions. An account without an Admin role cannot reach the reports.

**Why does a new enrollment not show right away?**

Absorb groups large volumes of changes and processes them at 10 minute intervals, so a short delay is normal. Read the enrollment again a few minutes later.

**Can my agent post or send messages in Absorb LMS without asking me?**

No. Every call to approve_enrollment_requests, decline_enrollment_requests, enroll_users, unenroll_user, message_users, create_user or set_user_status waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals.

**Can I use the Absorb LMS API in n8n?**

Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call its endpoints under https://cotlet.dev/api/v1/absorb-lms from the HTTP Request node.

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.