[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)

# iSpring Learn (iSpring LMS) API and MCP server

> iSpring Learn has a REST API, but only with the Business subscription, and no official MCP server (checked 20 Oct 2026). The API covers users, departments, courses, enrollments and results, so an agent needs custom code and a token; the Zapier app covers users, departments and enrollments but has no progress or report actions.

Cloud LMS from iSpring (called iSpring LMS in its help center) for training employees and customers: courses, enrollments with due dates, learner progress reports and users in departments and groups.

## What is the iSpring Learn (iSpring LMS) API?

Cotlet's iSpring Learn (iSpring LMS) API exposes 12 endpoints for your own iSpring Learn (iSpring LMS) account: list courses, list departments, list groups, list users, list enrollments of a course, get learner progress report, enroll users in courses, cancel enrollments, reset enrollment progress, add users by email, deactivate users and activate users. The list_courses endpoint returns courses in Learning Content, with title and the number of people enrolled. Each endpoint takes simple JSON inputs like cursor, query or department_id and works both as an operation of the ispring_read or ispring_write MCP tool for agents and as a REST call for scripts.

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

iSpring Learn has a REST API, but only with the Business subscription, and no official MCP server (checked 20 Oct 2026). Cotlet is a hosted MCP server and REST API for iSpring Learn (iSpring LMS) with 12 endpoints (6 read, 6 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does iSpring Learn (iSpring LMS) have an official API?

iSpring Learn has a REST API, but only with the Business subscription, and no official MCP server (checked 20 Oct 2026). The API covers users, departments, courses, enrollments and results, so an agent needs custom code and a token; the Zapier app covers users, departments and enrollments but has no progress or report actions.

| Task | iSpring Learn (iSpring LMS) official | Cotlet |
|---|---|---|
| List courses | Partly: REST API, Business subscription only | Yes |
| List users, departments and groups | Partly: REST API and Zapier, Business subscription for the API | Yes |
| Enroll users in courses | Partly: REST API and a Zapier action; the API needs the Business subscription | Yes |
| List enrollments of a course | Partly: REST API and Zapier search; the API needs the Business subscription | Yes |
| Learner Progress report with totals | Partly: The API returns learner results, not the report with its totals; no Zapier action | Yes |
| Cancel or reset enrollments | Partly: REST API only, Business subscription | Yes |
| Add users by email in bulk | Partly: The API adds users one call at a time | Yes |
| Deactivate and reactivate users | Partly: REST API and Zapier; the API needs the Business subscription | Yes |

Sources: [iSpring Help: REST API](https://ispringhelpdocs.com/ispring-learn/rest-api-10684924.html), [iSpring Learn REST API (OpenAPI file)](https://api-learn.ispring.com/docs/rest-api), [iSpring Learn on Zapier MCP](https://zapier.com/mcp/ispring-learn), [iSpring LMS pricing](https://www.ispring.com/pricing)

## For AI agents

```text
iSpring Learn has a REST API, but only with the Business subscription, and no official MCP server (checked 20 Oct 2026). The API covers users, departments, courses, enrollments and results, so an agent needs custom code and a token; the Zapier app covers users, departments and enrollments but has no progress or report actions.
Cotlet provides a hosted MCP server and REST API for iSpring Learn (iSpring LMS): 12 tools (6 read, 6 write).
Access       Sign up at https://cotlet.dev/app/signup?app=ispring, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    ispring_read, ispring_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/ispring, each operation at its own route, e.g. POST /api/v1/ispring/users/enroll
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_courses, list_departments, list_groups, list_users, list_enrollments, get_learner_progress, enroll_users, cancel_enrollment, reset_enrollment, add_users_by_email, deactivate_users, activate_users
Confirm      enroll_users, cancel_enrollment, reset_enrollment, add_users_by_email, deactivate_users (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/ispring-api-mcp-server.md

How access works:
1. The user signs up at https://cotlet.dev/app/signup?app=ispring, requests iSpring Learn (iSpring LMS) in the Cotlet console and creates an API key there.
2. The user signs in to iSpring Learn (iSpring LMS) once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables iSpring Learn (iSpring 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 iSpring Learn (iSpring 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 iSpring Learn (iSpring 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 iSpring Learn (iSpring 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 iSpring Learn (iSpring 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 iSpring Learn (iSpring LMS)'s terms; Cotlet is not affiliated with iSpring Learn (iSpring LMS).
```

## What can an AI agent do in iSpring Learn (iSpring LMS)?

Cotlet is best for L&D and HR admins who run iSpring Learn and want their AI agent to enroll learners, deactivate leavers and report overdue training without running or fixing a server.

- **[Enroll a department in a course](https://cotlet.dev/integrations/ispring-api-mcp-server/enroll-department-in-course.md)**: "Enroll everyone in the Sales department who is not yet in Information Security Basics. Start on 2 November, due 30 November, and list who you skipped." → `list_courses`, `list_departments`, `list_users`, `list_enrollments`, `enroll_users`
- **[Deactivate accounts of people who left](https://cotlet.dev/integrations/ispring-api-mcp-server/deactivate-leavers.md)** (runs: weekly): "Here are the emails of people who left this week. Deactivate their iSpring Learn accounts today, skip anyone who is an administrator, and tell me who was not found." → `list_users`, `deactivate_users`
- **Weekly overdue training report** (runs: weekly): "Every Monday, show who is overdue in the Learner Progress report, by department, and list the courses they are late on." → `list_departments`, `get_learner_progress`, `list_enrollments`
- **Let a failed or lapsed cohort retake a course**: "Find everyone who failed Information Security Basics and reset their progress so they can take it again." → `list_enrollments`, `reset_enrollment`
- **Onboard new hires from a list of emails** (runs: weekly): "Add these new hire emails to the Support department and the New hires 2026 group, then enroll them in Onboarding for New Hires." → `list_departments`, `list_groups`, `add_users_by_email`, `enroll_users`

## Can iSpring Learn (iSpring LMS) automations run on a schedule in n8n, Make or Zapier?

Yes. Cotlet does not replace your automation platform: it gives it a iSpring Learn (iSpring 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 deactivate accounts of people who left, 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/ispring/users. | 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/ispring/users with your API key. | cron or GitHub Actions. |

## Tools

**For AI agents:** Every endpoint and its schema is public. The 12 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 iSpring Learn (iSpring LMS).

### list_courses

Courses in Learning Content, with title and the number of people enrolled. Access: read. REST: `GET /api/v1/ispring/courses`. MCP: `ispring_read → list_courses`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `query` | string | no | Part of the course title. |
| `limit` | integer | no | Courses per page. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns the courses of Learning Content, newest change first, in pages; pass next_cursor back as cursor for the next page. enrolled is the number of enrollments in the course. Use course_id in list_enrollments and enroll_users.

Example response:

```json
{
  "courses": [
    {
      "course_id": "c_4f2a91",
      "title": "Information Security Basics",
      "enrolled": 38,
      "updated_at": "2026-10-12T10:20:00Z"
    },
    {
      "course_id": "c_4f2b07",
      "title": "Onboarding for New Hires",
      "enrolled": 24,
      "updated_at": "2026-10-05T08:02:00Z"
    }
  ],
  "next_cursor": null
}
```

### list_departments

Departments of the account with their parent department. Access: read. REST: `GET /api/v1/ispring/departments`. MCP: `ispring_read → list_departments`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `query` | string | no | Part of the department name. |

Returns the department tree of the Users section. Every user belongs to exactly one department. Department Administrators see only the departments they manage and their sub-departments. Use department_id in list_users and add_users_by_email.

Example response:

```json
{
  "departments": [
    {
      "department_id": "d_10",
      "name": "Sales",
      "parent": "Company"
    },
    {
      "department_id": "d_11",
      "name": "Support",
      "parent": "Company"
    }
  ]
}
```

### list_groups

User groups of the account with their member count. Access: read. REST: `GET /api/v1/ispring/groups`. MCP: `ispring_read → list_groups`.

No parameters.

Returns the groups of the Users section. A user can be in any number of groups, and a group can hold users from several departments. Use group_id in list_users and add_users_by_email.

Example response:

```json
{
  "groups": [
    {
      "group_id": "g_3",
      "name": "New hires 2026",
      "members": 17
    },
    {
      "group_id": "g_4",
      "name": "Team leads",
      "members": 9
    }
  ]
}
```

### list_users

Users with login, email, department, groups and status. Access: read. REST: `GET /api/v1/ispring/users`. MCP: `ispring_read → list_users`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `query` | string | no | Name, login or email. |
| `department_id` | string | no | Only users of this department and its sub-departments. |
| `group_id` | string | no | Only members of this group. |
| `status` | enum | no | active (default) or inactive. |
| `limit` | integer | no | Users per page. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists users in pages; pass next_cursor back as cursor for the next page. status is active or inactive; inactive users cannot sign in, so an enrollment for them is refused. Without department or group the whole account is searched, within the departments your role manages.

Example response:

```json
{
  "users": [
    {
      "user_id": "u_81c2d4",
      "name": "Ana Lopez",
      "login": "ana.lopez",
      "email": "ana.lopez@example.com",
      "department": "Sales",
      "groups": [
        "New hires 2026"
      ],
      "status": "active"
    },
    {
      "user_id": "u_81c2e9",
      "name": "Tom Becker",
      "login": "tom.becker",
      "email": "tom.becker@example.com",
      "department": "Sales",
      "groups": [],
      "status": "active"
    }
  ],
  "next_cursor": null
}
```

### list_enrollments

Who is enrolled in one course, with status, start date and due date. Access: read. REST: `GET /api/v1/ispring/courses/{course_id}/enrollments`. MCP: `ispring_read → list_enrollments`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `course_id` | string | yes | Course from list_courses. |
| `status` | enum | no | passed, failed, in_progress or not_started. Default: all. |
| `overdue_only` | boolean | no | Only enrollments past their due date. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns the rows of the course's Enrollments tab, in pages. status is passed, failed, in_progress or not_started, and overdue is true when the due date has passed. Use enrollment_id in cancel_enrollment and reset_enrollment.

Example response:

```json
{
  "enrollments": [
    {
      "enrollment_id": "e_70a0f1",
      "user_id": "u_81c2c0",
      "user": "Lena Ortiz",
      "status": "in_progress",
      "start_date": "2026-10-01T09:00:00",
      "due_date": "2026-10-15T00:00:00",
      "overdue": true
    },
    {
      "enrollment_id": "e_70a0f2",
      "user_id": "u_81c2c1",
      "user": "Sam Okafor",
      "status": "passed",
      "start_date": "2026-10-01T09:00:00",
      "due_date": "2026-10-15T00:00:00",
      "overdue": false
    }
  ],
  "next_cursor": null
}
```

### get_learner_progress

The Learner Progress report: totals by status and one row per enrollment. Access: read. REST: `GET /api/v1/ispring/learner-progress`. MCP: `ispring_read → get_learner_progress`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `department_id` | string | no | Only this department and its sub-departments. |
| `group_id` | string | no | Only members of this group. |
| `course_id` | string | no | Only this learning item. A course nobody is enrolled in still shows. |
| `enrollment_type` | enum | no | enrolled_by_administrator (mandatory items) or added_from_catalog (items learners added). Default: both. |
| `user_status` | enum | no | active (default) or inactive. |
| `cursor` | string | no | Next page cursor from the previous call. |

Opens Reports, Learner Progress, with the filters you pass, and returns the totals above the table and its rows. trained is the completion rate: completed enrollments divided by all enrollments. Only active users appear unless user_status is inactive, and a Department Administrator sees only the departments they manage.

Example response:

```json
{
  "summary": {
    "trained_percent": 60,
    "passed": 24,
    "failed": 0,
    "in_progress": 6,
    "not_started": 10,
    "overdue": 3
  },
  "rows": [
    {
      "user": "Lena Ortiz",
      "department": "Sales",
      "course": "Information Security Basics",
      "status": "in_progress",
      "due_date": "2026-10-15T00:00:00",
      "overdue": true
    },
    {
      "user": "Sam Okafor",
      "department": "Sales",
      "course": "Information Security Basics",
      "status": "passed",
      "due_date": "2026-10-15T00:00:00",
      "overdue": false
    }
  ],
  "next_cursor": null
}
```

### enroll_users

Enroll users in one or more courses with a start date and a due date. Access: write, asks the user first. REST: `POST /api/v1/ispring/users/enroll`. MCP: `ispring_write → enroll_users`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `course_ids` | string[] | yes | Courses from list_courses. |
| `user_ids` | string[] | yes | Users from list_users. |
| `start_date` | datetime | no | When the course opens. Default: now. |
| `due_mode` | enum | no | use_course_settings (default), by_date, for_period or none. |
| `due_date` | date | no | Needed for by_date. |
| `due_period` | string | no | Needed for for_period: a number and days, weeks, months or years, e.g. "30 days". |
| `restrict_access_after_due` | boolean | no | With by_date or for_period: learners cannot study after the due date. Default: false. |

Runs the Enroll Users wizard: courses, users, then parameters. due_mode is use_course_settings (the Availability tab of the course), by_date (midnight of due_date unless a time is given), for_period (due_period counted from the start) or none. In for_period a month is always 30 days and a year 365. Learners get a notification in the user portal and by email, and the course appears in My Courses. Department Administrators can enroll only users from their departments. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "enrolled": 2,
  "enrollments": [
    {
      "enrollment_id": "e_70a1b3",
      "user": "Ana Lopez",
      "course": "Information Security Basics",
      "start_date": "2026-11-02T09:00:00",
      "due_date": "2026-11-30T00:00:00"
    },
    {
      "enrollment_id": "e_70a1b4",
      "user": "Tom Becker",
      "course": "Information Security Basics",
      "start_date": "2026-11-02T09:00:00",
      "due_date": "2026-11-30T00:00:00"
    }
  ]
}
```

### cancel_enrollment

Cancel the enrollments you list, the same as on the course's Enrollments tab. Access: write, asks the user first. REST: `POST /api/v1/ispring/enrollment/cancel`. MCP: `ispring_write → cancel_enrollment`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `enrollment_ids` | string[] | yes | Enrollments from list_enrollments. |

Cancels each enrollment_id from list_enrollments and returns the ones that were cancelled. Department Administrators can cancel only enrollments of users in their departments. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "cancelled": 1,
  "enrollment_ids": [
    "e_70a0f1"
  ]
}
```

### reset_enrollment

Reset the progress of enrollments so learners can take the course again. Access: write, asks the user first. REST: `POST /api/v1/ispring/enrollment/reset`. MCP: `ispring_write → reset_enrollment`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `enrollment_ids` | string[] | yes | Enrollments from list_enrollments. |

Resets the progress of each enrollment_id from list_enrollments and returns their new status, not_started. The enrollment, its start date and its due date stay. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "reset": 1,
  "enrollments": [
    {
      "enrollment_id": "e_70a0f1",
      "status": "not_started"
    }
  ]
}
```

### add_users_by_email

Add users from a list of email addresses to a department and optional groups. Access: write, asks the user first. REST: `POST /api/v1/ispring/departments/{department_id}/users-by-emails`. MCP: `ispring_write → add_users_by_email`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `emails` | string[] | yes | Up to 50 email addresses. |
| `department_id` | string | yes | Department from list_departments. |
| `group_ids` | string[] | no | Up to 5 groups from list_groups. |

Runs Users, Export/Import, Add users by email: up to 50 emails per call, one department, and up to 5 groups. An email that already belongs to a user is added to the groups and stays in their current department. Only the Account Owner and Account Administrators can use this. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "added": 2,
  "existing": 0,
  "users": [
    {
      "user_id": "u_a1f003",
      "email": "new.hire1@example.com",
      "department": "Support"
    },
    {
      "user_id": "u_a1f004",
      "email": "new.hire2@example.com",
      "department": "Support"
    }
  ]
}
```

### deactivate_users

Deactivate users now or on a date. Their history stays in reports. Access: write, asks the user first. REST: `POST /api/v1/ispring/users/deactivate`. MCP: `ispring_write → deactivate_users`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `user_ids` | string[] | yes | Users from list_users. |
| `deactivate_on` | date | no | Schedule the deactivation for this date. Default: now. |

Sets users to Inactive, now or on deactivate_on. Inactive users cannot sign in, get notifications, open their courses or be assigned new ones, and they stop counting as active users. Their statistics stay for reports, and an administrator can reactivate them later. The Account Owner cannot be deactivated, and Department Administrators can deactivate only users in their departments. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "deactivated": 2,
  "scheduled_for": null,
  "users": [
    {
      "user_id": "u_92b7c1",
      "name": "Maria Silva",
      "status": "inactive"
    },
    {
      "user_id": "u_92b7c2",
      "name": "Jake Ortiz",
      "status": "inactive"
    }
  ]
}
```

### activate_users

Set inactive users back to Active. Access: write. REST: `POST /api/v1/ispring/users/activate`. MCP: `ispring_write → activate_users`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `user_ids` | string[] | yes | Inactive users from list_users with status inactive. |

Reactivates users and returns their status, with their permissions and history as before. It reaches no one by itself and one deactivate_users call undoes it, so it does not wait for your OK.

Example response:

```json
{
  "activated": 1,
  "users": [
    {
      "user_id": "u_92b7c1",
      "name": "Maria Silva",
      "status": "active"
    }
  ]
}
```

## How do I connect iSpring Learn (iSpring LMS) to Claude Code, Codex or Cursor?

Connecting iSpring Learn (iSpring LMS) takes three steps: sign up, sign in to iSpring Learn (iSpring 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 iSpring Learn (iSpring LMS) to your agent.

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

2. **Sign in to iSpring Learn (iSpring LMS) in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to iSpring Learn (iSpring 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 iSpring Learn (iSpring 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.

```
Enroll everyone in the Sales department who is not yet in Information Security Basics. Start on 2 November, due 30 November, and list who you skipped.
```

### Call iSpring Learn (iSpring 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/ispring 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/ispring/users/enroll \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"course_ids":["c_4f2a91"],"user_ids":["u_81c2d4","u_81c2e9"],"start_date":"2026-11-02T09:00","due_mode":"by_date","due_date":"2026-11-30"}'
```

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

```
{
  "enrolled": 2,
  "enrollments": [
    {
      "enrollment_id": "e_70a1b3",
      "user": "Ana Lopez",
      "course": "Information Security Basics",
      "start_date": "2026-11-02T09:00:00",
      "due_date": "2026-11-30T00:00:00"
    },
    {
      "enrollment_id": "e_70a1b4",
      "user": "Tom Becker",
      "course": "Information Security Basics",
      "start_date": "2026-11-02T09:00:00",
      "due_date": "2026-11-30T00:00:00"
    }
  ]
}
```

## Why use Cotlet for iSpring Learn (iSpring 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 iSpring Learn (iSpring 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 iSpring Learn (iSpring LMS) changes, the tool pauses until we fix it.
- Failed calls cost nothing.

## Is it safe to connect iSpring Learn (iSpring LMS) to Cotlet?

Yes. You sign in to iSpring Learn (iSpring LMS) yourself, in your own Cloud Browser, and we never save your password. Your agents only get iSpring Learn (iSpring 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 iSpring Learn (iSpring LMS) integration?**

No, Cotlet is independent of iSpring Learn (iSpring LMS). iSpring Learn (iSpring LMS)'s own API is too limited for this work. Cotlet works through your own iSpring Learn (iSpring LMS) account, the way you use iSpring Learn (iSpring 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 iSpring Learn (iSpring LMS) in your console: your agents lose access at once and you stay signed in. Signing out of iSpring Learn (iSpring LMS) in the browser works too, and Reset browser deletes the whole profile.

## Is there a iSpring Learn (iSpring LMS) MCP server on GitHub?

No open-source iSpring Learn MCP server turned up in the search. Zapier has an iSpring Learn app with 3 triggers and 22 actions on users, departments, courses and enrollments. Cotlet adds the learner progress report and reads on demand, in the same admin account you use by hand.

|  | Zapier | Cotlet |
|---|---|---|
| Setup | Connect iSpring Learn in Zapier, then build a Zap for each job | Sign up, sign in to iSpring Learn once, add one MCP server or API key |
| What it covers | 3 triggers and 22 actions on users, departments, courses and enrollments; no progress report | Enrollments, the Learner Progress report, resets, users and departments, asked for in plain words |
| When iSpring Learn changes | Zapier maintains its app; a job you built stays as you built it | Our team tests it daily and fixes it for you; failed calls are free |
| Your iSpring session | Zapier keeps a connection to your account | In 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 | The connection fails until you reconnect it | Your Cloud Browser keeps you signed in; if iSpring Learn logs you out, your agent gets a link to sign in again |
| Where it runs | In Zapier, on its triggers | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule. It also works inside a Zap |
| Price | A Zapier plan | 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 iSpring Learn (iSpring 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 iSpring Learn (iSpring LMS) API cost?

Free 7-day trial with 2,000 credits, no card needed. After that, the iSpring Learn (iSpring 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 iSpring Learn (iSpring 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 iSpring Learn (iSpring 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 iSpring Learn (iSpring LMS) only after you enable it. When iSpring Learn (iSpring 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 iSpring Learn (iSpring LMS), sign out of iSpring Learn (iSpring 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.
- **iSpring Learn (iSpring LMS)'s terms:** You use your own iSpring Learn (iSpring LMS) account and stay responsible for following iSpring Learn (iSpring LMS)'s terms. Cotlet is independent and not affiliated with iSpring Learn (iSpring 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 iSpring Learn (iSpring LMS) in the console and press Request access. Then you create your API key and connect iSpring Learn (iSpring LMS) there.

**Do I need to be technical?**

No. You sign in to iSpring Learn (iSpring 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 iSpring Learn (iSpring LMS) to Cotlet?**

Yes. You sign in to iSpring Learn (iSpring LMS) yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get iSpring Learn (iSpring 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 iSpring Learn (iSpring 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 iSpring Learn (iSpring 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 iSpring Learn (iSpring LMS)'s pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. iSpring Learn (iSpring 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 iSpring Learn (iSpring 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?**

iSpring Learn (iSpring 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).

**Do I need the Business subscription?**

Not for Cotlet. iSpring Learn labels its REST API as available with the Business subscription, and Cotlet works in your own administrator account instead of the API. Your role still counts: the Account Owner and Account Administrators reach all departments, and a Department Administrator only the departments they manage and their sub-departments.

**What does it not cover?**

It covers the web administrator portal of iSpring Learn, not the iSpring Suite authoring tools. Authoring or editing course content, learning tracks, trainings, appraisals and gamification are not part of these tools.

**Can my agent post or send messages in iSpring Learn (iSpring LMS) without asking me?**

No. Every call to enroll_users, cancel_enrollment, reset_enrollment, add_users_by_email or deactivate_users waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. activate_users runs without asking, because it sends nothing to anyone and one call undoes it.

**Can I use the iSpring Learn (iSpring 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/ispring 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.