Connect any learning platform

How it works

There are four ways to bring learning into MuchSkills. You can use more than one at the same time.

Cornerstone, Degreed, Docebo, LinkedIn Learning, Coursera and internal LMSs have no native connector today. Routes 2, 3 and 4 work with all of them.

Before you start

• In MuchSkills: the Owner or Admin role to create API clients and to ask for a custom connector.
• Decide what you need. Certificates, goals, course links, or learning activity. The answer picks the route.
• For the API route: a developer, your LMS's integration features or an integration platform that can call a REST API.
• Check email addresses. MuchSkills identifies people by the email they sign in with. Your LMS must send that address.

Steps

Push certificates and goals through the API

1. Create an API client with the Write scope. Go to Team/Org › Settings › API Access, click New Client, give it a name, tick Write under Scopes and click Create Client. Copy the Client ID and Client Secret. The full set-up is in MuchSkills API and API Access.
2. Get an access token. Send the Client ID and Client Secret to POST https://app.muchskills.com/oauth2/token, form-encoded, with grant_type=client_credentials. The token lasts about an hour.
3. Send a certificate. When someone earns a certificate in your LMS, send it to POST /api/v1/user-certifications/{email}, using the person's MuchSkills email:

{
"certification": "AZ-104",
"issuingOrganization": "Microsoft",
"period": {
"license": "AZ104-2026-001",
"issuedAt": "2026-01-15",
"expiredAt": "2027-01-15",
"urls": ["https://issuer.example/verify/abc"]
}
}

MuchSkills finds the certificate by its exact name, its code (such as AZ-104) or a known alias. issuingOrganization narrows the search. For a certificate that never expires, leave out expiredAt and send "notExpiring": true. The same call renews a certificate the person already holds.

1. Set a goal (optional). To give someone a development goal, send POST /api/v1/goals/{email} with either a skill or a certification, and how they will reach it:

{
"certification": "AWS Certified Developer - Associate",
"issuingOrganization": "Amazon Web Services",
"reachingType": "classes",
"deadline": "2026-12-31"
}

For a skill, send "skill" and a "desiredLevel" from 1 to 9 instead. reachingType is mentor, self or classes.

Link courses in the Learning Library

1. Open the Learning Library. Go to My Growth › Learning Library.
2. Add a course. Click Add a course, paste the course's web address and click Get Page Details. MuchSkills fills in the title, image and description from the page. Adjust them and set the course level.
3. Tag the skills. Tag every skill the course builds. The course then appears on those skills' pages, in analysis lists and in each person's gap analysis.

Ask for a custom connector

1. Send us the details. Email support@muchskills.com or use the chat with:
   We reply with what is possible. A custom set-up includes a technical session between your administrator and our CTO.
   • the platform's name, and whether it is cloud or on your own servers
   • a link to its API documentation
   • the data you want in MuchSkills, such as catalogue, completions or certificates
   • who should be in scope
   • a technical contact on your side

Check it worked

• API: the certificate call answers 200 with the certificate and its active periods. The certificate appears under the person's My Skills › My Certifications.
• Goals: the goal appears under the person's My Growth › Goals.
• Learning Library: the course is listed in the library and shows up in My Growth › Gap Analysis for people who lack a tagged skill.

What you get

• One place for proof. Certificates from any platform sit with the rest, with dates, proof files and full history.
• Learning tied to gaps. Courses tagged with skills appear exactly where people see what they are missing.
• No lock-in. You keep your learning platform, and MuchSkills works next to it.

Important to know

No endpoint for course activity yet. The API takes certificates and goals. It does not take course progress or completions. If you need activity from a platform without a native connector, ask for a custom connector.

Certificates are history. Each call adds a period of holding the certificate. To fix a mistake, correct the period with PATCH /api/v1/user-certifications/{periodId} rather than deleting it and sending it again.

Links or files as proof. A link in urls is stored as it is, and stops working if the source moves the file. To keep a lasting copy, upload the file itself. A certificate period holds up to 10 attachments of up to 10 MB each.

Goal rules. A person can have one open goal per skill or certificate. A certificate they already hold cannot become a goal.

Request limits. If you send requests too fast, the API answers 429. Wait and retry with a growing pause. The goals calls allow one request per second for each token.

Troubleshooting