LearnWorlds Integration
LearnWorlds can issue TRUE certificates on course completion
LearnWorlds has one of the better webhook systems in the category. It fires on course completion, it signs what it sends so the receiver can prove it is genuine, and it retries a failed delivery rather than dropping it. Point it at TRUE and every completion issues a branded, blockchain secured certificate on your own domain.
TL;DR
LearnWorlds documents a course completion webhook that posts to an address you choose. Each delivery is signed, so TRUE can confirm the call really came from your school before issuing anything, and a delivery that fails is retried with a growing gap rather than lost. An administrator adds the webhook under the developer settings and points it at us. From then on a completion produces a certificate carrying your design, on your own domain, written to blockchain at the moment of issue.
- Nothing to build. The completion webhook is part of LearnWorlds, so connecting TRUE is configuration.
- Signed and retried. LearnWorlds signs each delivery and retries a failed one, so a certificate is not lost to a bad minute on the network.
- Then it runs itself. Every completion issues a certificate, for every student.
How does the LearnWorlds certificate integration work?
LearnWorlds knows when a student completes, and its webhook system exists so another tool can act on it. TRUE is the tool on the other end: it checks the signature, issues the certificate against the matching design and delivers it to the student.
1
Add the webhook in LearnWorlds
An administrator opens the developer settings, chooses the course completion event and pastes in the address we provide. LearnWorlds also lets you trigger it from its automation builder if you prefer.
2
We verify each delivery
LearnWorlds signs what it sends. TRUE checks that signature before issuing, so nothing can be issued by somebody pretending to be your school.
3
Certificates issue themselves
On completion the student receives a branded, blockchain secured certificate with a permanent verification link. Nobody has to trigger it.
What does the certificate carry?
The student name, the course, your school and the date it was issued, written to blockchain at the moment of issue so it cannot be edited or backdated afterwards.
- Student name and course. Taken from the LearnWorlds completion itself, so it matches your course exactly.
- Your organisation. The certificate is branded as yours and lives on your own domain.
- Date of issue, fixed. Written to blockchain at issuance, which is what makes backdating impossible.
- A permanent verification link. An employer confirms it by opening the link or scanning the QR code, without contacting you.
What has to be in place before it can be switched on?
A LearnWorlds plan that includes the API and webhooks, administrator access, and a certificate design. LearnWorlds puts webhooks on its Learning Center plan and above, so it is worth checking which plan you are on before you start.
- A plan that includes webhooks. LearnWorlds makes the API and webhooks available from its Learning Center plan upwards.
- LearnWorlds administrator access, which is what the developer settings need.
- A certificate design, built by us to your profile or adapted by you from an existing template.
What does a student receive?
A branded, animated certificate delivered by email, on your own domain rather than ours. It carries a QR code and a permanent verification URL, so anyone can confirm it without contacting you, and it goes onto a LinkedIn profile in one click.
- Beautifully designed. Animated, branded and interactive rather than a static PDF.
- A shareable link. One URL that works in an email signature, a portfolio or a CV.
- QR code verification. An employer, a client or a regulator confirms the credential instantly.
- LinkedIn ready. Added to a profile in one click, which puts your name in front of their network.
- Blockchain secured. It cannot be edited, forged or backdated after issue.
How is student data handled?
LearnWorlds passes the student name, email address and the course details to TRUE, which is what a certificate needs to exist. The delivery is signed, so we can prove where it came from.
TRUE is hosted in the EU, and we sign a data processing agreement with you before anything is switched on.
How much has TRUE issued for organisations like yours?
More than 500,000 documents for over 200 organisations in 15 or more countries, and credentials shared by their recipients have produced over 100 million marketing impressions. These are TRUE platform figures, not third party research.
500K+ Documents issued
200+ Organisations
15+ Countries
100M+ Marketing impressions
Is a LearnWorlds completion on its own enough?
It proves the course was completed inside your school, which is enough internally. What it cannot do is prove anything to somebody outside it, and that is the part the connection adds.
| Capability | Completion on its own | Completion with TRUE connected |
|---|---|---|
| Proof outside your organisation | The reader has to take it on trust | A permanent verification link anyone can open |
| Tamper proof | No | Yes, written to blockchain at issue |
| Lives on your domain | No | Yes, branded on your own domain |
| LinkedIn shareable | A file to attach | One click add to LinkedIn |
| Effort per participant | Manual handling for anything formal | None, it issues on completion |
| If a delivery fails | Not applicable | LearnWorlds retries, so the certificate still issues |
| Analytics | None | Views, shares and verifications tracked |
What do LearnWorlds administrators ask about this?
Mostly which plan they need, whether anything has to be built and what happens if a call fails. Learning Center or above, nothing, and it is retried.
Does the LearnWorlds integration have to be built?
No. The course completion webhook is part of LearnWorlds. Connecting TRUE is adding one webhook and pointing it at the address we give you.
Which LearnWorlds plan do we need?
One that includes the API and webhooks. LearnWorlds makes those available from its Learning Center plan upwards, so it is worth checking your plan before you start.
What happens if a delivery fails?
LearnWorlds retries it, with a growing gap between attempts. A short outage on either side does not cost a student their certificate.
How do you know the call really came from us?
LearnWorlds signs every delivery and TRUE checks that signature before issuing anything.
Do participants need a TRUE account?
No. The certificate arrives by email with a unique link. No login, no account and no app.
Can the certificate carry our own design?
Yes. We build the design to your graphic profile, or you adapt one from an existing template. The certificate is branded as yours and lives on your own domain.
Can we issue certificates for courses that already finished?
Yes. Earlier completions can be issued as a batch, so a backlog does not have to be handled by hand.
What does a recipient do with the certificate?
Share it. It is a link rather than a file, so it goes on a LinkedIn profile in one click and into an email signature or CV, and every share points back to a verification page carrying your name.
Ready to switch it on?
We prepare your certificate design and give you the address for the webhook, and the next student who completes receives a verifiable credential.