BambooHR integration services

Payroll needs a subset of the BambooHR record: employee number, name, work email, hire date and employment status; job title, department, division and location from the jobInfo table; and rate, pay type, paid-per unit, pay schedule, overtime rate and FLSA exempt status from the compensation table. We read those through the REST API, catch changes with webhooks or the changed-employees endpoint, and map each value to the payroll provider’s fields, storing the BambooHR employee ID on the payroll side. After each run we compare headcount and pay totals in both systems and flag any employee whose rate, status or department differs.

BambooHR Payroll is an add-on that pays US-based employees, with federal, state and local tax filing, W-2 creation, direct deposit and multiple pay rates per employee. It reads the same employee record, PTO, time tracking and benefits data as the rest of BambooHR, so no HR-to-payroll sync is needed, and its journal entry builder feeds QuickBooks Online, Xero, NetSuite and Sage Intacct. Staff outside the US are paid through the Global Employment add-on (powered by Remote) or a third-party payroll connected through the marketplace or a custom integration.

Yes, in two ways. If you run BambooHR Payroll, its Custom Journal Entry Report Builder creates entries built around your chart of accounts, and BambooHR lists NetSuite as an accounting partner for them. If NetSuite is your ERP and payroll runs elsewhere, we sync BambooHR departments, divisions, locations and employees into NetSuite through its APIs, keyed on the BambooHR employee ID, so expense reports, project costing and payroll journals share one set of dimensions; that HR-record sync is a custom or iPaaS build rather than a BambooHR-supplied connector.

BambooHR exposes a REST API at https://{yourcompany}.bamboohr.com/api/v1/ covering employees and their tables, reports and datasets, time off, time tracking, benefits, files, hiring and webhooks. A single company uses an API key, created by a user with sufficient permissions from their name in the lower-left corner of BambooHR; the key sees exactly what that user can see. Integrations sold to many customers use OAuth 2.0 through an application in the Developer Portal, with 3,600-second access tokens and a refresh token only when the offline_access scope is requested. The only official SDK is PHP (bamboohr/api).

Yes. Datapay is Datacom’s payroll service for New Zealand and Australia, and Business Toolbox in Auckland implements a two-way BambooHR–Datapay integration powered by Datacom that syncs employee records, leave requests and balances daily, with a manual push for urgent changes and optional payslips back into BambooHR. For payrolls with no listed connector we build the same pattern on the BambooHR API: employee and compensation changes go out by webhook or on a schedule, and leave balances come back through the time off endpoints when payroll owns leave.

Three ways, in order of speed. Webhooks post JSON when a monitored field changes; permissioned webhooks can watch any field the API user may read, custom fields included, at the frequency you set (the documentation’s example is every 30 minutes). The changed-employees endpoint returns every employee whose record, employment status, job info or compensation table changed since a timestamp, which suits a poll every few minutes, and datasets cover full reconciliation loads. We combine webhooks for speed with a scheduled changed-since sweep that catches anything missed.

BambooHR signs each webhook with SHA-256 HMAC (X-BambooHR-Signature and X-BambooHR-Timestamp headers), requires HTTPS, and retries a failed delivery up to five times: immediately, then after 5, 10, 20 and 40 minutes. It publishes no request quota; calls it considers too frequent are throttled with a Retry-After header. From September 16, 2026 throttled requests return HTTP 429 instead of 503, so integrations that treated 503 as “try later” need updating, and 503 now means the API is actually unavailable.

BambooHR itself lists Core at $10, Pro at $17 and Elite at $25 per employee per month, or a flat rate from $250 per month for companies of 25 or fewer, with volume discounts by headcount (vendor list prices, Sep 2026); Payroll, Benefits Administration, Time & Attendance and Global Employment are priced separately. A marketplace connector such as Flexspring is bought from the partner, who configures it. A custom sync for one payroll or accounting system usually takes a few weeks including testing on a BambooHR test account; identity provisioning, several countries or a signed-off reconciliation report typically take two to three months.

An API key inherits its user’s access level, so we create a dedicated integration user with a custom access level that sees only the fields and employees the sync needs, and request scopes such as employee:compensation only where pay data is required. Fields the key cannot read are silently omitted from single-employee reads and returned as null on list calls, so tests confirm the key sees everything the mapping expects. Social Security numbers, national IDs and bank details stay out of the integration unless the payroll requires them, and then travel encrypted and are never logged.

Core, Pro and Elite differ in performance, engagement, analytics and compliance features; the pricing page does not list the API or webhooks as plan features, so confirm with BambooHR that your account has API keys and Account Settings > Webhooks before scoping. Time & Attendance, Benefits Administration and Payroll are add-ons, and their endpoints carry nothing useful without them. Datasets require elevated permissions on the API user and return 403 without them.

Yes. BambooHR runs a hosted MCP server at https://{yourcompany}.bamboohr.com/api/mcp, in beta, with OAuth sign-in and pre-built connectors for Claude and ChatGPT. It covers 11 areas, including employees, fields, datasets, reports, time off, goals, hiring, global employment and files, and every call runs with the signed-in user’s BambooHR permissions. It has no payroll tools, and results narrowed by permissions come back without a marker, so AIONDATA configures the official connector first and builds a custom MCP server when an assistant must also reach payroll or reconciliation data, run under a service account, or write only after a person approves.

No. AIONDATA is an independent integration consultancy and is not a BambooHR partner or marketplace developer. We are led from San Ramon, California, with engineering in Noida, India, and our delivery processes are ISO 9001:2015 and CMMI Level 3 certified. We can configure a marketplace partner’s connector, build alongside your BambooHR admin, or own the integration end to end, and we document every mapping so your team can maintain it.