How to connect BambooHR to Continu via API for direct user provisioning — generate the API key in BambooHR, configure the integration in Continu.
BambooHR has a dedicated API-based integration with Continu. Instead of file-based SFTP ingestion, Continu pulls user data directly from BambooHR via API key. The trade-off: less file management on your end; requires BambooHR-side admin to generate the API key.
For other HRIS systems, use the SFTP integration. For the strategic context on user provisioning, see Provisioning and Sync: How User Data Flows Into Continu.
Note: To set up the integration correctly, a user with admin-level privileges in BambooHR must establish the connection.
Enable BambooHR
1. In BambooHR, click the avatar icon.
2. Select API Keys.
3. Click Add New Key.
4. Name the API Key.
5. Click Generate Key.
6. Click Copy Key and save the API information securely. You'll need it in step 13.
7. Click Done to finish API Key setup in BambooHR.
8. In Continu, click Admin.
9. Select Settings.
10. Select Integrations.
11. Click the BambooHR button (under the HRIS area).
12. Add your BambooHR subdomain (the first part of the URL — e.g., company from company.bamboohr.com).
13. Paste the API Key (from step 6) into the BambooHR API-Key area.
14. Enable the correct Sign-In method for your organization. Check with IT if unsure.
15. Decide whether new users should receive invite emails when added through BambooHR. This applies whether or not you're using SSO.
16. Add users who should be Admins or Creators when they first sync from BambooHR. Anyone not listed defaults to the User role.
17. Save the integration. BambooHR users now sync into Continu on Continu's schedule.
Configuration Pitfalls
API Key Without Admin Privileges. If the user generating the API key doesn't have full BambooHR admin access, the API key has limited scope. Some user data won't sync. Verify the key generator has full admin before relying on the integration.
Subdomain Format Errors. The BambooHR subdomain field expects just the subdomain (company), not the full URL (company.bamboohr.com). Wrong format fails the connection.
Forgetting to Specify Admins/Creators. Without specifying, every BambooHR user syncs as User role. Adding the relevant admins/creators in step 16 saves the manual role-update work later.
Sign-In Method Mismatch. If the integration is set to send invite emails but the organization actually uses SSO, learners get duplicate or unnecessary email invitations. Verify the Sign-In configuration matches what the org actually uses.
API Key Rotation Without Updating Continu. If you rotate the BambooHR API key (security best practice), the integration breaks until the new key is updated in Continu. Coordinate API key rotations with Continu integration updates.
Where This Fits
You're here because you're configuring the BambooHR integration. For other HRIS paths, see How Continu Integrates with your HRIS. For the broader context, see Provisioning and Sync: How User Data Flows Into Continu.
See Also
- Provisioning and Sync: How User Data Flows Into Continu — the strategic anchor.
- How Continu Integrates with your HRIS — HRIS integration overview.
- Integrating Your HRIS via SFTP — SFTP path for non-BambooHR HRIS systems.
- HRIS Integration (via SFTP) - Field Guide — field reference.