A Step-by-Step Guide to Integrating Sertifier’s REST API for Seamless, Real-Time Credential Issuance and Delivery
Sertifier gives you a REST interface that lets your own backend create and deliver digital credentials the instant a learner completes a course. Each credential lives inside a Campaign. A Campaign links three things: the visual Design, the descriptive Detail you want printed on the certificate, and the Email Template that sends the finished credential to the recipient. Once you can reference a Campaign by its campaignId, issuing the credential becomes a single request.
1 | Begin with the documentation introduction
Open the Introduction page of the public docs at https://sertifier.docs.apiary.io/#introduction.
That page explains:
- where to find your personal API key
- the base URL you will call from your server
- the general request and response format used by every endpoint
Reading that one section is all you need before you start writing code.
2 | Choose the right Campaign workflow
Fixed course catalogue
If each course in your platform should always trigger the same certificate, create those Campaigns once in the Sertifier web dashboard. Copy the resulting campaignIds into your own database. Whenever your learning system detects that a learner has passed the course, look up the stored campaignId and move to Step 3.
Dynamic catalogue
If you launch new courses or micro‑trainings regularly, hard‑coding Campaign IDs quickly becomes unmanageable. Instead:
- Create a single reusable Design and Email Template in the Sertifier UI.
- Each time your platform opens a brand‑new course, call the AddCampaign endpoint (see doc link), passing the Design ID and Email Template ID.
- Store the campaignId that comes back in the response.
- Use that campaignId whenever a learner finishes the new course.
Creating a Campaign this way adds only a few hundred milliseconds to the flow, so learners never notice the extra step.
3 | Issue a credential with one request
Send a POST request to Campaign/AddCredentials (see doc link) that includes:
- campaignId – the container you created in Step 2
- email – the learner’s address
- name – the learner’s full name
- any extra key–value pairs you want merged into the template (for example: score, cohort, or completion date)
Sertifier immediately:
- builds the certificate image and metadata
- emails the credential using your chosen template
The API response includes a permanent credential URL you can log or display in your own user interface.
4 | Build a robust integration
- Save campaignIds in your own database. Avoid an extra round‑trip to Sertifier every time you need to issue a credential.
- Prevent duplicates. If your completion webhook might fire twice, check an idempotency key such as (enrolment ID + campaignId) before you call AddCredentials again.
- Protect your API key. Store it in a secure secrets vault, rotate it when staff change, and never embed it in client‑side JavaScript.
5 | Need tailored guidance?
Email support@sertifier.com and let us know a few times that suit you. Our integrations team will gladly schedule a call, review your use case, and map out the exact request sequence that fits your stack.
With these steps in place, you can move from manual CSV uploads to a fully automated, real‑time credentialing pipeline in just a few lines of code.