Skip to main content

Connect BambooHR

Import your workers and their current job from BambooHR, the HR platform. You connect Oho to BambooHR once, and Oho creates your workers and keeps them in step with BambooHR on the schedule you choose — so people don't have to be added in two places.

BambooHR is in Beta

This connector is still being rolled out. It imports workers and their current job, along with worker status where your account allows it — but not full job history yet. If you hit something unexpected, contact support@weareoho.com.

What you'll end up with

Your BambooHR employees in Oho as workers — each ready for credentials to be added and checked — kept in step with BambooHR, without maintaining two lists.

Before you start​

You'll need:

  • Your people already recorded in BambooHR, with the details you want in Oho — their names, contact details, and current job.
  • A BambooHR admin account, or someone who has one, to generate an API key in Step 1.
  • Your BambooHR company domain — the subdomain in your web address, for example mycompany in https://mycompany.bamboohr.com.

Step 1: Get your auth details​

What you'll need for this step

An admin login to BambooHR. The API key is generated inside BambooHR, not in Oho.

BambooHR uses the API key pattern — you generate a key in BambooHR and paste it into Oho.

  1. Sign in to BambooHR as an administrator.
  2. Click your profile icon (top right) and choose API Keys.
  3. Click Add New Key, name it Oho integration, and generate it.
  4. Copy the key straight away — BambooHR shows it only once.
Technical detail: API key, permissions & format
  • Oho authenticates with HTTP Basic auth, sending the API key as the username on every request.
  • A key inherits the permissions of the account that created it. Generate it from an account whose access is limited to the people and fields you want in Oho.
  • There's no IP allow-list to configure. See the shared Get your auth details → API key or token.
Treat the key like a password

The API key grants ongoing access to worker PII for as long as it's valid. Never post it in email, chat, or a ticket, and generate a new key (revoking the old one) if the connection is removed or someone with access to it leaves.

Expected outcome: you have your BambooHR API key and company domain copied, ready to paste into Oho.

Step 2: Connect it in Oho​

In the left menu under Admin, click Integrations, then start a new integration.

The Integrations page in Oho

Pick BambooHR from the list of sources.

Choosing BambooHR as the source

Paste your API key and enter your company domain, then click Next.

Entering the BambooHR connection details in Oho

Expected outcome: Oho confirms it can reach BambooHR and moves you on to field mapping.

Step 3: Map your fields​

Oho creates one worker per BambooHR employee. It recognises a returning worker by their BambooHR employee ID, carried on source.externalId — so a re-sync updates the existing worker in place rather than creating a duplicate.

BambooHR has its own names for things such as status, department, and location; the setup screen asks you to line each one up with its Oho value before your first sync. For what each field expects, which are required, and how re-syncs avoid duplicates, see the shared Map your fields reference, and the BambooHR integration reference for what this connector imports at a glance.

Map every value, or those records won't land where you expect

A BambooHR value you leave unmapped still imports, but Oho can't place it correctly until it's mapped. If a new value appears in BambooHR later, Oho flags it so you can map it.

Expected outcome: every BambooHR value the setup screen lists maps to its Oho equivalent, and each worker carries their BambooHR employee ID as the match key.

Step 4: Set the schedule​

Choose how often the sync runs, then name it and save.

  • Once — a one-off load to get started. You can revoke the API key in BambooHR afterwards if you don't intend to sync again.
  • Recurring — Oho re-reads BambooHR on a schedule, so new starters, role changes, and terminations flow through automatically. The API key must stay valid for future runs.

Setting the sync schedule

Expected outcome: the connection is saved and scheduled, and appears in your Integrations list.

Step 5: Run & verify your first sync​

Run it now with Save & Run, or wait for the first scheduled run. Once it's run, confirm your people are in: they appear under All Workers, and each credential you later add is checked against its official source (see One-off verification).

The new BambooHR connection in your Integrations list, run history green

If the run didn't bring everyone in, check the run history and the Common questions below.

Expected outcome: your people are in Oho under All Workers, ready for credentials to be added and checked.

What happens next​

  • Your people appear under All Workers, ready for checks.
  • To keep those checks current, add a verification source for the credential types you hold — synced credentials then verify at the register automatically.
  • If recurring, you don't re-import by hand — change it in BambooHR and Oho picks it up on the next run.

Common questions​

The sync found nothing. The API key may have been revoked or created under an account that can't see your employees. Generate a fresh key from an admin account and check the company domain is correct.

Some workers didn't import. Check the match key and required fields from Step 3 — a worker missing a required value won't import until it's populated in BambooHR.

I don't see Integrations. This is an admin area — if it's not in your menu, ask an admin in your organisation, or contact support@weareoho.com.