Skip to main content

Issue Shareable Certificates through Certopus - Article

Connect Certopus certificate designs with Eurekos issuance criteria, align expiration and understand delivery, storage and layout restrictions.
Updated: 14 Nov 2026
7 min read

Summary

Use Certopus when a training program needs externally verifiable, shareable certificates while Eurekos remains responsible for deciding who qualifies. This can support partner credentials, professional development and customer accreditation without maintaining a separate manual issuance list.

The supported workflow uses a Certopus certificate design selected through the Eurekos certificate layout. Align the design, eligibility rules and expiration across both systems.

Use this article to:

  • Prepare and connect the Certopus certificate context
  • Choose the correct layout and dynamic content
  • Verify issuance, recipient delivery and the stored certificate

Business Context

A partner or customer certification program often needs two connected outcomes: a reliable decision that the learner qualifies, and a credential the learner can present outside the training platform. Eurekos manages the training, assessment and certificate criteria. Certopus provides the branded credential and its external verification and sharing experience.

For example, a distributor’s technician can complete the required learning in Eurekos and receive a branded Certopus certificate. The training team retains the certificate record in Eurekos, while the technician can present the credential to a customer or share it through LinkedIn. This reduces manual issuance work and supports consistent branding across a growing certification program.

SystemResponsibility
EurekosLearning activities, completion and assessment logic, eligibility criteria, and the resulting certificate record
CertopusCertificate design and branding, credential generation, provider email delivery, verification and external sharing

Keep this division clear when troubleshooting. A learner who has not met the Eurekos issuance criteria has a different problem from a learner whose certificate was generated but whose Certopus email did not arrive.

Feature Overview

Once connected, Certopus becomes a certificate Layout choice in Eurekos. Use that layout when the certificate should use the design and credential context maintained in Certopus.

CapabilityWhat the reader or learner gains
Certopus designs in EurekosSelect the provider’s certificate context while keeping training eligibility in Eurekos
Automatic issuanceGenerate the credential when the configured Eurekos issuance criteria are met
Provider deliverySend the learner a Certopus email containing the credential link
Stored evidenceRetain the PDF and certificate expiration information in Eurekos
External sharingLet the learner view the credential online and share it through the supported Certopus experience, including LinkedIn

Data Flow and System Responsibilities

The integration connects eligibility to credential delivery. It does not require a separate manual list of people who passed.

ExchangeInformation or outcome
Eurekos → CertopusThe issuance trigger, learner information and selected certificate context
Certopus → EurekosThe generated certificate PDF and certificate metadata, including expiration
Certopus → learnerThe provider’s certificate email and online credential link

Eurekos stores the resulting certificate in the user profile. The certificate email is sent by Certopus, so investigate that delivery route separately from Eurekos System Email.

Configuration

Open Settings → Third party integrations → Certopus after preparing the certificate context in Certopus. The API key establishes the connection; the certificate’s Appearance choices determine which provider context is used.

Step 1: Prepare Certopus Environment

  1. Sign in to the intended Certopus account
  2. Create or select the Organization
  3. Create the Event that will provide the certificate context
  4. Design the certificate and configure its dynamic tokens
  5. Review the category and expiration choices needed for that certificate

Use names the certification team can recognize later. A Certopus Event is the provider’s certificate context; it is not automatically the same record as a scheduled Eurekos Event.

Step 2: Obtain API Key

  1. Open your Certopus profile settings
  2. Navigate to API Center
  3. Copy the REST API Key for the intended account

Keep the key in your organization’s approved credential-management process.

Step 3: Connect in Eurekos

  1. Open Settings → Third party integrations → Certopus
  2. Enter the API key
  3. Select Save

The connection makes the supported Certopus layout and certificate-context choices available. Verify them during certificate creation rather than treating a saved key as proof that the complete learner journey works.

Using Certopus in Eurekos

Creating a Certopus Certificate

  1. Open Course Administration → Certificates and select Create certificate
  2. Select Certopus in Layout
  3. Complete the provider choices in Appearance
Appearance fieldWhat to select
OrganizationThe intended organization returned by Certopus
EventThe Certopus certificate context prepared for this program
CategoryThe category returned by Certopus for the intended certificate context

Together, these values identify the provider context used to issue the credential. Choose and verify the intended layout before issuing the first certificate. A post-issuance layout lock can prevent later changes to Layout, even when the API connection is working.

Defining Issuance Criteria

Define eligibility in Eurekos using the certificate’s supported issuance criteria, such as Course completion, assessment results or Activity completion. The chosen rule should represent the qualification you are certifying. When that rule is met, Eurekos triggers Certopus to generate the credential.

Certificate Issuance and Delivery

Once the issuance criteria are met, Certopus generates the certificate and sends its email to the learner. The learner can open the online credential and use the supported sharing options. Eurekos stores the PDF and expiration information for the platform’s certificate record.

Generation can take a few seconds. A short delay before Get certificate succeeds is different from a failed eligibility rule. If availability does not resolve, check the selected provider context and whether its design is a Certificate rather than a Badge.

Tokens and Dynamic Content

Use tokens when the same design must show the correct learner, qualification and dates for each issued certificate. Keep the exact token syntax in the Certopus design.

Certopus Tokens

TokenValue
{Name}Participant name
{credential.issueDate}Certificate issuance date
{credential.expiryDate}Certificate expiration date

Eurekos tokens

The integration also provides Eurekos context for the Activity and its instructors.

TokenValue
{eurekos.activity}Activity title
{eurekos.instructors}Instructor names resolved from the certificate’s module or Activity context

For a module-level certificate, module instructors are used first, with Activity instructors as the fallback when the module has none. For an Activity-level certificate, Activity instructors are used; module instructors are not searched. Test the design in the context where the certificate will actually be issued.

Important Considerations

These conditions can look similar to a connection failure but need different checks.

ConditionWhat it means and what to do
Certificate generation is still processingAllow a short time for the provider to generate the credential, then retry Get certificate
Expiration differs between systemsConfigure matching expiration in both Certopus and Eurekos so the credential and platform record stay consistent
The provider context uses a BadgeUse the intended Certificate design; a Badge context can produce the same temporary-unavailability warning
Layout is locked after issuanceRespect the post-issuance safeguard rather than treating it as an API connection problem

Governance and Best Practices

Agree ownership of the design and the qualification rule before launch. This keeps a branding change, a training-policy change and a delivery investigation from being handled as the same task.

Working practiceWhy it matters
Design the certificate in Certopus firstPrepare the branding, provider context and dynamic fields before connecting the Eurekos issuance flow
Define eligibility in EurekosKeep the qualification decision tied to the intended training and assessment evidence
Keep names and contexts recognizableHelp maintainers choose the correct Organization, Event and Category
Align expiration settingsAvoid different validity expectations in the provider credential and Eurekos record
Test tokens in their real issuance contextConfirm the learner name, Activity and correct instructor fallback
Test delivery and stored evidenceCheck the provider email, online credential, PDF and expiration together

Verify the certificate journey

Use a representative certificate and recipient before launching the program. A saved API key establishes configuration, not successful delivery.

CheckExpected result or evidence
Certificate contextOrganization, Event and Category select the intended Certopus certificate design
EligibilityEurekos issues only when the configured criteria are met
Dynamic contentThe learner name, Activity and relevant instructors resolve correctly
Recipient experienceThe Certopus certificate becomes available and its provider email reaches the intended recipient
Stored evidenceThe PDF and expiration recorded in Eurekos match the issued certificate
Existing issued layoutAny layout lock is respected rather than treated as a failed connection

Troubleshooting

ProblemWhat to check
Certopus is unavailable as a layoutAPI configuration, certificate permissions and whether an issued certificate has locked Layout
Get certificate shows a temporary warningAllow provider generation time, then check the selected Certopus Event and that it uses a Certificate rather than Badge design
No certificate email arrivesCertopus delivery and recipient details; certification emails originate from Certopus
Expiry differs between systemsMatch the expiry configuration in Certopus and Eurekos
Instructor text is unexpectedModule versus Activity certificate context and the instructor fallback

Third Party Integrations

FAQ