Skip to main content

Connect SmartRecruiters

Screen your candidates from inside SmartRecruiters. Once connected, a recruiter picks an Oho screening when they're working a candidate in SmartRecruiters, and Oho collects that candidate's credentials, runs the checks, and reports the result straight back into SmartRecruiters — no one has to leave the ATS or re-enter anyone.

Unlike your HRIS or file connectors, SmartRecruiters doesn't import a list of people on a schedule. It works the other way around: each screening a recruiter orders flows into Oho one candidate at a time as a Recruitment Check. You enable Oho once from inside SmartRecruiters, and from then on orders push through as they happen.

What you'll end up with

Recruiters ordering Oho screenings without leaving SmartRecruiters — each candidate arriving in Oho as a Recruitment Check, and the result landing back in SmartRecruiters automatically once the checks are done.

Before you start​

You'll need:

  • Your screenings set up in Oho. The screenings recruiters can order come from your screening packages. If you've configured a package catalogue for SmartRecruiters, recruiters see that; otherwise Oho offers your active screening packages. If you have neither, recruiters will have nothing to order.
  • Your SmartRecruiters company recorded in Oho. Your SmartRecruiters company ID must be set on your Oho tenant settings. Oho checks it during connection and turns away a request from any other company, so this has to match before you enable the integration.
  • A SmartRecruiters admin who can enable a marketplace integration in your SmartRecruiters account.
  • An Oho admin account, to set the connection up and manage orders afterwards. Both live under Admin → Data Sources.

Step 1: Enable Oho in SmartRecruiters​

You start the connection from Oho, then finish it inside SmartRecruiters.

In Oho, go to Admin → Data Sources → Connect Integration → Smart Recruiters and follow the prompt through to SmartRecruiters. In SmartRecruiters, enable Oho from the marketplace. SmartRecruiters then sends your browser back to Oho to grant consent, Oho sets the connection up, and returns you to SmartRecruiters.

Because you enable Oho from inside your own SmartRecruiters account, there's nothing to copy or paste and no key to store — Oho and SmartRecruiters exchange the credentials they need between themselves, and keep them encrypted.

What "granting consent" does

When you enable Oho, your browser is briefly handed to Oho and back. In that moment Oho checks your SmartRecruiters company ID against your tenant settings, sets up the connection, and stores the credentials both sides will use — all encrypted. If the company ID doesn't match, or the return link isn't one Oho recognises, Oho shows a "couldn't connect" page and the integration stays off.

Technical detail: the credential exchange and where secrets live

Hand these points to whoever administers SmartRecruiters or handles Oho's setup — a non-technical admin can skip them.

  • Consent (front-channel). Enabling Oho redirects the recruiter's browser to Oho's consent endpoint. There's no API token on this step; Oho gates it on two checks — the presented company ID must equal the one on your tenant settings, and any return URL SmartRecruiters supplies must match an allow-listed domain (HTTPS). Both success and failure render a styled landing page; there's no error page in the usual sense.
  • What Oho stores. On success Oho obtains a SmartRecruiters partner token, generates a fresh Oho-issued client credential pair, and stores both pairs as encrypted secrets — four secrets in total — then flips the connection to enabled.
  • How SmartRecruiters authenticates afterwards. SmartRecruiters presents the Oho-issued credentials to Oho's OAuth2 token endpoint (client_credentials grant) and gets a short-lived bearer token for its calls. No one manages this by hand.
  • Rotating credentials. Re-enabling Oho from SmartRecruiters (re-consenting) regenerates all four secrets. That's the supported way to rotate them.

Expected outcome: the SmartRecruiters connection shows as enabled in Oho, and you didn't have to handle a credential yourself.

Step 2: Recruiters order screenings​

Once the connection is enabled, your screenings appear to recruiters inside SmartRecruiters. A recruiter working a candidate picks the Oho screening they want and orders it — that's the whole interaction on their side. There's nothing for them to set up in Oho, and they don't need an Oho login.

When an order is placed, SmartRecruiters sends Oho the candidate and the screening chosen, and Oho turns that into a Recruitment Check:

  • The candidate (their email and name) becomes the applicant to be screened — their email identifies them.
  • The screening package chosen sets which credential checks the candidate has to complete.
  • Any position information carried on the order is used to work out position-based requirements, where your screenings use them.

The candidate gets a secure link to provide what's needed, the checks run, and Oho sends the result back to SmartRecruiters.

Expected outcome: recruiters can see and order your screenings from within SmartRecruiters, and each order arrives in Oho as a Recruitment Check.

Step 3: Track results in Oho​

There are two places to keep an eye on work coming from SmartRecruiters.

Recruitment Check Requests. Each order becomes a Recruitment Check — the candidate's request and its results sit alongside your other recruitment checks, so screening a SmartRecruiters candidate looks the same as screening anyone else.

The request log. Every order SmartRecruiters places is also recorded against the connector. Go to Admin → Data Sources, open your Smart Recruiters source, and choose the Request Log step. Each request is listed with when it arrived, the candidate, the screening package, a status, and — where there is one — the issue that stopped it:

StatusWhat it meansWhat you can do
ReceivedSmartRecruiters' order has arrived and is queued.Wait.
ProcessingOho is working out the position and package.Wait.
AcceptedThe order became a Recruitment Check; the candidate has been asked.Wait.
Needs attentionOho couldn't match the order — the Issue column says why.Fix the configuration, then Retry.
Delivering resultThe checks are done and the result is on its way back.Resend result, if it doesn't land.
CompletedSmartRecruiters has the result.Resend result, if they lost it.
FailedProcessing errored.Fix the configuration, then Retry.

The log gives you two things to work with:

  • Status — filter the list down to one status, so you can pull up everything that's Needs attention without reading past the requests that are fine.
  • Retry and Resend result — in the Actions column, on the rows that can use them. Retry runs the whole screening again, so reach for it when the screening never happened. Resend result hands SmartRecruiters the result Oho already has without re-running any checks, so reach for it when the screening is done but the result didn't arrive.

Fix the configuration before you retry. Most Needs attention requests are a Position Source mapping that doesn't resolve the position the order names, and a retry against the same configuration just parks the request again — Oho will tell you so, and the Issue column will show the reason it gave the second time.

Who can manage orders

Seeing the request log needs read access, and Retry and Resend result need update access, on screening orders. Without update access Oho turns the first click down and says so, then greys both buttons out with the reason on hover — ask an admin in your organisation.

Expected outcome: you can see SmartRecruiters candidates as Recruitment Checks, and you have one place to find a stuck order and retry or re-send it.

Turning the connection off​

Disabling the integration deactivates the connection: Oho removes the stored credentials and sets the connection to disabled. This can happen from your side, or when a recruiter removes Oho from the SmartRecruiters marketplace. To turn it back on, enable Oho again from SmartRecruiters — that issues fresh credentials, exactly like the first time.

What happens next​

  • Candidates recruiters screen in SmartRecruiters arrive as Recruitment Checks, ready to work like any other — see Send a Recruitment Check.
  • When you take a candidate on, promote them to a worker and the credentials they submitted carry across, so nothing is re-collected (see Applicants).
  • Orders keep flowing as recruiters place them — there's no sync to schedule or re-run.

Common questions​

Recruiters can't see any screenings to order. Check you have screenings set up — either a SmartRecruiters package catalogue or active screening packages. With neither, there's nothing for recruiters to order.

An order isn't turning into a check, or it's flagged as needing attention. The order couldn't be matched — most often a position or configuration detail is missing. The Issue column in the request log says which. Fix the configuration, then Retry the request from Admin → Data Sources → Smart Recruiters → Request Log.

The screening finished but SmartRecruiters didn't get the result. The result can fail to hand back even when the screening itself is fine. Use Resend result on that request in the request log — it re-sends what Oho already has, without re-running the checks or asking the candidate for anything again.

Connecting failed with a "couldn't connect" page. The two usual causes are a company ID that doesn't match your Oho tenant settings, and a return link Oho doesn't recognise. Correct the company ID on your settings (or have the return domain allow-listed) and enable Oho again.

SmartRecruiters' orders are being rejected, or Oho says the integration isn't enabled. The connection may have been turned off, or its credentials may be stale. Enable Oho again from SmartRecruiters to switch it back on and refresh the credentials.

I don't see Data Sources. It's an admin area — if it isn't in your menu, ask an admin in your organisation, or contact support@weareoho.com. There is no separate "Screening Orders" menu item; the request log lives inside the Smart Recruiters source itself.