Learning & Training · Integration

Certifier

Add Certifier to your product for your customers, and give your AI agents governed access to it.

Certifier issues digital certificates and badges, and its API at api.certifier.io/v1 requires both a bearer access token and a Certifier-Version header, so requests that omit the version header fail even with a valid token. Credentials are always created inside a credential group, which carries the design, the expiry policy and the set of custom attributes such as course name, so you cannot issue anything until a group exists and your attribute names match the group's definition exactly. A credential starts as a draft and only becomes a real, verifiable record when POST /v1/credentials/{id}/issue runs, and only drafts can be issued, so a retry against an already issued credential is an error rather than a no-op. There is a combined /v1/credentials/create-issue-send endpoint that does all three steps at once, which is convenient but leaves no draft state to inspect before the recipient is emailed. Issuing and sending are separable, so you can mint credentials in bulk and deliver them later. fastn holds each customer's access token, sets the version header, and keeps the connection maintained as Certifier revises the API.

Start freeBook a demo

In your product

Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.

Let a customer connect their own Certifier account so completing a course in your product issues a certificate under their brand.

Issue credentials in bulk at the end of a cohort and hold them as drafts until the customer approves the list.

Read back issued credentials so your product can show a learner their certificate and verification link.

Revoke or expire a credential from your app when a customer's compliance record lapses.

For your AI agents

Governed, audited access for the agents you build, through the MCP server.

Let an agent create and issue a credential for a named recipient in an approved credential group, with the credential ID, recipient and tenant written to a per-tenant audit log.

Have an agent search credentials in a group and report which are still drafts rather than issued.

Let an agent check expiring credentials for a cohort and draft the renewal batch without sending it.

Example prompt

Which certificates from our March cohort are still sitting as drafts and were never issued?

Set up Certifier in 4 steps

  1. 01Enable the Certifier connector from your fastn dashboard.
  2. 02Have each customer authorise their own Certifier account, so calls run under their credentials rather than a shared key.
  3. 03Decide which learners, training records and credentials your product needs, map those fields, then enable the actions and triggers you want.
  4. 04Call it from your product and expose it to your agents through the same governed connection.

Why teams use the Certifier integration

What you get by embedding it with fastn instead of building it yourself.

  • Ship a Certifier integration without building it. Your customers connect their own Certifier account inside your product and work their learners, training records and credentials there, with no per-customer code on your side.
  • Handle the part that actually costs time: completion records get used as compliance evidence, so they have to be accurate and attributable. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Certifier update is not your on-call problem.
  • One integration serves your product and your agents. The same governed Certifier connection powers in-product features and gives AI agents scoped, audited access, so you keep training records current without chasing spreadsheets without wiring it twice.

Used by these teams

HR & People Ops

Compare with

Canvas LMSBridgeBrainshark

Often used alongside

Tools the same teams tend to run next to Certifier, across other categories.

SlackNotionBoxDocusign

Certifier integration FAQ

How do I add a Certifier integration to my product?

Enable the Certifier connector in your fastn dashboard, then let each customer authenticate their own Certifier account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Certifier client code in your app and no per-customer branch in your codebase. Setup is 4 steps.

Do my customers each connect their own Certifier account?

Yes. Every connection is scoped to the individual customer, so each authorises their own Certifier account and only ever sees their own learners, training records and credentials. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.

Can AI agents use this Certifier integration?

Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Let an agent create and issue a credential for a named recipient in an approved credential group, with the credential ID, recipient and tenant written to a per-tenant audit log.

Who maintains the Certifier integration?

fastn does. When Certifier changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.

Can my product enrol a learner or award a credential in Certifier automatically?

Yes. An event in your product can enrol someone, assign a course, add them to a training path, or issue a credential in the customer's own Certifier account, so training and recognition follow what actually happened rather than a manual upload.

Can I read completion and credential records back out of Certifier?

Yes, scoped per tenant and audited. Completions and issued credentials are frequently used as compliance evidence, so the read is logged and attributable rather than a bulk export nobody can trace.

What can I build with the Certifier integration?

A common starting point: let a customer connect their own Certifier account so completing a course in your product issues a certificate under their brand. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.

How much does the Certifier integration cost?

It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Certifier does not change your per-connector cost. You can start free with 3 connected accounts.

Add Certifier to your product

Start free with 3 connected accounts. No sales call required, and no per-customer integration code.

Start freeRead the docs
← All integrations