Employee tables endpoints provide access to table entries of employees' historical data and other types of information stored in tables holding multiple rows.

Reading employee tables

Employee data includes tables that store several entries of data per employee. To access data stored in the employee table entries, use the employee tables endpoints below.

Before you start, explore How to read employee data to learn how to map the fields and their properties and how to process the response payload.

Required Permissions

In Bob, employee tables are systematically organized within categories. This means that when you enable permissions to the Service User you enable the permission to the category and as a result, to all the tables that reside in that category.

Before accessing a table, ensure the service user has permissions to access the relevant category, just like you would do with a user within Bob.

For example, if you need the service user to pull employee work history, you would set permissions to:

People’s data permissions:
- People > Work > View selected employees' Work section histories
  (this gives you access to all the rows in the table)
- People > Work > View selected employees' Work sections
  (this gives you access to the current effective row)
Access rights permissions:
- Select “Everyone” (if you need to access all employees).
- Or include the employee in the list of selected users.

To learn more, see Categories and Permissions.

To learn more about permissions, see Setting permissions to Service Users .

📘
Note: When field-level permissions (FLP) are enabled and the service user has partial column access, the response includes a restricted_columns object indicating which columns were filtered. See Field level permissions for details.

Pagination

Some of the endpoints use cursor-based pagination to go through the results. It's the fastest and most reliable way to handle a large number of items.

To learn more, see Pagination in Bob's API.

Rate limiting

Rate limits are restrictions that our API imposes on the number of times a user can access our endpoints within a specified period of time. To learn more about rate limiting best practices, see Rate limiting.

Below is a table detailing the rate limits for each endpoint in the Employee tables endpoints.

Method	Endpoint	Limit per minute
GET	List work history for a list of employees	100
GET	List the lifecycle history for a list of employees	100
GET	List employment history for a list of employees.	100
GET	List payroll history (salaries) for a list of employees.	100
GET	List employee's employment history	50
POST	Creates a new employment entry for a given employee	10
PUT	Update an employment entry from a given employee's employment history	10
GET	List employee's work history	50
POST	Create a new work entry for a given employee	10
PUT	Update a work entry in the employee's work history table	10
DELETE	Deletes a work entry from a given employee's work history	10
GET	List employee's life-cycle status history	50
GET	List employee's salary history	10
POST	Creates a new salary entry for a given employee	10
DELETE	Deletes a salary entry from the employee's list	10
GET	List the employee's training records	50
POST	Creates a new training records for a given employee	10
DELETE	Deletes any training records for an employee	10
GET	Read payroll history	20
GET	List the employee's equity grants	50
POST	Creates a new equity grant for a given employee	10
PUT	Updates an equity grant for an employee	10
DELETE	Deletes an equity grant for an employee	10
GET	List employee's variable payments	50
POST	Creates a new variable payment for a given employee	10
DELETE	Deletes a training record for an employee	10
GET	Read all open tasks	50
GET	Read tasks of a specific employee	50
POST	Search for actual payments	100
GET	List employee's bank accounts	50
POST	Create a new bank account entry for a given employee.	10
PUT	Update a bank account entry in the employee's bank accounts table.	10
DELETE	Deletes a bank account entry from a given employee's bank accounts table.	10