TalentLMS
TalentLMS is a cloud-based learning management system (LMS) with a REST API for managing users, courses, categories, branches, groups, and enrollments, as well as accessing completion and assessment report data. The API supports over 50 endpoints covering user and course lifecycle management, group and branch administration, and retrieval of test and survey results. Authentication uses API key-based HTTP Basic Auth on V1 and header-based API keys on V2. TalentLMS V2 introduces versioned requests, clear rate-limit response headers, and a dedicated developer hub.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles TalentLMS the way a machine reads it — 32 machine-readable artifacts across 12 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — TalentLMS scores 57.7/100 (developing), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile TalentLMS
Each block below is one kind of artifact we hold for TalentLMS. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 12
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
TalentLMS API
REST API for TalentLMS providing programmatic access to users, courses, categories, branches, groups, enrollments, and reporting data including test and survey results. Over 50 ...
TalentLMS Batch Actions API
This section introduces endpoints that perform bulk actions. After invoking any of the below endpoints, their response includes a background task ID.. You can use the `GET api/v...
TalentLMS Branch API
The Branch API from TalentLMS — 5 operation(s) for branch.
TalentLMS Category API
The Category API from TalentLMS — 3 operation(s) for category.
TalentLMS Course API
The Course API from TalentLMS — 6 operation(s) for course.
TalentLMS Group API
The Group API from TalentLMS — 5 operation(s) for group.
TalentLMS Learning Paths API
The Learning Paths API from TalentLMS — 3 operation(s) for learning paths.
TalentLMS Portal API
The Portal API from TalentLMS — 2 operation(s) for portal.
TalentLMS Task API
The Task API from TalentLMS — 1 operation(s) for task.
TalentLMS Timeline API
The Timeline API from TalentLMS — 1 operation(s) for timeline.
TalentLMS Unit API
The Unit API from TalentLMS — 2 operation(s) for unit.
TalentLMS User API
The User API from TalentLMS — 16 operation(s) for user.
Scroll within the panel for all 12 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Talentlms Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Talentlms Finops
FINOPSSemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Talentlms Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
TalentLMS API Rules
SPECTRALJSON Schema 12
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
getuserbranches-response-200
JSON SCHEMAgetuserbyid-response-200
JSON SCHEMAgetusercertificates-response-200
JSON SCHEMAgetusercourses-response-200
JSON SCHEMAgetusergroups-response-200
JSON SCHEMAgetuserresources-response-200
JSON SCHEMAGroupCourseItem
JSON SCHEMAPaginationLinks
JSON SCHEMAPaginationMeta
JSON SCHEMAUserGamification
JSON SCHEMAUserGamificationBadge
JSON SCHEMAUserListItem
JSON SCHEMAScroll within the panel for all 12 ·
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for TalentLMS — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 3
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/talentlms · machine-readable index on apis.io