Integrations

Issue credentials from the systems you already use

Connect Certrust to your student records, learning platform or HR system. Your records stay where they are, and the right people get a verifiable credential the moment they earn it, without spreadsheets or uploads.

How it works

  1. 1

    Create an API key

    In Certrust, go to Manage → API keys, name the key and choose what it may do. It takes a minute.

  2. 2

    Add it to your system

    Your IT team or provider adds the key to the system you already use: student records, a learning platform, an HR or event tool.

  3. 3

    Credentials issue themselves

    When someone passes, completes or attends, your system tells Certrust and their verifiable credential is issued and emailed to them.

Less admin, fewer mistakes

The work your team does by hand today becomes something your systems do on their own.

Universities and colleges

Today: Exporting graduate lists into spreadsheets at the end of every term.

Connected: The student records system issues each certificate as soon as a final result is recorded.

Training centres

Today: Checking the learning platform by hand to see who passed, often weeks later.

Connected: The certificate arrives the moment a learner completes the course.

Companies and HR teams

Today: Keeping compliance training and certificates in step across two lists.

Connected: The HR system issues the badge, and revokes it when it expires or someone leaves.

Events and workshops

Today: Building an attendance CSV after every event.

Connected: Check-in or attendance tools issue certificates the same day.

Your data stays where it is

There is nothing to migrate and no copy of your database in Certrust. Your system sends only what goes on the credential, at the moment it is issued. Your records system stays the one source of truth.

Stays in your systems

  • Student, learner and employee records
  • Grades, transcripts and HR files
  • Passwords and logins to your systems

Sent to Certrust

  • The recipient's name and email
  • Which achievement they earned
  • Optional details you choose to print, such as a date or location

Safe for your IT and compliance teams

Every connection is controlled by your organisation, and every action is accounted for.

Only the permissions you choose

A key can be limited to reading, issuing, revoking or managing achievements. It can never touch billing, account settings or other keys.

Revoke in one click

Stop a key instantly from the API keys page, give it an expiry date, or let it stop on its own if the person who created it leaves your organisation.

No duplicates, even on retries

If a connection drops and your system sends the same request again, Certrust returns the first result instead of issuing twice.

A record of every action

Everything done with a key is logged against that key, so you can always see which system issued or revoked a credential.

For your IT team

  • A simple HTTPS API: one request issues a credential
  • Batch issuing for whole classes or cohorts
  • Safe retries with the Idempotency-Key header
  • Open Badges 3.0 credentials that work beyond Certrust
  • Open source, so anyone can check how it works
POST /api/credentials/issue
Authorization: Bearer crt_…
Idempotency-Key: student-1042-course-7

{ "data": {
    "achievementId": 12,
    "recipient": {
      "name": "Ada Lovelace",
      "email": "ada@example.edu"
    } } }

Included in every paid plan

API keys come with Pro and Enterprise. Start free, issue your first credentials by hand, and connect your systems when you are ready.