BambooHR API

Name: BambooHR API
Brand: BambooHR API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentHR recruitingEmployee Managementoauth2, basic164 EndpointsREST

For Agents

Query employee records, submit time-off requests, run custom reports, and manage benefits, payroll, and hiring pipelines across an entire BambooHR account.

Install Jentic One Beta

Connect the BambooHR API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the BambooHR API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with BambooHR API.

Pull employee directory listings and individual profile records with custom field support

Submit and approve time-off requests with policy-aware balance calculations

Generate custom reports with flexible field selection and filtering criteria

GET STARTED

Start building with BambooHR API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use BambooHR API for, with concrete tasks.

★ AI Agent HR Data Retrieval

AI agents use the BambooHR API through Jentic to fetch employee records, time-off balances, and organizational data without direct BambooHR credentials. An agent searches for 'get employee details', loads the schema for the employee endpoint, and retrieves structured profile data including custom fields. This enables HR chatbots, onboarding automations, and self-service portals to pull real-time workforce data.

Retrieve the full employee profile for employee ID 123 including custom fields and return their department, manager, and hire date

Time-Off Automation

Automate the full time-off lifecycle from request submission through approval and balance tracking. The API exposes endpoints to submit requests with specific date ranges and absence types, check remaining balances against policies, and update request statuses. Integrations typically connect with Slack bots or internal portals so employees request PTO without logging into BambooHR directly.

Submit a 2-day vacation request for employee ID 456 starting next Wednesday and verify the remaining balance afterwards

Custom Reporting and Analytics

Generate on-demand or scheduled custom reports pulling any combination of employee fields across the workforce. The custom reports endpoint accepts field lists and filter criteria, returning structured data suitable for dashboards, compliance audits, or headcount planning. Reports can include compensation, tenure, demographics, and custom field data.

Generate a custom report listing all employees hired in the last 90 days with their department, title, and manager name

Applicant Tracking Integration

Connect hiring workflows with external systems by accessing applicant data, tracking candidates through pipeline stages, and syncing hiring decisions. The applicant tracking endpoints expose job postings, applications, candidate profiles, and status transitions. Recruiting teams integrate this with scheduling tools, assessment platforms, and onboarding systems.

List all applicants in the 'Interview' stage for the Engineering department and return their names and application dates

Benefits Administration Sync

Synchronize benefits enrolment data between BambooHR and insurance carriers, payroll systems, or benefits administration platforms. Endpoints cover company benefit plans, employee enrolment records, deduction types, and coverage details. Automations ensure new hires are enrolled and life-event changes propagate to downstream systems without manual data entry.

Retrieve all active benefit enrolments for employee ID 789 including plan names, coverage levels, and monthly deduction amounts

Key Endpoints

164 endpoints — jentic publishes the only available openapi specification for bamboohr api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/{companyDomain}/v1/employees/directory

List the employee directory

GET

/{companyDomain}/v1/employees/{id}/tables/{table}

Get employee tabular data

POST

/{companyDomain}/v1/reports/custom

Generate a custom report

PUT

/{companyDomain}/v1/employees/{employeeId}/time_off/request

Submit a time-off request

GET

/{companyDomain}/v1/employees/{employeeId}/time_off/policies

Get time-off policies for an employee

GET

/{companyDomain}/v1/employees/changed

List recently changed employee records

GET

/{companyDomain}/v1/benefit/company_benefit

List company benefit plans

GET

/{companyDomain}/v1/employees/{employeeId}/time_off/calculator

Calculate time-off balance

GET

/{companyDomain}/v1/employees/directory

List the employee directory

GET

/{companyDomain}/v1/employees/{id}/tables/{table}

Get employee tabular data

POST

/{companyDomain}/v1/reports/custom

Generate a custom report

PUT

/{companyDomain}/v1/employees/{employeeId}/time_off/request

Submit a time-off request

GET

/{companyDomain}/v1/employees/{employeeId}/time_off/policies

Get time-off policies for an employee

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your BambooHR OAuth token or API key is stored once, encrypted, by your own Jentic One instance and injected at execution time, scoped to a specific company domain. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'get an employee profile' or 'check an employee's time-off balance', and Jentic returns the matching BambooHR operation with its input schema and required path parameters so the agent calls the right endpoint without parsing the documentation.

Time to first call

FAQs

Specific to using BambooHR API through Jentic.

Why is there no official OpenAPI spec for BambooHR API?

BambooHR does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call BambooHR API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the BambooHR API use?

The API supports two authentication methods: OAuth 2.0 authorization code flow (recommended for production integrations) and HTTP Basic auth using an API key as the username with an empty password. OAuth tokens are obtained from https://{companyDomain}.bamboohr.com/authorize.php. Through Jentic, credentials are stored in your Jentic One instance and agents receive scoped tokens without handling raw API keys.

Can I generate custom employee reports with the BambooHR API?

Yes. POST to /{companyDomain}/v1/reports/custom with a JSON body specifying the fields you want (e.g., firstName, lastName, department, hireDate) and optional filter criteria. The response returns structured tabular data. You can also retrieve pre-built reports via GET /{companyDomain}/v1/reports/{id} using the report ID from the BambooHR UI.

What are the rate limits for the BambooHR API?

BambooHR enforces a rate limit of 50 requests per 15-second window per API key. Exceeding this returns HTTP 429. The response includes a Retry-After header indicating when the next request can be made. For bulk operations, batch employee change detection via GET /{companyDomain}/v1/employees/changed to identify only modified records.

How do I submit a time-off request through Jentic?

Search Jentic for 'submit employee time off request', load the schema for PUT /{companyDomain}/v1/employees/{employeeId}/time_off/request, and execute with the employee ID, date range, and time-off type. Before submitting, call GET /{companyDomain}/v1/employees/{employeeId}/time_off/calculator to check the available balance. Install with pip install jentic.

Does the BambooHR API support webhooks for real-time updates?

Yes. The Webhooks resource allows you to register HTTP callback URLs that receive notifications when employee records change. Events include new hires, terminations, field updates, and time-off status changes. This eliminates the need for polling the employees/changed endpoint for near-real-time integrations.

Can I limit what my agent is allowed to do with the BambooHR API?

Yes. Because you run Jentic One yourself, your own rules decide which BambooHR operations and credentials the agent may use, and BambooHR puts the company domain and employee ID in the URL path, so a rule can pin the agent to a single company or employee. You can allow only read operations such as GET /{companyDomain}/v1/employees/directory or GET /{companyDomain}/v1/employees/{employeeId}/time_off/calculator, and the agent can do nothing else. Write operations like PUT /{companyDomain}/v1/employees/{employeeId}/time_off/request are excluded unless you explicitly add them. The stored OAuth token or API key is injected at execution time and scoped to the company domain you set, never entering the agent's prompt or logs.