Certopus - Article
Summary
Integrate Certopus with Eurekos to automatically issue digital certificates and badges based on learning completion, including credential delivery, storage, and LinkedIn sharing.
In this article you will learn:
- How Certopus integrates with Eurekos certificate functionality
- How certificates are created, issued, and delivered
- How data flows between Eurekos and Certopus
- How to configure and use the integration step by step
Business Context
The Certopus integration extends Eurekos from a learning platform into a certification and credentialing system, enabling organizations to issue externally verifiable digital certificates and badges.
While Eurekos manages:
- Learning activities
- Completion logic
- Assessment and eligibility
Certopus manages:
- Certificate design and branding
- Credential verification
- External sharing (e.g. LinkedIn)
This separation is important. Eurekos determines who qualifies for a certificate, while Certopus ensures that the certificate is professionally issued, verifiable, and shareable outside the platform.
From a business perspective, this enables:
- Scalable certification programs
- Increased learner value through verifiable credentials
- Stronger brand visibility via external sharing
- Consistent and automated certificate issuance
Feature Overview
Once integrated, Certopus becomes available as a certificate layout option inside Eurekos.
This means:
- Certificates are still created and managed in Eurekos
- Certopus provides the design, issuance, and delivery layer
What the integration enables
- Use Certopus certificate templates inside Eurekos
- Automatically issue certificates when criteria are met
- Send certificates directly to users via email
- Store certificate PDFs in the user profile
- Allow users to share certificates on LinkedIn
As described in the Help Center draft, the Certopus template becomes available as a selectable layout when creating certificates in Eurekos
Data Flow and System Responsibilities
Understanding how the two systems interact is critical.
Eurekos → Certopus
- User data (name, activity context)
- Certificate issuance trigger (based on criteria)
- Selected certificate configuration
Certopus → Eurekos
- Certificate PDF
- Certificate metadata (including expiry date)
Additionally:
- Certopus sends the certificate email directly to the user
- Eurekos stores the certificate in the user profile
⚠️ Important distinction:
- Eurekos controls eligibility
- Certopus controls issuance and delivery
Configuration
The integration is configured in Settings → Third party integrations → Certopus.
Step 1: Prepare Certopus Environment
Before connecting Eurekos, Certopus must be configured.
In Certopus:
- Log in to your account
- Create an Organization
- Create an Event (this represents a certificate context)
- Design a certificate template
- Configure tokens if needed
This setup defines what Eurekos will later reference.
As shown in the internal documentation, certificates are tied to Certopus events and layouts
Step 2: Obtain API Key
- Go to your Certopus profile settings
- Navigate to API Center
- Copy your REST API Key
This key is used to connect Eurekos to your Certopus account
Step 3: Connect in Eurekos
- Go to Settings → Third party integrations → Certopus
- Paste the API Key
- Click Save
Once saved:
- Eurekos connects to Certopus
- Certificate layouts and configuration options become available
Using Certopus in Eurekos
After configuration, Certopus becomes part of the certificate creation workflow.
Creating a Certopus Certificate
- Go to Course Administration → Certificates → Create certificate
- In Layout, select Certopus
- Configure the Appearance section:
| Field | Description |
|---|---|
| Organization | Certopus organization |
| Event | Certificate context |
| Category | Certificate type |
These values are pulled directly from Certopus and determine which certificate is issued
Defining Issuance Criteria
Certificate eligibility is defined entirely in Eurekos.
Examples include:
- Course completion
- Test score thresholds
- Activity completion
When a user meets the criteria:
- Eurekos triggers certificate issuance
- Certopus generates the certificate
Certificate Issuance and Delivery
Once triggered:
- Certopus generates the certificate (≈ a few seconds)
- The user receives an email from Certopus with a certificate link
- The certificate can be:
- Viewed online
- Shared on LinkedIn
- A PDF copy is stored in the Eurekos user profile
⚠️ Important:
- Emails are sent by Certopus, not Eurekos
- Eurekos stores the certificate for internal tracking
Tokens and Dynamic Content
Certopus supports dynamic tokens for certificate content.
Certopus Tokens
- {Name} → Participant name
- {credential.issueDate} → Issue date
- {credential.expiryDate} → Expiry date
Eurekos Tokens
- {eurekos.activity} → Activity title
- {eurekos.instructors} → Instructor(s)
Instructor resolution depends on context:
- Module level → Module instructor
- Activity level → Activity instructor
Important Considerations
Certificate timing
If a user clicks Get certificate before Certopus finishes generating it:
- A temporary warning message appears
- The certificate becomes available shortly after
Expiration consistency
If certificates have expiration, expiry must be configured in both Certopus and Eurekos. This ensures consistent behaviors across systems.
Certificate type alignment
If configured as a badge instead of certificate in Certopus:
- Eurekos may display a warning
- Ensure alignment between systems
Governance and Best Practices
- Design certificates in Certopus first → Treat Certopus as the design and branding layer.
- Define issuance logic in Eurekos → Always control eligibility through Eurekos criteria.
- Keep naming and structure aligned → Ensure Certopus “Events” match Eurekos course/activity structure.
- Test the full flow before launch → Validate:
- Certificate creation
- Email delivery
- Profile storage
- Align expiration settings → Always configure matching expiry rules in both systems.
- Use tokens consistently → Ensure dynamic fields (name, activity, instructor) are correctly mapped.