Not all background checks are the same; while the government court data is universal, the mechanisms to access that data vary wildly from automated searches to manual court-runners.
This means the speed, cost, and accuracy of reports vary from provider to provider.
I should be clear that I’m not unbiased, as an engineer at GoodHire, but after managing dozens of API integrations with companies like TriNet, Lever.co, BambooHR, ZipRecruiter, and beyond, I’ve learned how to make an employment screening API work well.
On top of that, the APIs used to access reports vary. With that in mind, there are three things you should pay attention to when choosing a vendor:
Tech Stack and API Design
To avoid spending lots of unnecessary time on an integration, select an API that has been well-documented and tested. Beware of legacy platforms using outdated and insecure technologies. Make sure the API you select is RESTful, provides HTTPS endpoints, and requires API keys.
Think carefully about the full-cycle customer experience and make sure your API can support them every step of the way. Some key functions that you might want include:
- Order / Retrieve Reports - Of course, you want to be able to trigger and receive API calls for the check itself. This is the main function, and this is where most APIs stop.
- Create Account - Provision access for your users automatically through the API thus eliminating paperwork.
- Create Sub-Account - If your app will be used by businesses (like HR platforms), you’ll need to create sub-users.
- Define Reports - there is no one-size-fits-all report for all customers. You might want to let your customers build a “bundle” of reports during signup.
- Customer Credentialing - Under the law, any background check vendor must collect and verify certain customer data to prove it’s a legit business. How does this happen?
- Reject / “Adverse Action” - If a background check has negative results, employers need to follow a legal process to reject the candidate. It’s quite complex with different state and county laws.
Trust and Compliance
Adding background checks to your app means that you’ll be covered under regulations, including the FCRA (Fair Credit Reporting Act) of the USA. How you manage your compliance is key to ensuing a successful integration.
- State and National Laws - Background checks are affected by overlapping state and national laws passed in 2017. If you use a screening provider that’s not in-compliance, you open yourself to legal issues.
- Security - Your background check API will need to collect lots of personal information about your customer. While you might not be legally responsible for a breach, what happens if all your background checks are breached or leaked? (note: several of the largest providers have already been breached) . GoodHire is paranoid and SOC2 certified.
- Partner Support - What happens when there is an issue? Does your partner provide support to your customers as well as your team? GoodHire relies on API partners for business success, so we’re ready to help you if any issues arise with dedicated support.