About Checkr
Iru reads candidate, report, and package metadata from Checkr’s REST API using HTTP Basic: username = Secret API key, password empty - effectivelybase64(api_key:).
How It Works
Checkr’s REST API uses HTTP Basic over HTTPS: the Secret API key is the username and the password is left empty, so the header isAuthorization: Basic base64(api_key:).
| Detail | Value |
|---|---|
| Category | Background screening |
| Authentication | Basic (API key + empty password) |
Prerequisites
- Dashboard access to copy production vs staging keys as appropriate.
Connect Checkr to Iru
- Checkr
- Iru Compliance
Complete this tab before you connect the source in Compliance.
Open the Checkr Dashboard
Sign in to the Checkr Dashboard with an account that can view API credentials.
Open Account Settings
From the Dashboard, go to Account Settings (or the gear Settings entry your tenant uses for organization-wide configuration).
Open Developer Settings
Select Developer Settings (or API / Developers, depending on Checkr UI labels).
Pick the right environment
Confirm whether Iru should use production or staging data, then locate the Secret Key (or Secret API key) for that same environment.
Copy the Secret Key
Copy the Secret Key and store it like a password. In Iru you will paste it as the Username for HTTP Basic auth and leave Password blank, as on the Iru Compliance tab.
Continue on the Iru Compliance tab.
Troubleshooting
Nothing opens when you turn the source on
Nothing opens when you turn the source on
Check pop-up blocker settings for the Iru site and try again.
401 Unauthorized
401 Unauthorized
Related Articles
Sources Management
Browse and manage every Compliance source.
Getting Started With Compliance
Frameworks, actions, and Artifacts.
Iru Overview
How Endpoint, Compliance, and Identity fit together.
Artifacts Management
Upload, review, and organize evidence from sources and actions.