OVERALL CONTROL / 0.6-customer-control
Grades and scoring
Data access
25% of the overall score before applicability adjustment.
Scored answers and evidence
Read interface 7.5/10
Structured API for the declared product scope
BambooHR employee records / customer API key plus new-integration OAuth guidance; employee change IDs and permission-scoped updates.
Structured read interface for the declared product and resources
Get Changed Employee IDs ↗
Structured read interface for the declared product and resources · Checked 2026-10-16
Bulk delivery 8.8/10
Batched or iterable API requests
BambooHR employee records / customer API key plus new-integration OAuth guidance; employee change IDs and permission-scoped updates.
Repeatable current-state collection retrieval within the declared employee/customer and permission scope; whole-product recovery remains unverified.
List Employees ↗
GET /api/v1/employees; data, meta.page and _links.next; default250/max2500; current field permissions · Checked 2026-10-16
Query expressiveness 8.8/10
Documented structured API filters
BambooHR employee records / customer API key plus new-integration OAuth guidance; employee change IDs and permission-scoped updates.
since and change-type filters
Get Changed Employee IDs ↗
since and change-type filters · Checked 2026-10-16
Access cost barrier -
-
BambooHR employee records / customer API key plus new-integration OAuth guidance; employee change IDs and permission-scoped updates.
Reviewed entitlement documentation; minimum eligible plan and fixed route-specific access charges remain unresolved
Getting Started With The API ↗
Reviewed entitlement documentation; minimum eligible plan and fixed route-specific access charges remain unresolved · Checked 2026-10-16
Third-party accessibility
20% of the overall score before applicability adjustment.
Scored answers and evidence
Third-party eligibility -
-
BambooHR employee records / customer API key plus new-integration OAuth guidance; employee change IDs and permission-scoped updates.
New OAuth guidance; current third-party enrollment contract unverified
Authentication migration guidance ↗
New OAuth guidance; current third-party enrollment contract unverified · Checked 2026-10-16
Downstream permission -
-
BambooHR employee records / customer API key plus new-integration OAuth guidance; employee change IDs and permission-scoped updates.
Reviewed access documentation; applicable downstream processing, AI and redistribution terms not established
Getting Started With The API ↗
Reviewed access documentation; applicable downstream processing, AI and redistribution terms not established · Checked 2026-10-16
External action
15% of the overall score before applicability adjustment.
Scored answers and evidence
Write interface 7.5/10
Create and update in one business domain
BambooHR employee records / customer API key plus new-integration OAuth guidance; employee change IDs and permission-scoped updates.
Employee create and update through separately documented operations; field and payroll-sensitive constraints remain applicable.
Update Employee ↗
Update Employee; employee and field permissions; status-field exclusions · Checked 2026-10-16
Create employee ↗
Create employee; POST employee collection with company-specific validation and field permissions · Checked 2026-10-16
Custom application path -
-
BambooHR employee records / customer API key plus new-integration OAuth guidance; employee change IDs and permission-scoped updates.
Current chosen-application distribution and approval conditions remain unresolved
Getting Started With The API ↗
Current chosen-application distribution and approval conditions remain unresolved · Checked 2026-10-16
Continuity
15% of the overall score before applicability adjustment.
Scored answers and evidence
Refresh mechanism 7.5/10
Documented updated-since filters or webhooks
BambooHR employee records / customer API key plus new-integration OAuth guidance; employee change IDs and permission-scoped updates.
GET /employees/changed?since=...
Get Changed Employee IDs ↗
GET /employees/changed?since=... · Checked 2026-10-16
Limit visibility -
-
BambooHR employee records / customer API key plus new-integration OAuth guidance; employee change IDs and permission-scoped updates.
Technical onboarding reviewed; numeric account throughput unresolved
Getting Started With The API ↗
Technical onboarding reviewed; numeric account throughput unresolved · Checked 2026-10-16
CDC and deletion capture 7.5/10
Updates and deletion identities documented for the stated resources
BambooHR employee records / customer API key plus new-integration OAuth guidance; employee change IDs and permission-scoped updates.
Employee ID, Inserted/Updated/Deleted type and last-changed timestamp
Get Changed Employee IDs ↗
Employee ID, Inserted/Updated/Deleted type and last-changed timestamp · Checked 2026-10-16
Replay and gap recovery 2.5/10
Rebuild from a fresh snapshot; no historical replay established
BambooHR employee records / customer API key plus new-integration OAuth guidance; employee change IDs and permission-scoped updates.
Repeat List Employees and follow the returned cursor links to rebuild permitted current employee records and selected fields. This is a roster resnapshot, not the published directory, and does not recover deleted employee payloads, prior field versions, documents or retained change history.
List Employees ↗
GET /api/v1/employees; data, meta.page and _links.next; default250/max2500; current field permissions · Checked 2026-10-16
Data exit
20% of the overall score before applicability adjustment.
Scored answers and evidence
Export custody 7.5/10
Customer-held structured files or API records
BambooHR employee records / customer API key plus new-integration OAuth guidance; employee change IDs and permission-scoped updates.
Customer-held structured API records within the declared resource scope
Get Changed Employee IDs ↗
Customer-held structured API records within the declared resource scope · Checked 2026-10-16
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
BambooHR employee records / customer API key plus new-integration OAuth guidance; employee change IDs and permission-scoped updates.
Applicable post-cancellation retrieval clause not established by reviewed technical documentation
Getting Started With The API ↗
Applicable post-cancellation retrieval clause not established by reviewed technical documentation · Checked 2026-10-16
Planned migration fidelity 7.5/10
Portable structured records on documented routes; whole-product completeness unverified
BambooHR employee records / customer API key plus new-integration OAuth guidance; employee change IDs and permission-scoped updates.
Structured resource records can be retrieved; complete attachments, versions, relationships and native configuration remain unverified
Get Changed Employee IDs ↗
Structured resource records can be retrieved; complete attachments, versions, relationships and native configuration remain unverified · Checked 2026-10-16
Business logic and customization
5% of the overall score before applicability adjustment.
Scored answers and evidence
Logic authoring 2.5/10
External integration code; native business logic portability not established
BambooHR employee records / customer API key plus new-integration OAuth guidance; employee change IDs and permission-scoped updates.
Customer integration code can run outside the provider; native workflow authoring not established
Getting Started With The API ↗
Customer integration code can run outside the provider; native workflow authoring not established · Checked 2026-10-16
Rights to custom logic -
-
BambooHR employee records / customer API key plus new-integration OAuth guidance; employee change IDs and permission-scoped updates.
Ownership and reusable export or independent execution of native workflow artifacts remain unresolved
Getting Started With The API ↗
Ownership and reusable export or independent execution of native workflow artifacts remain unresolved · Checked 2026-10-16
Scores are out of 10. * Incomplete evidence discounts verified capabilities (unknown answers stay unknown). Planned migration drives data exit. Scoring method ↗
CUSTOMER CHOICE
Third-party accessibility
API-key requests use HTTP Basic and inherit user permissions. Current guidance directs new integrations to OAuth; the former approved-partner OpenID Connect route is no longer available for new integrations. Chosen-third-party enrollment conditions remain unresolved.
Confirm who can connect, who owns the credentials and which uses are permitted. Customer consent and provider approval can be separate requirements; the selected plan and contract still matter.
READ / INTEGRATE
API and export routes
Changed employee IDs include change type and timestamp, and employee APIs return fields allowed to the API user. Custom report extraction and employee table history are separate selections rather than evidence that every HR record was recovered.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| BambooHR scoped API access | HTTP Basic | Customer | Not confirmed | Not confirmed | 2026-10-16 |
Availability depends on your product, plan and agreement. See the documentation below for the requirements of each route.
ECONOMIC ACCESS
Cost, authentication and limits
Current minimum-plan eligibility and access-specific fees were not established. Authentication documentation does not prove a free integration entitlement.
Check API entitlement, credential ownership and rate limits for the route you intend to use. Include review fees, customer-plan upgrades and ongoing access charges in the total.
ACT FROM OUTSIDE
External action
Employee creation and updates are documented through distinct POST and update endpoints. Current field permissions and validation still apply; payroll execution and employment termination require separate operation-specific authority.
Validate the supported operation, acting identity and permission scope (read access does not imply write permission). Ambiguous retries and revoked credentials also affect whether an external workflow can run safely.
KEEP ACCESS USEFUL
Continuity
The changed-ID endpoint accepts since and distinguishes inserted, updated and deleted employees. Table changes can also make employees appear; replay retention and a checkpoint recovery procedure remain unresolved. Repeat List Employees and follow the returned cursor links to rebuild permitted current employee records and selected fields. This is a roster resnapshot, not the published directory, and does not recover deleted employee payloads, prior field versions, documents or retained change history.
CDC, deletions and recovery
| Question | Answer / applicable route | Evidence |
|---|---|---|
| Can ongoing extraction identify updates and deleted records on the declared route? | Updates and deletion identities documented for the stated resourcesBambooHR employee records / customer API key plus new-integration OAuth guidance; employee change IDs and permission-scoped updates. Employee ID, Inserted/Updated/Deleted type and last-changed timestamp | Get Changed Employee IDs ↗Employee ID, Inserted/Updated/Deleted type and last-changed timestampChecked 2026-10-16 |
| How can extraction recover after missed events or an interrupted consumer? | Rebuild from a fresh snapshot; no historical replay establishedBambooHR employee records / customer API key plus new-integration OAuth guidance; employee change IDs and permission-scoped updates. Repeat List Employees and follow the returned cursor links to rebuild permitted current employee records and selected fields. This is a roster resnapshot, not the published directory, and does not recover deleted employee payloads, prior field versions, documents or retained change history. | List Employees ↗GET /api/v1/employees; data, meta.page and _links.next; default250/max2500; current field permissionsChecked 2026-10-16 |
Useful ongoing access includes corrections and deletions, not only the first export. A failed request, changed filter or lost resource permission should not be interpreted as a deleted record.
LEAVE WITH YOUR DATA
Data exit and portability
Employee records can be copied before cancellation within the user’s field permissions. Full table history, documents and native approval settings require separate retrieval; post-cancellation access was not established.
Test the output against the destination’s required fields and history. Check stable identifiers, relationships, attachments and extraction time; a sample file proves only the coverage of that sample.
BUILD / INSPECT / REUSE
Business logic and customization
External integrations can apply customer rules to permitted HR data. Native workflow ownership and portable execution remain unresolved (employee field access does not establish workflow export).
Custom API access, ownership of workflows and the right to export their definitions are separate questions. A custom-app capability alone does not establish that business rules can move to another system.
AGREEMENTS / API DOCS / PROGRAM REQUIREMENTS
Documented conditions
Answers below come from public provider materials. Every answer retains its source check date, scope (a partner agreement does not describe every customer route). Customer contracts and live behavior still need verification.
| Question | Answer / applicable route | Evidence |
|---|---|---|
| What structured read interface is documented? | Structured API for the declared product scopeBambooHR employee records / customer API key plus new-integration OAuth guidance; employee change IDs and permission-scoped updates. Structured read interface for the declared product and resources | Get Changed Employee IDs ↗Structured read interface for the declared product and resourcesChecked 2026-10-16 |
| How can customers retrieve data in bulk? | Batched or iterable API requestsBambooHR employee records / customer API key plus new-integration OAuth guidance; employee change IDs and permission-scoped updates. Repeatable current-state collection retrieval within the declared employee/customer and permission scope; whole-product recovery remains unverified. | List Employees ↗GET /api/v1/employees; data, meta.page and _links.next; default250/max2500; current field permissionsChecked 2026-10-16 |
| What queries can a customer issue outside the provider UI? | Documented structured API filtersBambooHR employee records / customer API key plus new-integration OAuth guidance; employee change IDs and permission-scoped updates. since and change-type filters | Get Changed Employee IDs ↗since and change-type filtersChecked 2026-10-16 |
| Who decides whether a chosen third party may connect? | -BambooHR employee records / customer API key plus new-integration OAuth guidance; employee change IDs and permission-scoped updates. New OAuth guidance; current third-party enrollment contract unverified | Authentication migration guidance ↗New OAuth guidance; current third-party enrollment contract unverifiedChecked 2026-10-16 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | -BambooHR employee records / customer API key plus new-integration OAuth guidance; employee change IDs and permission-scoped updates. Reviewed entitlement documentation; minimum eligible plan and fixed route-specific access charges remain unresolved | Getting Started With The API ↗Reviewed entitlement documentation; minimum eligible plan and fixed route-specific access charges remain unresolvedChecked 2026-10-16 |
| What permission is needed for the documented downstream use? | -BambooHR employee records / customer API key plus new-integration OAuth guidance; employee change IDs and permission-scoped updates. Reviewed access documentation; applicable downstream processing, AI and redistribution terms not established | Getting Started With The API ↗Reviewed access documentation; applicable downstream processing, AI and redistribution terms not establishedChecked 2026-10-16 |
| Which external write operations are documented? | Create and update in one business domainBambooHR employee records / customer API key plus new-integration OAuth guidance; employee change IDs and permission-scoped updates. Employee create and update through separately documented operations; field and payroll-sensitive constraints remain applicable. | Update Employee ↗Update Employee; employee and field permissions; status-field exclusionsChecked 2026-10-16 Create employee ↗Create employee; POST employee collection with company-specific validation and field permissionsChecked 2026-10-16 |
| How can customers connect an application they build or choose? | -BambooHR employee records / customer API key plus new-integration OAuth guidance; employee change IDs and permission-scoped updates. Current chosen-application distribution and approval conditions remain unresolved | Getting Started With The API ↗Current chosen-application distribution and approval conditions remain unresolvedChecked 2026-10-16 |
| What mechanism supports repeatable extraction of changes? | Documented updated-since filters or webhooksBambooHR employee records / customer API key plus new-integration OAuth guidance; employee change IDs and permission-scoped updates. GET /employees/changed?since=... | Get Changed Employee IDs ↗GET /employees/changed?since=...Checked 2026-10-16 |
| How are integration limits disclosed? | -BambooHR employee records / customer API key plus new-integration OAuth guidance; employee change IDs and permission-scoped updates. Technical onboarding reviewed; numeric account throughput unresolved | Getting Started With The API ↗Technical onboarding reviewed; numeric account throughput unresolvedChecked 2026-10-16 |
| Where can a usable data copy be delivered? | Customer-held structured files or API recordsBambooHR employee records / customer API key plus new-integration OAuth guidance; employee change IDs and permission-scoped updates. Customer-held structured API records within the declared resource scope | Get Changed Employee IDs ↗Customer-held structured API records within the declared resource scopeChecked 2026-10-16 |
| What retrieval rights are documented at cancellation? | -BambooHR employee records / customer API key plus new-integration OAuth guidance; employee change IDs and permission-scoped updates. Applicable post-cancellation retrieval clause not established by reviewed technical documentation | Getting Started With The API ↗Applicable post-cancellation retrieval clause not established by reviewed technical documentationChecked 2026-10-16 |
| How can customers define their own business logic? | External integration code; native business logic portability not establishedBambooHR employee records / customer API key plus new-integration OAuth guidance; employee change IDs and permission-scoped updates. Customer integration code can run outside the provider; native workflow authoring not established | Getting Started With The API ↗Customer integration code can run outside the provider; native workflow authoring not establishedChecked 2026-10-16 |
| What rights or portability are documented for custom workflow artifacts? | -BambooHR employee records / customer API key plus new-integration OAuth guidance; employee change IDs and permission-scoped updates. Ownership and reusable export or independent execution of native workflow artifacts remain unresolved | Getting Started With The API ↗Ownership and reusable export or independent execution of native workflow artifacts remain unresolvedChecked 2026-10-16 |
| What usable data or native definitions can leave before cancellation? | Portable structured records on documented routes; whole-product completeness unverifiedBambooHR employee records / customer API key plus new-integration OAuth guidance; employee change IDs and permission-scoped updates. Structured resource records can be retrieved; complete attachments, versions, relationships and native configuration remain unverified | Get Changed Employee IDs ↗Structured resource records can be retrieved; complete attachments, versions, relationships and native configuration remain unverifiedChecked 2026-10-16 |
SOURCES / SCOPE / HISTORY
Sources and open questions
This review is based on the documentation below. Live account behavior and customer-specific agreements haven’t been tested.
Still to confirm
- Lowest eligible plan and fixed API access fees
- Applicable downstream-use and customer cancellation terms
- Complete file, history and configuration recovery
- Native workflow artifact ownership and independent execution
- Retained replay, checkpoints and gap-recovery procedure
Documentation
Assessment checked 2026-10-16. Each answer retains its source and applicable route; the check date does not establish live account behavior.