Sana Integration
Sana can issue TRUE certificates when someone finishes
Sana already streams learning events as they happen, over xAPI and over webhooks, and it documents both. Point a completion event at TRUE and the learner gets a branded, blockchain secured certificate on your own domain, with a permanent link they can share. There is nothing to build on either side.
TL;DR
Sana's own documentation covers streaming real time learning events to an external system, over xAPI statements or webhooks, with OAuth 2.0 for the connection. Either route carries what a certificate needs: who completed, what they completed and when. We agree which of the two suits your setup, you point it at the address we provide, and from then on a completion produces a certificate carrying your design, written to blockchain at the moment of issue.
- Nothing to build. Sana already streams completion events, so connecting TRUE is configuration.
- Two routes, one result. xAPI or a webhook, whichever fits how you already run Sana.
- Then it runs itself. Every completion issues a certificate, for every learner.
How does the Sana certificate integration work?
Sana knows the moment somebody finishes, and it is built to tell other systems about it in real time. TRUE listens for that completion, issues the certificate against the matching design and delivers it to the learner, with no export step and nobody in the middle.
1
Choose the route with us
Sana can send an xAPI statement or a webhook. Which one is right depends on what else you already stream out of Sana, so we pick it with you rather than for you.
2
Connect it once
Sana uses OAuth 2.0 for the connection, so the credentials are issued and revoked on your side. You point the completion event at the address we provide.
3
Certificates issue themselves
On completion the learner receives a branded, blockchain secured certificate with a permanent verification link. No administrator action is needed.
What does the certificate carry?
You decide what the certificate carries. Most issuers start with the learner name, what they completed, your organisation and the date it was issued, written to blockchain at the moment of issue so it cannot be edited or backdated afterwards.
- Your document, your fields. Add what matters to you and leave out what does not. A certificate can run to several pages when there is more worth recording.
- Learner name and course. Taken from the Sana completion event itself, so it matches your content 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?
Administrator access in Sana and a certificate design. The technical side is one connection and one event. The design is either one we build to your graphic profile or one you adapt yourself from a template.
- Sana administrator access, which is what setting up the connection needs.
- A decision on xAPI or a webhook, which we make with you in one short conversation.
- A certificate design, built by us to your profile or adapted by you from an existing template.
What does a learner 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.
- Animated and branded. An interactive page in your design 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. Anyone can run the same check at TRUE Verify.
- LinkedIn ready. Added to a LinkedIn profile in one click.
- Blockchain secured. It cannot be edited, forged or backdated after issue.
How is learner data handled?
Sana passes the learner name, email address and the completion details to TRUE, which is what a certificate needs to exist. The connection uses OAuth 2.0, so access is granted and withdrawn on your side.
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 900,000 documents for over 200 organisations in 15 or more countries, and credentials shared by their recipients have produced over 100 million marketing impressions.
500K+ Documents issued
200+ Organisations
15+ Countries
100M+ Marketing impressions
Is a Sana completion on its own enough?
It proves the course was completed inside your organisation, which is enough internally. What it cannot do is prove anything to somebody outside it, and that is the part the connection and TRUE add.
| 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 |
| Access control | Not applicable | OAuth, so you grant and withdraw it yourself |
| Analytics | None | Views, shares and verifications tracked |
What do Sana administrators ask about this?
Mostly whether to use xAPI or a webhook, whether anything has to be built and who controls access. We choose it with you, nothing, and you do.
Does the Sana integration have to be built?
No. Sana already streams learning events to external systems, over xAPI and over webhooks, and both are documented. Connecting TRUE is configuration.
Should we use xAPI or a webhook?
Whichever fits what you already stream out of Sana. If you have an xAPI setup running, use that. If you do not, a webhook is the shorter path. We decide it with you in one conversation.
Who controls the connection?
You do. Sana uses OAuth 2.0, so the access is granted from your side and can be withdrawn there too.
Does it cover everything in Sana or only courses?
We start with the completion event that matters to you and widen from there. Not every completion needs a certificate, so the events that issue one are chosen with you.
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, agree the route with you and give you the address to point it at, and the next learner who finishes receives a verifiable credential.