Update Table Row v1.1

post

https://{companyDomain}.bamboohr.com/api/v1_1/employees/{id}/tables/{table}/{rowId}

Update an existing row in the specified employee table using the v1.1 table-row update endpoint. Submit the field changes in JSON or XML. This version is largely compatible with v1 and is intended for the same tabular employee data use cases.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Path Params

string

required

The employee ID.

table

string

required

The API name of the table containing the row to update. See the TableName schema for valid standard values; custom tables use a custom prefix. Use GET /api/v1/meta/tables to discover the complete list.

rowId

string

required

The ID of the row to update.

Body Params

A dictionary of table field names and values for creating or updating a row in an employee table. The listed properties are common examples, but accepted fields depend on the specific table being targeted. Some string-valued fields are backed by lists or lookups, so callers should use valid option values from BambooHR metadata rather than assuming any free-text string will persist as entered.

date

The effective date for the row in YYYY-MM-DD format.

location

string

The employee location value for the row.

division

string

The division value for the row.

department

string

The department value for the row.

jobTitle

string

The job title value for the row.

reportsTo

string

The manager or reports-to value for the row.

teams

array of strings

Team values associated with the row.

teams

Headers

content-type

string

enum

Defaults to application/json

Generated from available request content types

Allowed:

Responses

200

Row updated successfully. A 200 response is returned as long as at least one field was updated, even if some fields were skipped due to permissions. No response body is returned.

400

The posted JSON or XML is malformed, or required fields are missing.

403

Permission denied.

404

The employee, table, or row does not exist.

406

One or more field values are invalid.

409

Conflict. The provided field values conflict with business rules or payroll constraints.

412

Precondition failed. The update requires an active pay schedule or other required prerequisite data.