Bolt.new AI and Lynda (LinkedIn Learning) integration: Step-by-Step Guide 2025

Bolt.new cannot directly “integrate with Lynda/LinkedIn Learning” because LinkedIn does not provide a public API for accessing Lynda.com / LinkedIn Learning course content, user progress, or search. The only usable entry point for external integrations is the LinkedIn REST API, and that API does not expose Lynda/LinkedIn Learning data. Therefore, any integration you build in Bolt.new must work through standard LinkedIn OAuth and whatever endpoints LinkedIn actually exposes — but none of them give you access to Learning course catalogs or playback data.

 

What you can integrate today

 

You can build in bolt.new an app that:

• Authenticates a user with LinkedIn OAuth 2.0
• Calls any supported LinkedIn REST APIs (profile, organizations, UGC posts, ads, etc.)
• Stores access tokens in environment variables inside Bolt

But you cannot fetch LinkedIn Learning courses, descriptions, videos, or user progress because LinkedIn does not expose these capabilities outside enterprise SSO integrations (a separate product that requires a corporate agreement, not API access).

 

If your goal is “recommend courses from LinkedIn Learning using Bolt.new”

 

You can still build a helper workflow:

• You scrape or manually maintain a curated dataset of Learning course URLs (you must follow LinkedIn’s Terms — scraping is generally forbidden).
• You store this dataset in your Bolt project or a small hosted DB.
• You let your AI logic in Bolt generate recommendations based on text, then redirect users to the public course URLs on LinkedIn Learning.

But you cannot programmatically read private metadata from LinkedIn Learning.

 

How to implement the only possible real integration inside bolt.new

 

This is the correct technical pattern for integrating Bolt.new with LinkedIn's legitimate APIs:

• Register an app at: https://www.linkedin.com/developers/
• Enable OAuth 2.0
• Set your redirect URI to a Bolt.new route (for example, https://your-bolt-app.vercel.app/api/auth/callback)
• Use OAuth to obtain an access token
• Use the token to call any supported API endpoint

 

// Example: basic LinkedIn profile fetch from a Bolt.new Next.js API route

export default async function handler(req, res) {
  try {
    const token = process.env.LINKEDIN_ACCESS_TOKEN; // store securely in Bolt env vars

    const response = await fetch(
      "https://api.linkedin.com/v2/me",
      {
        method: "GET",
        headers: {
          Authorization: `Bearer ${token}`
        }
      }
    );

    const data = await response.json();
    res.status(200).json(data);

  } catch (err) {
    res.status(500).json({ error: err.message });
  }
}

 

This is the real and only supported way to integrate Bolt.new with LinkedIn services.

No endpoint exists for:

• LinkedIn Learning course data
• LinkedIn Learning progress
• Lynda.com API (Lynda API was never public; now merged into LinkedIn Learning)

 

If you need enterprise LinkedIn Learning integration

 

Large companies can use SSO + SCIM provisioning to integrate Learning with internal systems. That is not an API. Bolt.new cannot access it unless your company provides an internal proxy layer that you own.

That means: only the IT department with a LinkedIn Learning Enterprise contract can expose internal endpoints to your Bolt app.

 

Summary: Bolt.new cannot directly integrate with Lynda/LinkedIn Learning because LinkedIn provides no public API for Learning content. The only real integration path is LinkedIn OAuth + approved endpoints, or a custom internal proxy if your company has an enterprise agreement.