Overview
Checkr Integration
Connect Checkr with Sprinto to automate background verification checks, sync employee screening reports, and monitor compliance status.
Sprinto connects to Checkr using an OAuth-based authentication flow and periodically syncs candidate and report data.
Once connected:
- Sprinto fetches candidate data from Checkr
- Background verification reports are retrieved for each candidate
- Employees are matched using email IDs
- The latest report status is evaluated
- Compliance checks are updated automatically
If no background verification report is found for a staff member, Sprinto activates a check and flags it as non-compliant.
Features
- Automated sync of background verification reports
- Continuous monitoring of employee screening status
- Automatic mapping of Checkr candidates to Sprinto users
- Detection of missing background checks
- Real-time compliance status updates
- Support for OAuth-based secure authentication
Sprinto checks for Checkr integration
Following are the Sprinto checks available for Checkr integration:
| Sprinto check | Required action |
|---|---|
| Background check via Checkr should be completed | This check activates against a staff member if no background verification report is detected. To fix this check, complete the background verification for the respective staff member on the integrated service provider platform. Once done, Sprinto detects the changes and sets the check status to “Passing.” |
Prerequisites
Before connecting Checkr to Sprinto, ensure that:
- You have administrator access to your Checkr account
- Your Checkr account has active background verification data
- Employees are added in Sprinto with valid email IDs (for mapping)
What data does Sprinto collect?
| Data Type | Purpose |
|---|---|
| Candidate details | Identify employees in Checkr |
| Email ID | Map candidates to Sprinto users |
| Background verification reports | Evaluate screening status |
| Report status | Determine compliance outcome |
Permissions required
Sprinto requires the following access from Checkr:
- Read candidate data
- Read background verification reports
- Read account information
You must have admin-level access to grant these permissions.
Technical details
Authentication
- Method: OAuth 2.0 (primary)
- Alternative: API key (Basic Auth, internal support)
API usage
Sprinto interacts with Checkr APIs to:
- Fetch candidates (paginated)
- Retrieve report details
- Validate account connection
- Map report status to compliance checks
Rate limits
- Checkr API: ~600 requests per minute
- Sprinto applies internal throttling and retry mechanisms
Connect Checkr to Sprinto
- Log in to the Sprinto dashboard.
- Navigate to Settings → Integrations.
- In the All tab, search for Checkr.
- Click Connect.
- In the first drawer:
- Review the permissions and data accessed by Sprinto.
- Click Next.
- In the connection drawer:
- Click Connect Checkr.
- You will be redirected to Checkr:
- Log in using your admin credentials.
- Review the requested permissions and connect.
After successful authorisation, you will be redirected back to Sprinto and the integration will be established.
Add Checkr as a background verification source
After connecting the integration, you must configure Checkr as a background verification provider:
- Navigate to Data Library → People → Configuration.
- Click Manage next to Background verifications.
- Select Automate via BGV provider.
- Select Checkr and click Add.
Sprinto will begin syncing background verification data.
Data sync and behaviour
- Initial sync: Triggered immediately after connection
- Processing time:
- Data sync: ~15–20 minutes
- Evaluation: May take a few hours
- Ongoing sync: Periodic background updates
If required, you can manually refresh data from the People configuration section.
Error handling and troubleshooting
| Issue | Cause | Resolution |
|---|---|---|
| Authentication failure | Invalid session or revoked access | Reconnect the integration |
| Missing reports | No background checks completed | Complete verification in Checkr |
| User not mapped | Email mismatch | Ensure emails match between systems |
| Insufficient permissions | Non-admin account | Reconnect with admin access |
Additional notes
- Only employees with matching email IDs are mapped correctly.
- Background verification status is derived from the latest available report.
- Missing or incomplete reports will trigger compliance failures.
- Reconnecting the integration may be required if admin access changes.
Support
Please contact Sprinto Support If you have any queries related to the integration or need any assistance.