Skip to main content

Connect Humanforce Talent (LiveHire)

Screen your candidates from inside Humanforce Talent, the recruitment platform formerly called LiveHire — the two names refer to the same product, and you'll see both in Oho and in Humanforce's own documentation. When a recruiter requests a check on a candidate in Humanforce Talent, Oho picks it up, emails the candidate a secure link to provide the credentials their role needs, and reports the result back to the candidate in Humanforce Talent.

Like SmartRecruiters, this connector doesn't import a list of people on a schedule. Each check a recruiter requests flows into Oho one candidate at a time.

Humanforce Talent is set up with Oho's help

You don't add this connector from Oho's Data Sources page. It's separate from Oho's built-in connectors and needs settings on both sides — in your Humanforce Talent account and in Oho — so you contact Oho's support team and they design and configure it with you. This guide covers what to prepare, the decisions you'll make, and what to expect.

What you'll end up with

Recruiters requesting Oho checks from the Checks & Assessments stage in Humanforce Talent. Each candidate gets an email from Oho asking for the right credentials, and once they're done, a report listing every completed credential lands on their profile in Humanforce Talent, with a link to each one in Oho.

Not the same as the Humanforce connector

This is Humanforce's recruitment product. Workers from Humanforce's workforce management product come in through a separate connector — see Connect Humanforce.

How it works​

  1. A recruiter requests a check. In Humanforce Talent, the recruiter moves a candidate to the Checks & Assessments stage of the job and picks the Oho check.
  2. Oho picks it up. Humanforce Talent tells Oho a check has been requested. Oho reads the candidate, job, and application details and works out which screening package applies.
  3. The candidate gets an email from Oho. It holds a secure link to provide the credentials that package asks for. The candidate becomes an applicant in Oho, and you can track them like any other recruitment check.
  4. The result goes back to Humanforce Talent. When the candidate completes the package, Oho posts a single report to the check in Humanforce Talent. It lists every credential completed, each with a link straight to that credential in Oho, so anyone with Oho access can open it in one click.

Before you start​

Check these before you request setup:

  • Checks & Assessments in your Humanforce Talent subscription. The integration runs through the Checks & Assessments stage and Humanforce Talent's API. Some Humanforce subscriptions don't include them, so confirm with your Humanforce account manager first.
  • A Humanforce Talent administrator, or your Humanforce contact. Someone who can ask Humanforce for API access and get changes made to your Checks & Assessments setup. Many of these changes are made by Humanforce staff, not in your own account, so loop them in early.
  • Your screening packages in Oho, one for each set of checks a role needs. See Create a screening package.
  • Which environments you want connected. Production only, or a UAT (test) environment plus production.

Step 1: Contact Oho support​

Humanforce Talent isn't one of the connectors you add from Oho's Data Sources page. It runs separately from them, so you request it through Oho's customer support team.

Email support@weareoho.com and tell us you'd like to connect Humanforce Talent. Include your organisation, whether you want UAT as well as production, and who your Humanforce contact is.

Expected outcome: your request is with Oho's team, and they'll arrange a design session with you.

Step 2: Get API access from Humanforce​

What you'll need for this step

Your Humanforce Talent administrator or Humanforce contact. This is a Humanforce-side task.

Ask Humanforce to issue Oho an OAuth2 client credential (a client ID and secret) for each Humanforce Talent environment you want connected: one for production, plus one for UAT if you're testing first. Hand the technical detail below to whoever makes the request. The client must have the listed permissions, or Oho can connect but can't see or answer check requests.

Share the secret securely

A client secret gives access to your candidates' personal details. Send it to Oho through a secure channel your IT team approves, not in a plain email, and never share it anywhere else.

Technical detail: authentication and the API permissions Oho needs

Hand this to whoever administers your Humanforce Talent API access. A non-technical admin can skip it.

  • Authentication. Oho uses the OAuth2 client_credentials grant against Humanforce Talent's token endpoint (https://sts.livehire.com/connect/token), as described in the Humanforce Talent authentication docs. Oho sends no scope parameter, so the scopes allocated to the client are the ones Oho gets.
  • Webhook subscriptions. GET and POST on /subscriptions, so Oho can register its webhook for the CheckRequested event.
  • Reading the request. GET on /checks, /candidates, /job-vacancies, and /job-applications. Oho uses the IDs on the webhook to read the check, the candidate, the job, and the application.
  • Returning the result. Every POST endpoint under /checks, so Oho can update the check and post the completion report.

If authentication fails, the token endpoint's error points to the cause:

  • invalid_client: the client ID or secret is wrong, or the client isn't active in that environment.
  • invalid_scope: the credentials are right, but no scopes are allocated to the client. Humanforce needs to add them.

The full API reference is at api.livehire.com/docs.

Expected outcome: Oho has a working client ID and secret for each environment, with the permissions above.

Step 3: Decide how each candidate's package is chosen​

This is the main design decision, and you make it with Oho's team. There are two options:

OptionHow it worksBest when
A list of packagesEach Oho package appears as its own option in the Checks & Assessments dropdown. The recruiter picks the right one per job, and its code tells Oho which package to send.You have a handful of packages, and recruiters know which one each role needs.
One Oho check, chosen by OhoThe dropdown holds a single Oho check. Oho picks the package from another detail on the job or candidate in Humanforce Talent (for example the job title or location), using rules agreed during setup.You have many roles, or you'd rather recruiters didn't choose the package themselves.

Either way, Oho's team records the mapping in the integration's configuration, and your Humanforce contact sets up the matching Checks & Assessments options on the Humanforce side.

Expected outcome: you've agreed which option you're using and how every role maps to a screening package.

Step 4: Oho connects and tests​

Oho's team configures the integration in Oho's integration platform, registers it with Humanforce Talent, and runs a test check end to end, in UAT first if you have it. You review the candidate email and the report that lands back in Humanforce Talent, then sign off before going live.

Expected outcome: a test check has run end to end, and the integration is live in production.

Changing your packages later​

There's no live sync of packages between Oho and Humanforce Talent. Creating or editing a package in Oho doesn't change what recruiters see in Humanforce Talent, and editing the Checks & Assessments list in Humanforce Talent doesn't tell Oho.

Package changes need both sides updated

If the codes in the Checks & Assessments list and the mapping in Oho stop matching, check requests can't be matched to a package and candidates won't get their email. Plan package changes with Oho's team instead of making them on one side.

To add, rename, or retire a package:

  1. Update the package in Oho, or ask Oho's team to.
  2. Email support@weareoho.com with what's changing. Oho's team updates the integration's mapping.
  3. Ask Humanforce to update your Checks & Assessments options. If you use the list option, each package's option and code is set up by a Humanforce employee, so raise it with your Humanforce contact. If you use the single-check option, this step usually isn't needed, unless the job or candidate detail Oho reads is changing.

Expected outcome: the dropdown in Humanforce Talent, the mapping in Oho, and your packages all match.

Common questions​

Do Humanforce Talent and LiveHire mean the same thing? Yes. Humanforce Talent is LiveHire's current name.

Can I set this up from the Integrations page? No. Humanforce Talent is separate from Oho's built-in connectors. Email support@weareoho.com to request it.

Recruiters can't see the Oho check in Checks & Assessments. The options haven't been set up on the Humanforce side yet, or Checks & Assessments isn't in your subscription. Raise it with your Humanforce contact.

A recruiter requested a check, but the candidate never got an email. Usually the option's code doesn't match a package in Oho's mapping, often after a package changed on one side only. Contact support@weareoho.com with the candidate's name and the job, and see Changing your packages later.

I created a new package in Oho. Why can't recruiters pick it? Packages don't sync to Humanforce Talent. Follow Changing your packages later.

Where does the result show up in Humanforce Talent? On the candidate's check, as a single report posted when they complete their package. Each credential in it links to that credential in Oho. Opening the links needs an Oho login.

Do I need an Oho login to request checks? No. Recruiters work entirely in Humanforce Talent. You only need Oho to open the credential links in the report or to manage applicants.