Integrations/
API, SFTP and automation
API, SFTP and automation

Intellum API for custom integrations

Developers connect Intellum to the systems your organization runs through the open v3 REST API, which reads and writes users, courses, enrollments and more. An admin creates the OAuth app, and your developers or Intellum Integration Services build the integration.

How it connects
API via OAuth app with signed key pair
Who sets it up
Admin creates app; developers build
What moves
Two-way: you define what moves

Common uses of the Intellum API

  • IT teams create and remove Intellum accounts automatically from the organization’s HR system.
  • Operations leads build custom two-way flows between Intellum and internal systems.
  • Analysts pull completion data into custom BI and reporting tools.

How the Intellum API works

An admin with unrestricted rights creates an OAuth app in Settings > API, chooses Read, Write or both scopes and generates a public and private key pair. Your application signs token requests with the private key.

Developers then call the v3 API to read and write users, courses, course sessions, enrollments, assessment responses, groups, purchases, taxonomy, certifications and more. The same API powers Workato recipes, MCP connectors and partner integrations.

How to set up the Intellum API

An unrestricted admin creates the OAuth app. Your developers build the integration, or Intellum Integration Services builds it for you.

  • Developer resources or an Integration Services budget
  • An Intellum admin with unrestricted rights
Security and IT

How the Intellum API handles access and data

  • Authentication: OAuth apps with Read, Write or both scopes, using token requests signed with a public and private key pair.
  • Private keys: Intellum does not store them. Download them when you create the app.
  • Test tokens: last one hour.
  • Rate limits: 200 requests per second from each source address. List endpoints allow 50 requests per 5 seconds per host and return a 429 with a Retry-After header when exceeded.
  • Data that moves: what moves, and in which direction, depends on the integration you build.
SOC 2 Type II
Controls audited by an independent CPA firm
AES-256 encryption
AES-256 at rest and 256-bit TLS in transit
AWS hosting
In the US, with an EU hosting option in AWS Ireland
Enterprise sign-in
SAML 2.0, OAuth 2.0, OpenID Connect, LDAP and ADFS
Read the security, privacy and architecture summary

What to know about the Intellum API

  • Build new work on v3. Version 2, which uses an API key, stays supported for legacy integrations only.

Questions about the Intellum API

Does Intellum have an open LMS API?

Yes. Intellum’s v3 API is an open REST API that reads and writes users, courses, enrollments, assessment responses, groups, purchases, certifications and more. Workato recipes, MCP connectors and partner integrations all run on it.

No. Intellum Integration Services can scope and build it for you. If you have developers, they build on the v3 API at no added cost, and teams that prefer recipes can use the prebuilt Intellum connector in Workato.

Yes. An HR system integration built on the API can create Intellum accounts for new hires and remove them when people leave. Accounts can also be created at first sign-in through SAML or OAuth.

Each source address can make 200 requests per second. List endpoints cap at 50 requests every 5 seconds per host, and requests over that limit get a 429 response with a Retry-After header.

See the Intellum API working with your stack

Walk through this integration, and the questions IT will ask, with an Intellum expert.