- Learning content: fetch an asset by URN, search by criteria, browse by locale and type
- Classifications: taxonomy by locale and type, by category URN or by keyword
- Learning activity reports: completions and engagement per learner or content for your enterprise account
- Seven routes, all read-only, documented in the AI integration guide (llms.txt)
LinkedIn Learning Solutions API Connector
LinkedIn Learning's partner API — learning assets by URN, criteria, locale and type, classifications by category and keyword, and learning activity reports — registered in Apivom Atlas as seven read-only routes for L&D platforms and HR tenants, with your own LinkedIn Learning token.
What you can do
Use cases
- Surface courses inside your LMS — Search and browse LinkedIn Learning assets by skill or category and link them into your own learning paths with up-to-date metadata.
- Completion reporting in HR — Pull learning activity reports on a schedule to record completions against employee records and development plans.
LinkedIn Learning exposes its catalogue and its usage data to enterprise customers and LMS partners through Learning Solutions. The content side lets you fetch a specific course, video or learning path by URN, search assets by criteria, list them by locale and type, and navigate the classification taxonomy — by locale and type, by category or by keyword — so your own learning portal can show LinkedIn Learning content in context. The reporting side returns learning activity reports: which learners completed or engaged with which content over a period, for your enterprise account. All seven routes are read-only. Apivom Atlas registers them with the credential contract (a client-credentials token from your LinkedIn Learning enterprise application) and the AI integration guide (llms.txt), logging every call per tenant. No Apivom product workflow uses LinkedIn Learning today — the connector is available to tenants running L&D or HR platforms, and a product workflow is scoped per customer.
A LinkedIn OAuth 2.0 access token — 3-legged for member-authorised actions or client-credentials for partner programs — sent as Bearer per request, with the LinkedIn-Version header on versioned APIs. Stored tokens are encrypted in your Iris tenant; Apivom Atlas forwards, logs and stores nothing.
Frequently asked questions
Can I switch this connector on today?
The connector is registered in Apivom Atlas — every route is catalogued, the credential contract is published and the AI integration guide (llms.txt) is live — and your credential can be stored in Apivom Iris. Wiring it into a product workflow (sync, automation, notifications) is done per customer: tell us the use case and we scope it with you.
Which LinkedIn Learning account do I need?
An enterprise LinkedIn Learning subscription with API access enabled by your account team, which provides the application credentials used for the client-credentials token. Content metadata is available to all enterprise accounts; activity reports cover your own learners.
Does Apivom charge per API call for this connector?
No. Connectors are part of your Apivom tenant and are not metered in the Atlas portal. The vendor's own pricing, quotas and rate limits still apply to the account you connect — Apivom paces its calls to stay inside them and shows every call in your tenant's integration log.
Where are my credentials stored and who can see the traffic?
Apivom Atlas is a stateless gateway: it never stores vendor credentials or tokens. The Apivom product that connects keeps the credential encrypted in your tenant database, and every request and response is logged in your tenant only — your data is never shared across tenants.
More Atlas integrations
AI integration guide (llms.txt)
Machine-readable markdown — feed it to your AI assistant as integration instructions.