Connector
Dayforce Connector
Get time and pay data from the systems where work is recorded into Dayforce payroll, without re-keying it and without writing code.
Rapidi connects to Dayforce through a standard REST web service that signs in with a token request, paired with a JSON schema that defines which Dayforce objects can be mapped. It is most often used to bring employee time and pay data from another operational system into Dayforce, as pay adjustments and labor metrics.
- What it connects to
- Dayforce, the cloud HCM platform, through the Dayforce API.
- Which way the data moves
- Most often into Dayforce. The schema makes each Dayforce object available to map into or out of it.
- What you need
- A Dayforce web service user, your client namespace, and the hosted JSON schema for your tenant.
What does this connector actually do?
| What it moves | The Dayforce objects defined in the schema: employees, employee pay adjustments, labor metrics, and employee punches with their meal breaks, transfers and labor metrics. |
|---|---|
| Direction | Most often into Dayforce, as the target for time and pay data from another system. The schema makes each object available to map into or out of Dayforce. |
| How it connects | A standard REST web service, one per Dayforce endpoint, all sharing the same sign-in and the same schema. |
| How it signs in | A token request. Rapidi sends the account, user ID and password to the Dayforce token endpoint, receives an access token, and uses it to call the endpoint for each object. |
| How records are defined | A single hosted JSON schema for the tenant. Each top-level definition matches a Dayforce API endpoint name exactly. |
| How often it runs | On a schedule you set. The shortest interval depends on your plan, from one hour on Entry down to one minute on Unlimited. |
| What you set up once | The REST connection with the Dayforce endpoint, account, user ID, password, token endpoint and the schema address in the Metadata URL field, with SSL on. |
How does the Dayforce schema work?
One JSON schema file covers every Dayforce endpoint for your tenant, and it is the single source of truth for what can be mapped. Adding a Dayforce object to the integration is a schema-only change.
- Add the new endpoint's definition to the hosted JSON schema.
- Click Read Design on the existing web service in Rapidi.
- The new object is ready to map. No new web service, and no change to the endpoint, token endpoint, account or other connection fields.
Changing a field works the same way: update its name, type, description or example in the schema, then Read Design again.
| Object | What it holds |
|---|---|
| Employees | Employee master data: numbers, names, employment dates and status, organisational placement, contact details and manager |
| EmployeePayAdjustments | Pay adjustment transactions: employee, pay code, date, hours, amount, rate, job, department and project |
| LaborMetrics | Labor metric items for a pay adjustment or a punch, such as a job code |
| EmployeePunches | Clock-in and clock-out time entries |
| MealBreaks | Meal break records within an employee punch |
| Transfers | Mid-shift department, job or project transfers within an employee punch |
| PunchLaborMetrics | Labor metric items attached to an employee punch |
| TransferLaborMetrics | Labor metric items attached to a transfer within an employee punch |
What does a typical Dayforce integration move?
The documented example takes field-recorded work from Aimsio, an operational system on an SQL database hosted on Azure, into Dayforce payroll. Jobs, assets and timesheet forms recorded in the field reach Dayforce without manual re-entry.
| Layer | What moves | Why it goes in this order |
|---|---|---|
| Reference data | Jobs and assets, added to Dayforce as labor metrics | Dayforce needs each labor metric to exist before a pay adjustment can reference it, the way an item has to exist before it appears on an order |
| Transactions | Timesheet and form entries, added to Dayforce as employee pay adjustments | Each adjustment carries labor metrics that point at the codes created in the first layer |
Several source forms, such as standard timesheets, bills of lading and crew supervisor timesheets, all write to the same Dayforce pay adjustments object. Running labor metrics first avoids orphaned or failed adjustment records in Dayforce.
Which other systems connect the same way?
Dayforce runs on the generic REST Web Service connection, like Workday. If the source system is a database, the database connectors cover that side.
Connector
REST Web Service
The generic REST connection this connector is built on, for any system with a REST API.
APIs and Protocols
Connector
Workday
The other HR system on the same REST and JSON schema pattern, usually as the source for employee data.
Business Apps
Category
Databases and Warehouses
SQL Server, MySQL, Oracle and the other databases Rapidi reads and writes.
Databases
Where do you go next?
Connectors
Every system Rapidi connects to
The full list, A to Z, with versions and how each one connects.
All connectors
Connector
REST Web Service
The generic REST connection this connector is built on, for any system with a REST API.
APIs and Protocols
Pricing
What Rapidi costs
Four plans, priced per subscription rather than per connector. Adding Dayforce does not change the licence.
Plans
Your setup
Ask about your own Dayforce
Tell us which system records the work and what has to reach payroll, and we will say plainly how Rapidi covers it.
Talk to a consultant
Frequently asked questions
Can Rapidi connect to Dayforce?
Yes. Rapidi connects to Dayforce through a standard REST web service with token-based sign-in, paired with a JSON schema that defines which Dayforce objects can be mapped.
Which way does the data move?
Most often into Dayforce, as the target for employee time and pay data from another operational system. The schema makes each Dayforce object available to map into or out of Dayforce.
Which Dayforce objects can Rapidi reach?
The ones defined in the schema: employees, employee pay adjustments, labor metrics, employee punches, meal breaks, transfers, punch labor metrics and transfer labor metrics.
How does the connection sign in?
With a token request. Rapidi sends the account, user ID and password to the Dayforce token endpoint, receives an access token, and uses it to call the endpoint for each object.
What happens when we need a new Dayforce object or field?
Add its definition to the hosted JSON schema and click Read Design on the existing web service. No new web service and no connection changes are needed.
Why do labor metrics have to sync before pay adjustments?
Each pay adjustment references labor metrics, such as a job code, and Dayforce needs them to exist first. Syncing them first avoids orphaned or failed adjustment records.
How often does the data move?
On a schedule you set. The shortest interval comes from your plan, from one hour on Entry down to one minute on Unlimited.
What does the Dayforce connector cost?
Nothing on its own. Rapidi is priced per subscription plan rather than per connector, so adding Dayforce does not change the licence.
Does your payroll run on Dayforce?
Tell us which system records the work and what has to reach Dayforce, and we will tell you plainly what the setup involves.