Softbook Certify

Certificates you can check — not a picture in a PDF

Softbook Certify is a service for issuing certificates: build a template, issue to participants one by one, by list, or through the API, and each one gets a serial number and a public page where it can be checked.

Works without an LMS and without courses.

  • No LMS, no courses
  • Checked by QR code
  • No subscription — you pay per certificate issued
A certificate with a verification QR code in Softbook Certify

A certificate nobody can check is just a picture. Anyone can draw one. Certify gives every certificate a serial number and a public check page — and it starts to mean something.

Workflows

Certificates aren't only for schools

Certify is about your case, even if you don't have an online school and never will.

Conferences and webinars

Named certificates for participants, right after the event.

Training centers

Training certificates people can check.

HR and internal training

Confirmation that an employee completed the program.

Professional communities

Membership and participation certificates.

Course creators on other platforms

Your own checkable certificate, even if the course itself isn't on Softbook.

Template

Design it once — from then on it works for every cohort

You don't pay a designer for every cohort and you don't fix five hundred files by hand: you build the template once, and the name, the course, and the date fill themselves in on issue. The visual editor puts together the background, text, images, the logo, the verification QR code, and variable fields, and you keep several templates with previews for different programs.

  • Background, text, images, logo, verification QR code
  • Variable fields — name, course, date — filled in on issue
  • Several templates for different programs, with previews
Certificate template editor in Softbook Certify

Issuing

Four ways to issue — for any scenario

You don't bend your process to fit the service: you have a list, we'll send them out; you have no emails, you give a link; you need it automatic, there's the API. You pick the method to suit the situation, and the template stays the same.

  • One by one — to a single person
  • By list plus email — you upload a list, pick a template and an email; the service generates all the certificates and sends them out. It runs in the background, with visible progress
  • An invitation link — the person collects the certificate themselves: drop it in a chat, a post, or a thank-you page. Links are grouped into campaigns and can be revoked
  • API — issued from your own system automatically: on course completion or payment, for example
Bulk certificate issue with progress in Softbook Certify

Verification

The employer opens the page — and sees the certificate is real

Your certificate stops being a picture: it no longer has to be taken on trust — which means people start taking it seriously. That's the difference between "they sent a PDF" and "I have proof." Every certificate has a serial number in the form SB-XXXXX-XXXXX-C and a public check page, and the QR code on the certificate itself leads to the same place.

  • A serial number and a public check page for every certificate
  • The QR code on the certificate leads to the same page
  • The check is open to everyone — no account needed
  • A certificate can be revoked — the check page will then mark it invalid
Certificate verification page
Longevity

The check still works five years later

Whoever received your certificate can confirm it whenever they need to — even if your conference happened once and the company closed long ago. That's exactly why the check can be trusted: it doesn't depend on whether the issuer is still around. Certificates are stored with us for life and separately from file storage, and they can't be deleted — because if the issuer could erase a certificate after the fact, the check would be worth nothing.

Certificates are stored for life

The serial number is permanent — the check page is always available

The check doesn't depend on whether the project that issued the certificate still exists

LinkedIn

The graduate adds the certificate to their profile — and their network hears about you

Your participants tell people about you themselves — for free and by choice. Usually a certificate stays in the Downloads folder and nobody sees it again; here it goes into a profile read by colleagues and employers: the certificate page has an "Add to LinkedIn profile" button, and the recipient adds it in one click.

A Softbook Certify certificate on a LinkedIn profile

Emails

The certificate comes from you, not from a service nobody has heard of

The email doesn't look like spam, so people open it: the person was expecting a certificate from your conference, and it arrives from your conference. You connect your own sending domain through DNS records (and if you have a school on Softbook LMS, you import the domain you've already verified); until the domain is connected, the emails go out from a Softbook address.

  • Your sending domain, sender name, and time zone
  • Email builder: text, buttons, images, timer
  • Several emails for different campaigns — you pick one when you issue
Email builder for sending certificates

Dashboard

You're not left guessing whether people got their certificates

After a bulk issue you see it in numbers: how many were issued, how many emails were delivered, who had an error, how many tokens are left — and failed sends are repeated in a couple of clicks. The dashboard pulls the whole picture together for the last 30 days.

  • Certificates issued, emails sent, unique recipients, token balance
  • Issue chart by source: bulk · API · manual
  • Delivery status for every recipient, with failed sends repeated
  • Top templates, invitation link funnel, activity feed
Certificate issue dashboard in Softbook Certify
Pricing

Pay per certificate issued, with no subscription

1 token = 1 certificate issued. Take a pack or a custom amount — tokens are spent as you issue and they don't expire. The bigger the pack, the cheaper each certificate.

Need a custom amount?

Tell us how many certificates you need, and get a price for that exact number.

Calculate
  • Tokens never expire — unused ones stay on your balance
  • Payment by card or from your Softbook balance
FAQ

Questions about issuing certificates

No. Certify stands on its own; no LMS required. If you do have a school on Softbook, you can reuse the sending domain you've already verified.

Not if you issue certificates for your own courses: they're already included in the LMS. Certify is for certificates that aren't tied to a course — a conference, a webinar, internal training, membership in a community.

You pay per certificate issued: 1 token = 1 certificate. In packs it starts from $0.16 per certificate, and the bigger the pack the cheaper it gets. Or pick a custom amount on the slider. There's no subscription.

Nothing happens: the serial number is permanent, the check page is always available, and there's no need to issue it again.

Yes. A revoked certificate is marked invalid on the check page.

They open the check page by link or QR code — it shows that the certificate is genuine, who issued it, and when. No account needed.

Yes, through the REST API — issuing a certificate on course completion or payment in your own system, for example.

No. Certificates are stored for life and can't be deleted — otherwise the check would be meaningless: here today, gone tomorrow.

No. Tokens you've bought don't expire: you pay for the act of issuing, and unused ones stay on your balance — you can buy a pack ahead of a future event.

The token is spent on issuing the certificate, not on sending the email. The certificate has already been issued and is sitting in your account — send the email again or pass on the link however suits you. You don't pay twice.

Issue your first certificates

Pay for the act of issuing, with no subscription. You can start with $7 — that's 25 certificates.

Customer Care — real people, in your language

Quick, to-the-point answers, around the clock.