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 .

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

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