← All integrations
Live integration

BambooHR

HR · API key / service-account token · Daily

API key auth. Pulls active employee count, recent terminations (30d), and onboarding-task completion rate for personnel-control evidence.

Authentication
API key / service-account token
Sync cadence
Daily
Stale threshold
Every 2 days
Category
HR

Evidence this connector produces

Every sync writes typed evidence rows linked to the controls below. Evidence is immutable once attached to an approved assessment, fingerprinted for de-dup, and surfaced in the control coverage calculation on your dashboard.

SOC 2 CC1.4CC6.3

How to connect

Generate an API key in your BambooHR account. Paste the key + your company subdomain.

  1. 1
    Generate the API key

    BambooHR → click your name (top-right) → API Keys → Add a new key. Note: API keys inherit the permissions of the user who creates them — use a service-account-style user with read-only access.

  2. 2
    Note your subdomain

    Your BambooHR URL is acme.bamboohr.com — paste 'acme' as the subdomain.

Security model

Every connector ships behind the same auditor-grade primitives — not just RBAC config, but architectural enforcement.

Credentials KMS-encrypted at rest

Tokens, client secrets, and service-account keys are encrypted under a per-tenant AWS KMS data key. The plaintext is never persisted, never logged, and never leaves the FastAPI process boundary.

Tenant-isolated by architecture

Every Connection, ConnectorRun, and emitted Evidence row carries an organization ObjectId. The scheduler never iterates without an org-scoped filter; cross-tenant evidence bleed is impossible at the data layer.

Audit log on every action

Connect, sync, sync-failure, re-auth, and revoke each write a row to the immutable AuditLog. The full lifecycle is reconstructable for any examiner.

Soft-delete on revoke

Revoking a connection sets deletedAt and clears the encrypted credential blob, but the historical evidence + sync log stays queryable for the retention window. Auditors can still trace what was attested when.

Stale-evidence degradation

If this connector hasn't synced in Every 2 days, control coverage degrades automatically and an alert fires. Auditors don't trust stale evidence — neither do we.

Least-privilege scopes only

We request the minimum read-only scopes needed for the listed evidence. No write scopes, no admin scopes, no scopes outside the documented set.

Ready to connect BambooHR?

Connect from Settings → Integrations — typically under 5 minutes. Or talk to us first.