Skip to main content

Integrations

Connect Qualeron to the systems you already run

Your team's channel, your own systems through signed webhooks and the API, fees on your own Stripe account, and signed badges for your credential holders. Each integration names what it reads, what it sends and what it never touches, and says honestly whether you can use it today.

Illustrative example: a certifying body's connection to its team's channel, #certification: it sends the credentials issued, its last test was delivered and its health check passed, and it was authorized in the other system, so Qualeron never sees that password; beside it, a scoped, read-only API key, and the body's own system's last webhook deliveries — a seat confirmed, a result released, a credential issued — each signed and answered with status 200; a failed delivery is retried on a schedule and can be replayed. The readouts: 8 integrations available today, 17 listed, in 10 categories, every delivery signed.

How it works

Connected, and on the record

8 integrations are available on Qualeron today, with more being built. Whichever you use, the rules are the same.

  • You choose what it sendsEach connection has its own events, and names or scores leave Qualeron only where the integration's page says they do.
  • Nothing hiddenYou authorize in the other system, so Qualeron never sees that password. What Qualeron holds to reach it is stored encrypted and never shown.
  • Every delivery recordedEach delivery, test and health check is logged with its result. A failing connection says so in Qualeron instead of going quiet.
Illustrative example: a credential issued by Meridian Certification Board and recorded by Qualeron arrives in three places: a message in the team's channel, a webhook the body's own system received with its signature verified, and a signed Open Badges credential for the holder.

For software companies

Offer your app to certifying bodies

If your product serves certifying bodies, you can list an app in the catalog they see in Qualeron. When a body installs it, Qualeron issues it a scoped, read-only key and a signed webhook for the events it needs, and the body hands them to your app.

  • Qualeron reviews every listing before any body sees it: who you are, what the app does, what it reads, and your privacy policy and support.
  • A body installs your app itself and can disconnect it at any time; its key is revoked and its webhook turned off at once.
  • Your app reads only what the listing names, with a read-only key. Writing through the API is not offered yet.
  • The listing names your company as the one that builds and supports the app. Qualeron claims no partnership.

Tell us what your app does, what it needs to read, which events it listens for, and where your privacy policy and support are.

Questions

Integrations, plainly

What does an integration cost?

What the published price book says. Stripe, Open Badges 3.0 and CE provider reporting are included in every plan. The API and webhooks are included from Professional. Standard integrations such as Slack and Microsoft Teams are included in Professional (2) and Scale (5), with more at $1,000 a year each; Enterprise is reasonable use. A custom connector is quoted from $3,000, plus $1,000 a year maintenance.

Is every integration here available today?

No, and each one says so. Available means a certifying body can use it now. Coming soon means Qualeron has built it and is switching it on. In development means it is being built. Planned means it is on the roadmap with no date promised.

Does Qualeron have partnerships with these companies?

No partnership is claimed on these pages, and no other company's logo is used. Product names are their owners' trademarks.

Where does a certifying body connect them?

In Qualeron, under Settings, then Integrations. Owners and administrators connect, pause and disconnect; every change and every delivery is recorded there.

What if the system we use is not listed?

Ask for it. Requests from many bodies move an integration up the list, and a custom connector can be built and maintained for one body, quoted after a written scope.

Can another company list its app?

Yes. A company whose product serves certifying bodies can ask to list an app. Qualeron reviews the listing before any body sees it, and an app reaches only what a body grants when it installs it: a read-only key and signed webhooks. Apps are offered inside Qualeron, labeled with the company that builds and supports them.

Not listed?

Tell us the system you need

Name it and say what it should do. Requests from many bodies move an integration up the list; one only your body needs can be built as a custom connector.

Privacy choices

Control optional diagnostics and site-journey measurement. Essential technologies remain active when needed to provide a requested function.

Essential technologies

Authentication, CSRF and form security, anti-abuse controls, checkout and payment integrity, privacy-choice storage, and interface state you asked for.

Always active

Optional diagnostics

Limited client-error events and first-touch, form-journey measurement used to find broken experiences and improve the website. Not advertising.

Advertising and cross-context behavioral tracking

Qualeron does not deploy targeted-advertising cookies or cross-context behavioral advertising trackers on qualeron.com.

Not used

Read Privacy & Cookies