Certn
Connect Certn to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Record your Certn connection as background check providers evidence. Automated collection is not available for this provider yet.
| Category | Background Check Providers |
| Connect with | API token |
| What a connection produces | Connection record |
Connect with an API token
-
In Certn:
- Sign in to the Certn Client Portal and open the Integrations area.
- Create a new API key there and copy it.
Where to find the other values:
- Base URL (optional): Certn's API reference gives the sandbox base URL as https://api.sandbox.certn.co/api/public/; use your production API host for live accounts.
Certn's public documentation does not cover every step.
Certn's API docs say keys are created and managed in the Integrations area of the Client Portal but do not give button labels. API keys expire after 1 year (365 days); admins get expiry notices 30, 14, 7 and 1 day(s) before. More than one active key can exist, so rotation needs no downtime. No read-only key type is documented. Certn's help-center article on API keys (help.certn.co) blocked automated access, so the exact button labels are unverified.
Source: centric-api-docs.certn.co, checked 2026-10-07.
-
On Compliance › Connectors, open Certn, click Connect, choose API token and fill in:
Field What to enter API token / Personal access token Required. Stored encrypted and never shown again. Base URL (optional) — Account / Org / Workspace (optional) — -
Click Connect with token.
Frameworks
No automated compliance test reads Certn yet, so no framework lists it. How connectors provide evidence for frameworks: Frameworks and connectors.
Related
- Background Check Providers connectors
- Compliance connectors: how connecting works, card statuses and multiple accounts
- Connector setup reference: every connector in one table
- Frameworks and connectors: how connectors provide evidence for frameworks