API Reference
Become a partner

Table entry created

wbhk
tableEntryCreated

Triggered when an entry is added to an employee's table (including out-of-the-box and custom tables).

Does not apply to Training, Equity, Positions, or Jobs tables.

To identify the row/entry when fetching using the API, use the property that appears in the payload for that table type:

  • id — Included only for non-historical tables (e.g. custom tables, bank accounts). Identifies the entry row. Omitted for historical tables.
  • effectiveDate — Included only for historical tables. Identifies the entry row for that table type. Omitted for non-historical tables.

Each event includes exactly one of effectiveDate or id inside data, depending on whether the table is historical.

To learn more about table types, see Employee data modeling.

When a table entry is created or updated, it may also update employee-level fields (e.g. derived or linked). In that case you will also receive an employee.updated event with the list of changed field IDs in fieldUpdates. Bank accounts and custom tables do not trigger this additional employee.updated event.

In the right panel, open Examples and select Payload Example to see a real payload.

Payload

Base webhook event structure containing common webhook properties

number
required

The company ID

string
enum
required

Event type for table entry created

Allowed:
string
required

The backend-id of the employee that triggered the event, or 'system' for system-triggered events

string
required

The timestamp when the event occurred (ISO 8601-style string)

string
required

The webhook version (e.g., v2)

data
required

Data payload for table.entry.created and table.entry.updated events. Historical tables include effectiveDate only; non-historical tables include numeric id only. The other identifier is omitted from the JSON when not applicable.

Headers
string
required

Base64-encoded signature sent with each webhook request. Use it to verify that the request came from Bob. To verify webhook authenticity, see How does Bob calculate the signature.

string

Present only for custom tables. The URL to call to read this table entry. For out-of-the-box tables the path is well known, but for custom tables this header provides the full URL with the table ID (e.g. category_1716214820047__table_1716214839517) already in the right place. Example: https://api.hibob.com/v1/people/custom-tables/{employeeId}/{custom_table_id}.

Responses
200

Webhook received successfully

Updated 6 days ago 

LoadingLoading…

Updated 6 days ago