Employee Tables

The Employee Tables API provides access to the details of your company employees's data tables.

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

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.

MethodEndpointLimit per minute
GETList work history for a list of employees100
GETList the lifecycle history for a list of employees100
GETList employment history for a list of employees.100
GETList payroll history (salaries) for a list of employees.100
GETList employee's employment history50
POSTCreates a new employment entry for a given employee10
PUTUpdate an employment entry from a given employee's employment history10
GETRead metadata of custom tables defined50
GETRead metadata for specific custom table50
GETRead all entries of the given custom table50
POSTCreate new custom table entry10
PUTUpdate custom table entry10
DELETEDelete custom table entry10
GETList employee's work history50
POSTCreate a new work entry for a given employee10
PUTUpdate a work entry in the employee's work history table10
DELETEDeletes a work entry from a given employee's work history10
GETList employee's life-cycle status history50
GETList employee's salary history10
POSTCreates a new salary entry for a given employee10
DELETEDeletes a salary entry from the employee's list10
GETList the employee's training records50
POSTCreates a new training records for a given employee10
DELETEDeletes any training records for an employee10
GETList the employee's equity grants50
POSTCreates a new equity grant for a given employee10
PUTUpdates an equity grant for an employee10
DELETEDeletes an equity grant for an employee10
GETList employee's variable payments50
POSTCreates a new variable payment for a given employee10
DELETEDeletes a training record for an employee10
GETRead payroll history20
GETRead all open tasks50
GETRead tasks of a specific employee50
POSTSearch for actual payments100