This article outlines the supported fields, expected formats, and integration guidelines for HR data synchronisation between Ceridian Dayforce and Thrive LMS via API.
Supported Fields
Below is the list of fields supported in the integration:
Thrive Field | Ceridian Dayforce Field | Standard or Custom | Example Value |
|---|---|---|---|
Ref | Employee ID, Payroll ID, Email | Required Standard | 123455 |
First Name | FirstName | Required Standard | |
Last Name | LastName | Required Standard | |
Required Standard | |||
Start Date | StartDate/Hire Date/Effective Date | Standard Optional | Employee's official start date DD-MM-YYYY |
Job Details (Optional Fields — Not Required for User Profile Creation)
Thrive Field | Ceridian Dayforce Field | Standard or custom | Example Value |
|---|---|---|---|
Job Title | Position.ShortName | ||
Standard Optional | Director of Learning & Development | ||
Manager | Manager ID | Standard Optional | Name of the employee’s direct manager
|
Location | Data.HomeOrganization.ShortName | Optional | London |
Country | Location.LegalEntity.Country.XRefCode | Optional | USA |
Employee Type | PositionTerm.LongName | Optional | Regular |
Department | Position.Department.ShortName | Optional | Learning and Development |
Important:
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
Cerdian Dayforce HCM API will send user data in a structured JSON format to Thrive Link.
Thrive 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 according to the latest records received from Ceridian Dayforce HCM.
Security and Authentication
To authenticate Dayforce HCM (formerly Ceridian Dayforce HCM) using your credentials, you will need to provide the following information:
Company ID
Credentials
This guide will walk you through finding or creating those credentials within Dayforce.
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 Dayforce.