This document outlines the supported fields, expected formats, and integration guidelines for HR data synchronisation between HiBob and Thrive Learning LMS via API.
Supported Fields
Below is the list of fields supported in the integration:
User Information
Thrive Field | HiBob Field | Standard or Custom | Example Value |
---|---|---|---|
Ref | Employee ID, Payroll ID, Email | Required Standard | 123455 |
First Name | /root/firstName.value | Required Standard | |
Last Name | /root/surname.value | Required Standard | |
/root/email.value | Required Standard | ||
Start Date | work.startDate/work effective date | Standard Optional | Employee's official start date DD-MM-YYYY |
Job Details (Optional Fields, Not Required for User Profile Creation)
Thrive Field | HiBob Field | Standard or custom | Example Value |
---|---|---|---|
Job Title | Job title | Standard Optional | Director of Learning & Development |
Manager | work.Manager | Standard Optional | Name of the employee’s direct manager
|
Location | site | Optional | London |
Country | country | Optional | UK |
Department | work.department | Optional | Learning and Development |
Note:
Optional fields must be pre-configured in the Thrive UI before enabling the integration for the data to be ingested.
Data Format and Expectations
Email addresses must be unique within the system.
Required fields must be provided for every user record.
Note:
Example values may be different in format in comparison to the above values.
Integration Methodology
HiBob API will send user data in a structured JSON format to Thrive Link.
Thrive LMS will process and validate incoming data.
Any discrepancies or errors (e.g., missing required fields, incorrect formats) will be logged and flagged for review.
Data will be updated in Thrive LMS according to the latest records received from HiBob.
Security and Authentication
To authenticate HiBob using a Service Account, you will need to provide the following information:
Service Account User ID
Service Account Token
This guide will walk you through finding or creating those credentials within HiBob.
Testing and Deployment
A staging environment will be available for integration testing.
Test cases will validate:
Field mappings and data integrity.
Error handling for missing/incorrect data.
System behaviour for updates, deletions, and new entries.
Deployment will be monitored to ensure stability.
What is not supported via Merge.dev
Bi-directional syncing of user data.
Sending skills data to Thrive.
Sending tags, compliance and completions data from Thrive to HiBob.