HiBob

Sync employee data from HiBob HR platform.

Overview
Setup Guide
Permissions
Troubleshooting

Connect Parable to HiBob using a service user for automated HR data access.

People Data

Profiles, employment, org structure

Time & Attendance

Time off, attendance records

Data streams

This Provider Plugin defines 3 data streams.

Stream	Description	Sync
`employee`	Active employees	full
`job_roles`	Job catalog roles	full
`position_budget`	Position budget entries	full

What You’ll Need

Credential	What it is
Service ID	Bob service user identifier
Token	Service user API token

Info: Setup access in HiBob. These steps require Administrator, or a colleague with equivalent permissions who can create credentials for you. If that is not you, ask your HiBob administrator.

Admin role in HiBob
Permission to create service users

Step 1: Access Service Users

Log in to HiBob as admin
Go to Settings → Integrations
Click Service Users

Step 2: Create Service User

Click Add Service User
Fill in:

Field	Value
Name	`Parable Integration`
Description	Integration user for Parable

Step 3: Configure Permissions

A service user starts with no access. Add it to a permission group, and give the group View on these categories:

✅ Root, About, Employment and Work: the employee directory, including each employee’s manager.
✅ Internal: each employee’s lifecycle status, termination date and termination reason.
✅ Personal and Payroll: only if you want those categories in the employee stream.
✅ Job catalog and Workforce planning: only if you turn on job_roles or position_budget.

Under Access data for, choose every employee you want in the employee stream. Parable asks HiBob for active employees only, so the employee table holds no former employees. When HiBob terminates an employee, it stops returning them, and Parable treats them as removed at the next sync. They then read no HiBob row. This holds also when the group has no View on Internal.

Warning: Only grant permissions for data you need to access.

Step 4: Generate Token

Click Create or Save
Copy the Service User ID
Generate and copy the Token

Warning: Store the token securely — it won’t be shown again!

Step 5: Enter values in the form

Enter Service User ID, Token, and Service URL in the Provider form.
Click Save & test connection.

Who reads HiBob rows

HiBob decides who sees a record by permission group and data category. The HiBob API returns no permission group, so Parable applies one rule that the API states: an employee’s row opens to that employee.This applies while your Workspace turns on Enforce source permissions, and on a table where a Provider Policy rule reads Source permissions (Source permissions):

Table	Who reads a row
`employee`	The employee the row is about
`position_budget`	Only people with All data access, and the roles that a Provider Policy rule gives All rows or Rows where
`job_roles`	Every active HiBob employee

Parable matches a person to their HiBob employee by the employee’s email.
A manager reads only their own employee row. Their reports’ rows stay closed to them. Parable reads each employee’s manager from work.manager, so a Workspace can choose HiBob as the source of Pulse manager reads.
An employee reads only their own employee row, not the company directory: the row also holds the personal, payroll and about categories.
An employee that HiBob terminates, or no longer returns, reads no HiBob row after the next sync, with no action from you.
A person with no HiBob employee reads no HiBob row.
A person with All data access, such as a Workspace administrator, reads every row. Each such read is recorded in your Workspace’s audit events.

While Enforce source permissions is off, a table that no Provider Policy names is read in full by everyone whose role can read it.To let your HR team read every HiBob row while Enforce source permissions is on, give their role All rows on each HiBob table in Protection → Provider Policies.Parable asks HiBob for machine values (humanReadable: APPEND). So work.manager holds the manager’s employee ID, a list value such as work.department can hold its list item ID, and dates are ISO dates. The readable names and dates are in the humanReadable column.

Employee

Developer identifier: employeeEmployee. Active employees.

Enables: Reconcile active HiBob employee records to work identity, organization, manager, site, and employment dates.
Scope: Reads every record from HiBob’s /v1/people/search operation on each sync. The request asks for machine values and appends HiBob’s readable values (humanReadable: APPEND), so work.manager holds the manager’s employee ID. The request sends showInactive: false, so HiBob returns active employees only: an employee that HiBob terminates leaves the read, and the next complete read marks the row removed. This stream is opt-in. Visibility follows the HiBob service user’s granted data categories and employee population. The stream does not include records that the credential, the parent records, the configured filters, or the provider API leave out. A later complete read can treat a previously seen record that is absent as removed.

About

Developer identifier: employee.aboutAbout. About section. It preserves the nested context needed to interpret the parent employee.

Enables: Attribute about in employee.about to the parent employee; identify parent records where that nested about object is absent.
Interpretation: HiBob reports about as a nested object on each employee; optional children may be absent from a valid response.

Creation Date Time

Developer identifier: employee.creationDateTimeCreation Date Time. Record creation timestamp. It anchors the employee on the provider’s reported timeline.

Enables: Order Employee by creation date time in employee.creationDateTime and isolate records inside an exact provider reporting window.
Interpretation: HiBob reports creation date time as a timestamp on each employee; timezone and precision follow this API field, and absence is not an inferred event time.

Display Name

Developer identifier: employee.displayNameDisplay Name. Display name. It distinguishes the provider-defined display name state or classification for the employee.

Enables: Label each employee with display name from employee.displayName; distinguish records that share that display name but have different HiBob identifiers.
Interpretation: HiBob reports display name as display text for each employee; names are mutable and are not stable identities. Parable uses this field as the person’s name.

Developer identifier: employee.emailEmail. Employee email address. It supplies the provider-reported address or location facet for the employee, not a residency determination.

Enables: Attribute each employee to a person or account by the exact email in employee.email; identify addresses that do not match the HiBob directory.
Interpretation: HiBob reports email as an address on each employee; aliases, casing, and unverified addresses can prevent a one-to-one person match. Parable uses this field as the account’s email when it links the account to a person. Under source permissions, it is the employee’s primary principal email, and the employee gets a token for its domain.

First Name

Developer identifier: employee.firstNameFirst Name. First name. It gives the employee a human-readable provider label while its identifier remains the stable reference.

Enables: Label each employee with first name from employee.firstName; distinguish records that share that display name but have different HiBob identifiers.
Interpretation: HiBob reports first name as display text for each employee; names are mutable and are not stable identities.

Human Readable

Developer identifier: employee.humanReadableHuman Readable. The readable form of the employee’s values, such as the manager’s name and the department’s name.

Enables: Label employee.work.manager, employee.work.department and the other values that HiBob returns as IDs with the names that HiBob shows.
Interpretation: HiBob adds this node because the request sets humanReadable: APPEND. It repeats the employee’s categories (work, personal, payroll and the others) with readable values, so it can hold personal and payroll values. Dates use the company’s date format.

Developer identifier: employee.idID. Unique employee identifier. It provides the reference needed to connect the employee to the corresponding provider object.

Enables: Match repeated employee entries on ID in employee.id. Only entries that share this key are the same record.
Interpretation: HiBob reports ID as an identifier in its employee namespace; it is not a universal identity outside HiBob. It is the record key. Parable uses this field as the account’s ID when it links the account to a person. Under source permissions, it is the employee’s user principal, and the employee’s own row opens to that employee only, and to All data access.

Internal

Developer identifier: employee.internalInternal. Internal HR fields including lifecycle status. It preserves the nested context needed to interpret the parent employee.

Enables: Attribute internal in employee.internal to the parent employee; identify parent records where that nested internal object is absent.
Interpretation: HiBob reports internal as a nested object on each employee; optional children may be absent from a valid response.

Lifecycle Status

Developer identifier: employee.internal.lifecycleStatusLifecycle Status. Current lifecycle status of the employee. It distinguishes the provider-defined lifecycle status state or classification for the HiBob employee internal.

Enables: Segment HiBob employee internal entries in Employee by lifecycle status in employee.internal.lifecycleStatus; compare counts only within the same HiBob taxonomy.
Interpretation: HiBob reports lifecycle status as a label from its own taxonomy on each HiBob employee internal; preserve unknown labels rather than mapping them by assumption.

Status

Developer identifier: employee.internal.statusStatus. Whether the employee is active in HiBob.

Enables: Separate active employees from inactive employees in employee.internal.status.
Interpretation: HiBob reports Active or Inactive; an inactive employee is usually terminated or a former employee. Under source permissions, an Inactive employee holds no HiBob token. The request asks for active employees only (showInactive: false), so HiBob leaves out a terminated employee, also when the service user cannot read the internal category.

Termination Date

Developer identifier: employee.internal.terminationDateTermination Date. Termination date if applicable. It anchors the employee on the provider’s reported timeline.

Enables: Order Employee by termination date in employee.internal.terminationDate and isolate records inside an exact provider reporting window.
Interpretation: HiBob reports termination date as a calendar date on each HiBob employee internal; its grain is one day and no time of day should be inferred.

Termination Reason

Developer identifier: employee.internal.terminationReasonTermination Reason. Reason for termination if applicable. It supplies the returned termination reason text needed to understand the HiBob employee internal in context.

Enables: Search the returned termination reason text in employee.internal.terminationReason and attribute each match to its parent employee and reported author when available.
Interpretation: HiBob supplies termination reason as returned text on each HiBob employee internal; truncation, formatting, and access boundaries can limit completeness.

Payroll

Developer identifier: employee.payrollPayroll. Payroll details. It preserves the nested context needed to interpret the parent employee.

Enables: Attribute payroll in employee.payroll to the parent employee; identify parent records where that nested payroll object is absent.
Interpretation: HiBob reports payroll as a nested object on each employee; optional children may be absent from a valid response.

Personal

Developer identifier: employee.personalPersonal. Personal details. It preserves the nested context needed to interpret the parent employee.

Enables: Attribute personal in employee.personal to the parent employee; identify parent records where that nested personal object is absent.
Interpretation: HiBob reports personal as a nested object on each employee; optional children may be absent from a valid response.

Surname

Developer identifier: employee.surnameSurname. Employee surname (HiBob wire key; not lastName). It supplies the surname profile facet used to reconcile or attribute the employee.

Enables: Reconcile the employee’s surname in employee.surname with its provider profile or directory identity; confirm ambiguous matches with the stable provider ID.
Interpretation: HiBob reports surname as a mutable profile or directory attribute on each employee; it may be absent, shared, or non-unique.

Work

Developer identifier: employee.workWork. Work details including title, department, and manager. It preserves the nested context needed to interpret the parent employee.

Enables: Attribute work in employee.work to the parent employee; identify parent records where that nested work object is absent.
Interpretation: HiBob reports work as a nested object on each employee; optional children may be absent from a valid response.

Custom

Developer identifier: employee.work.customCustom. Custom work fields. It preserves the nested context needed to interpret the parent employee.

Enables: Attribute custom in employee.work.custom to the parent employee; identify parent records where that nested custom object is absent.
Interpretation: HiBob reports custom as a nested object on each HiBob employee work; optional children may be absent from a valid response.

Department

Developer identifier: employee.work.departmentDepartment. The employee’s department. It supplies the department profile facet used to reconcile or attribute the HiBob employee work.

Enables: Reconcile the employee’s department in employee.work.department with its provider profile or directory identity; confirm ambiguous matches with the stable provider ID.
Interpretation: HiBob reports department as a mutable profile or directory attribute on each HiBob employee work; it may be absent, shared, or non-unique. The request asks for machine values, so HiBob can return the department’s list item ID here; the readable name is in employee.humanReadable.

Manager

Developer identifier: employee.work.managerManager. The HiBob employee ID of the employee’s direct manager.

Enables: Join each employee in employee.work.manager to the manager’s employee.id row, and read the reporting line from it.
Interpretation: HiBob returns the manager’s employee ID because the request asks for machine values; the manager’s name is in employee.humanReadable. It is empty for an employee with no manager. Under source permissions, it is the employee’s reporting line to a manager of the same HiBob account. No HiBob table opens to managers, so the line gives the manager no HiBob row of the employee.

Reports To

Developer identifier: employee.work.reportsToReports To. Reports-to reference. It preserves the nested context needed to interpret the parent employee.

Enables: Attribute reports to in employee.work.reportsTo to the parent employee; identify parent records where that nested reports to object is absent.
Interpretation: HiBob reports reports to as a nested object on each HiBob employee work; optional children may be absent from a valid response.

Site

Developer identifier: employee.work.siteSite. Work site or office location. It supplies the provider-reported address or location facet for the HiBob employee work, not a residency determination.

Enables: Group Employee by site in employee.work.site without treating that user, device, or request attribute as a data-residency signal.
Interpretation: HiBob reports site as a user, device, request, or resource location attribute on each HiBob employee work; it does not establish where data is stored or processed.

Start Date

Developer identifier: employee.work.startDateStart Date. Employment start date. It anchors the employee on the provider’s reported timeline.

Enables: Filter Employee by start date in employee.work.startDate; pair that boundary with the corresponding end before measuring elapsed time.
Interpretation: HiBob reports start date as a calendar date on each HiBob employee work; its grain is one day and no time of day should be inferred.

Tenure

Developer identifier: employee.work.tenureTenure. Tenure details. It preserves the nested context needed to interpret the parent employee.

Enables: Attribute tenure in employee.work.tenure to the parent employee; identify parent records where that nested tenure object is absent.
Interpretation: HiBob reports tenure as a nested object on each HiBob employee work; optional children may be absent from a valid response.

Title

Developer identifier: employee.work.titleTitle. Job title. It gives the HiBob employee work a human-readable provider label while its identifier remains the stable reference.

Enables: Label each HiBob employee work with title from employee.work.title; distinguish records that share that display name but have different HiBob identifiers.
Interpretation: HiBob reports title as display text for each HiBob employee work; names are mutable and are not stable identities.

Job Roles

Developer identifier: job_rolesJob Roles. Job catalog roles.

Enables: Verify the lifecycle and assignment of each HiBob job role.
Scope: Reads every record from HiBob’s /v1/job-catalog/job-roles operation on each sync. This stream is opt-in. Visibility follows the HiBob service user’s granted data categories and employee population. The stream does not include records that the credential, the parent records, the configured filters, or the provider API leave out. A later complete read can treat a previously seen record that is absent as removed.

Job Role Description

Developer identifier: job_roles./jobRole/descriptionJob Role Description. Job role description. It preserves the nested context needed to interpret the parent job role.

Enables: Attribute job role description in job_roles./jobRole/description to the parent job role; identify parent records where that nested job role description object is absent.
Interpretation: HiBob reports job role description as a nested object on each job role; optional children may be absent from a valid response.

Human Readable

Developer identifier: job_roles./jobRole/description.humanReadableHuman Readable. Human-readable representation of the value when includeHumanReadable is set. It gives the HiBob path keyed value a human-readable provider label while its identifier remains the stable reference.

Enables: Display the human readable from job_roles./jobRole/description.humanReadable for each HiBob path keyed value; resolve duplicate or changed labels through the provider ID rather than the text.
Interpretation: HiBob supplies human readable as mutable display text on each HiBob path keyed value; it is not a stable identity.

Value

Developer identifier: job_roles./jobRole/description.valueValue. Raw field value (string, number, boolean, or object depending on field). It must be interpreted with the enclosing provider field name, type, or custom schema for the HiBob path keyed value.

Enables: Interpret job_roles./jobRole/description.value with the enclosing custom field name, declared type, and provider schema; compare only records that share that contract.
Interpretation: HiBob reports value under the enclosing custom or typed field contract on each HiBob path keyed value; compare it only with values from the same provider key and type.

Job Role ID

Developer identifier: job_roles./jobRole/idJob Role ID. Job role ID. It preserves the nested context needed to interpret the parent job role.

Enables: Match repeated job role entries on job role ID in job_roles./jobRole/id. Only entries that share this key are the same record.
Interpretation: HiBob reports job role ID as a nested object on each job role; optional children may be absent from a valid response. It is the record key.

Job Role Name

Developer identifier: job_roles./jobRole/nameJob Role Name. Job role name. It preserves the nested context needed to interpret the parent job role.

Enables: Attribute job role name in job_roles./jobRole/name to the parent job role; identify parent records where that nested job role name object is absent.
Interpretation: HiBob reports job role name as a nested object on each job role; optional children may be absent from a valid response.

Position Budget

Developer identifier: position_budgetPosition Budget. Position budget entries.

Enables: Compare authorized position budget amounts by position, currency, pay period, and effective workforce-planning context.
Scope: Reads every record from HiBob’s /v1/positions/position-budget/search operation on each sync. HiBob requires a filter on this operation and accepts only /positionBudget/id with equals or notEqual. The request asks for each entry whose ID is not 0, a value that no HiBob budget ID takes, so the filter keeps every entry. This stream is opt-in. Visibility follows the HiBob service user’s granted data categories and employee population. Use is limited to authorized workforce and payroll reconciliation; the records are not invoices and do not support performance inference. A later complete read can treat a previously seen record that is absent as removed.

Position Budget Converted Total Cost Currency Value

Developer identifier: position_budget./positionBudget/convertedTotalCostCurrencyValuePosition Budget Converted Total Cost Currency Value. HiBob reports the position-budget attribute at /positionBudget/convertedTotalCostCurrencyValue. It preserves the nested context needed to interpret the parent position budget.

Enables: Attribute position budget converted total cost currency value in position_budget./positionBudget/convertedTotalCostCurrencyValue to the parent position budget; identify parent records where that nested position budget converted total cost currency value object is absent.
Interpretation: HiBob reports position budget converted total cost currency value as a nested object on each position budget; optional children may be absent from a valid response. Use is limited to authorized workforce or payroll reconciliation and must not be used to infer employee performance. Any monetary amount is a provider HR or payroll record at its stated currency and pay basis, not an invoice.

Human Readable

Developer identifier: position_budget./positionBudget/convertedTotalCostCurrencyValue.humanReadableHuman Readable. Human-readable representation of the value when includeHumanReadable is set. It gives the HiBob path keyed value a human-readable provider label while its identifier remains the stable reference.

Enables: Display the human readable from position_budget./positionBudget/convertedTotalCostCurrencyValue.humanReadable for each HiBob path keyed value; resolve duplicate or changed labels through the provider ID rather than the text.
Interpretation: HiBob supplies human readable as mutable display text on each HiBob path keyed value; it is not a stable identity. Use is limited to authorized workforce or payroll reconciliation and must not be used to infer employee performance.

Value

Developer identifier: position_budget./positionBudget/convertedTotalCostCurrencyValue.valueValue. Raw field value (string, number, boolean, or object depending on field). It must be interpreted with the enclosing provider field name, type, or custom schema for the HiBob path keyed value.

Enables: Interpret position_budget./positionBudget/convertedTotalCostCurrencyValue.value with the enclosing custom field name, declared type, and provider schema; compare only records that share that contract.
Interpretation: HiBob reports value under the enclosing custom or typed field contract on each HiBob path keyed value; compare it only with values from the same provider key and type. Use is limited to authorized workforce or payroll reconciliation and must not be used to infer employee performance.

Position Budget Currency

Developer identifier: position_budget./positionBudget/CurrencyPosition Budget Currency. HiBob reports the position-budget attribute at /positionBudget/Currency. It preserves the nested context needed to interpret the parent position budget.

Enables: Attribute position budget currency in position_budget./positionBudget/Currency to the parent position budget; identify parent records where that nested position budget currency object is absent.
Interpretation: HiBob reports position budget currency as a nested object on each position budget; optional children may be absent from a valid response. Use is limited to authorized workforce or payroll reconciliation and must not be used to infer employee performance. Any monetary amount is a provider HR or payroll record at its stated currency and pay basis, not an invoice.

Position Budget Expected Base Salary Currency Value

Developer identifier: position_budget./positionBudget/expectedBaseSalaryCurrencyValuePosition Budget Expected Base Salary Currency Value. HiBob reports the position-budget attribute at /positionBudget/expectedBaseSalaryCurrencyValue. It preserves the nested context needed to interpret the parent position budget.

Enables: Attribute position budget expected base salary currency value in position_budget./positionBudget/expectedBaseSalaryCurrencyValue to the parent position budget; identify parent records where that nested position budget expected base salary currency value object is absent.
Interpretation: HiBob reports position budget expected base salary currency value as a nested object on each position budget; optional children may be absent from a valid response. Use is limited to authorized workforce or payroll reconciliation and must not be used to infer employee performance. Any monetary amount is a provider HR or payroll record at its stated currency and pay basis, not an invoice.

Position Budget Expected Variable Pay Currency Value

Developer identifier: position_budget./positionBudget/expectedVariablePayCurrencyValuePosition Budget Expected Variable Pay Currency Value. HiBob reports the position-budget attribute at /positionBudget/expectedVariablePayCurrencyValue. It preserves the nested context needed to interpret the parent position budget.

Enables: Attribute position budget expected variable pay currency value in position_budget./positionBudget/expectedVariablePayCurrencyValue to the parent position budget; identify parent records where that nested position budget expected variable pay currency value object is absent.
Interpretation: HiBob reports position budget expected variable pay currency value as a nested object on each position budget; optional children may be absent from a valid response. Use is limited to authorized workforce or payroll reconciliation and must not be used to infer employee performance. Any monetary amount is a provider HR or payroll record at its stated currency and pay basis, not an invoice.

Position Budget ID

Developer identifier: position_budget./positionBudget/idPosition Budget ID. HiBob reports the position-budget attribute at /positionBudget/ID. It preserves the nested context needed to interpret the parent position budget.

Enables: Match repeated position budget entries on position budget ID in position_budget./positionBudget/id. Only entries that share this key are the same record.
Interpretation: HiBob reports position budget ID as a nested object on each position budget; optional children may be absent from a valid response. It is the record key. Use is limited to authorized workforce or payroll reconciliation and must not be used to infer employee performance. Any monetary amount is a provider HR or payroll record at its stated currency and pay basis, not an invoice.

Position Budget Pro Rated Cost Currency Value

Developer identifier: position_budget./positionBudget/proRatedCostCurrencyValuePosition Budget Pro Rated Cost Currency Value. HiBob reports the position-budget attribute at /positionBudget/proRatedCostCurrencyValue. It preserves the nested context needed to interpret the parent position budget.

Enables: Attribute position budget pro rated cost currency value in position_budget./positionBudget/proRatedCostCurrencyValue to the parent position budget; identify parent records where that nested position budget pro rated cost currency value object is absent.
Interpretation: HiBob reports position budget pro rated cost currency value as a nested object on each position budget; optional children may be absent from a valid response. Use is limited to authorized workforce or payroll reconciliation and must not be used to infer employee performance. Any monetary amount is a provider HR or payroll record at its stated currency and pay basis, not an invoice.

Position Budget Salary Pay Period

Developer identifier: position_budget./positionBudget/salaryPayPeriodPosition Budget Salary Pay Period. HiBob reports the position-budget attribute at /positionBudget/salaryPayPeriod. It preserves the nested context needed to interpret the parent position budget.

Enables: Attribute position budget salary pay period in position_budget./positionBudget/salaryPayPeriod to the parent position budget; identify parent records where that nested position budget salary pay period object is absent.
Interpretation: HiBob reports position budget salary pay period as a nested object on each position budget; optional children may be absent from a valid response. Use is limited to authorized workforce or payroll reconciliation and must not be used to infer employee performance. Any monetary amount is a provider HR or payroll record at its stated currency and pay basis, not an invoice.

Position Budget Total Position Cost Currency Value

Developer identifier: position_budget./positionBudget/totalPositionCostCurrencyValuePosition Budget Total Position Cost Currency Value. HiBob reports the position-budget attribute at /positionBudget/totalPositionCostCurrencyValue. It preserves the nested context needed to interpret the parent position budget.

Enables: Attribute position budget total position cost currency value in position_budget./positionBudget/totalPositionCostCurrencyValue to the parent position budget; identify parent records where that nested position budget total position cost currency value object is absent.
Interpretation: HiBob reports position budget total position cost currency value as a nested object on each position budget; optional children may be absent from a valid response. Use is limited to authorized workforce or payroll reconciliation and must not be used to infer employee performance. Any monetary amount is a provider HR or payroll record at its stated currency and pay basis, not an invoice.

Position Budget Update Effective Date

Developer identifier: position_budget./positionBudget/updateEffectiveDatePosition Budget Update Effective Date. HiBob reports the position-budget attribute at /positionBudget/updateEffectiveDate. It preserves the nested context needed to interpret the parent position budget.

Enables: Attribute position budget update effective date in position_budget./positionBudget/updateEffectiveDate to the parent position budget; identify parent records where that nested position budget update effective date object is absent.
Interpretation: HiBob reports position budget update effective date as a nested object on each position budget; optional children may be absent from a valid response. Use is limited to authorized workforce or payroll reconciliation and must not be used to infer employee performance. Any monetary amount is a provider HR or payroll record at its stated currency and pay basis, not an invoice.

Position Budget Variable Pay Period

Developer identifier: position_budget./positionBudget/variablePayPeriodPosition Budget Variable Pay Period. HiBob reports the position-budget attribute at /positionBudget/variablePayPeriod. It preserves the nested context needed to interpret the parent position budget.

Enables: Attribute position budget variable pay period in position_budget./positionBudget/variablePayPeriod to the parent position budget; identify parent records where that nested position budget variable pay period object is absent.
Interpretation: HiBob reports position budget variable pay period as a nested object on each position budget; optional children may be absent from a valid response. Use is limited to authorized workforce or payroll reconciliation and must not be used to infer employee performance. Any monetary amount is a provider HR or payroll record at its stated currency and pay basis, not an invoice.

Error	Meaning	Solution
`401 Unauthorized`	Invalid credentials	Verify ID and token
`403 Forbidden`	Missing permission	Add required permission to service user
`404 Not Found`	Resource doesn’t exist	Check the Service URL in the connection

HiBob API — Official API documentation

​People Data

​Time & Attendance

​Data streams

​HiBob

​What You’ll Need

​Step 1: Access Service Users

​Step 2: Create Service User

​Step 3: Configure Permissions

​Step 4: Generate Token

​Step 5: Enter values in the form

​Who reads HiBob rows

People Data

Time & Attendance

Data streams

HiBob

What You’ll Need

Step 1: Access Service Users

Step 2: Create Service User

Step 3: Configure Permissions

Step 4: Generate Token

Step 5: Enter values in the form

Who reads HiBob rows