Skip to content
Human resources

Connect Ceridian Dayforce to any app with two-way sync.

Two-way sync Ceridian Dayforce across all your CRMs, databases, data warehouses, EDI systems, and AI tools, with custom workflows tailored to your data.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Object catalog

What Stacksync syncs in Ceridian Dayforce.

These objects sync between Ceridian Dayforce and any connected system, with field-level mapping and conflict resolution. Custom fields are picked up from the live schema where Ceridian Dayforce exposes them.

Employee (HR / Person Details)
Core worker record keyed by XRefCode; GET Employees returns matching XRefCodes, then a per-employee GET fetches full HR details. New hires are added with POST and edits made with PATCH, so it is read and write.
Employment Status
Effective-dated employment status and type (active, leave, terminated) that drives active/terminated state for downstream provisioning; read, and writable as new dated status records.
Work Assignments
Effective-dated position, department, location, and org-unit assignment; the most-synced record for org charts, provisioning, and analytics. Read and updatable via PATCH.
Compensation Summary & Pay Adjustments
Compensation Summary returns pay rate and frequency for reporting; Employee Pay Adjustments are written as effective-dated records via PATCH to post pay changes back to Dayforce.
Employee Punches & Raw Clock Entries
Time-and-attendance punches; raw clock entries are added with POST and punches removed with DELETE, so time data flows both ways between Dayforce and scheduling or workforce tools.
Employee Schedules
Shift and schedule assignments; created and updated through POST and PATCH schedule endpoints and paged with pageSize, used to push schedules from a WFM tool or pull them for analytics.
Org Units, Departments, Jobs & Positions
Configuration reference data; POST creates org units and departments and PATCH updates job, position, department, and org-unit data. Used to resolve and validate XRefCodes when mapping employee writes.
Time Away From Work & Balances
Time-off requests and accrual balances read per employee; pulled into scheduling, payroll, or absence-reporting databases and used to reconcile leave against downstream systems.
API surface

How Stacksync connects to Ceridian Dayforce.

The connector runs on Ceridian Dayforce's native API. Stacksync manages authentication, rate limits, retries, and schema changes so your team does not maintain integration code.

Connection
REST API (Dayforce RESTful Web Services, v1/v2), JSON payloads
Authentication
HTTP Basic authentication with a dedicated Web Services user plus the client namespace (Company ID), or an OAuth 2.0 access token from the Dayforce identity endpoint (POST dfid.dayforcehcm.com/connect/token, client_id Dayforce.HCMAnywhere.Client). Token-based auth is recommended, and the Web Services role with the Read Data subfeature must be enabled on the account.
Change detection
No CDC stream. Broad change detection uses delta polling on GET Employees with filterUpdatedStartDate/filterUpdatedEndDate and filterUpdatedEntities to pull only records changed in a window. Dayforce also has native Event Notifications (the Notification Publisher) for lifecycle events — hire, rehire, terminate, and workflow validation — delivered by push to a receiver service or by querying unacknowledged notifications; the publisher runs roughly hourly and each notification must be acknowledged.
Rate limits
Dayforce does not publish numeric rate limits; thresholds vary by tenant and exceeding them returns HTTP 429, so large employee reads are paged (pageSize) and throttled with backoff. Employee list calls return XRefCodes only, so each employee needs a follow-up GET.

Sync directions

  • Read Supported
  • Write Supported
  • Change data capture Not available
  • Webhooks Supported
Ceridian Dayforce connector documentation
What ships with Ceridian Dayforce

Connect Ceridian Dayforce for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every connection.

Real-time

Two-way sync

Changes in Ceridian Dayforce instantly reflect across connected systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Ceridian Dayforce data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Ceridian Dayforce record.

Observability

Monitoring

Track your Ceridian Dayforce sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions.

Use cases

What teams run on the Ceridian Dayforce connector.

Dayforce (formerly Ceridian Dayforce) is a cloud HCM and payroll platform used by mid-market and enterprise employers, owned by HRIS admins and HR/payroll operations. It is the system of record for the worker — person and HR details, employment status, work assignments (position, department, location, org unit), compensation, time, schedules, and payroll. Because payroll runs from it and every employee has a record, IT provisioning, ERP, benefits, and reporting systems all depend on current worker and org data flowing out of Dayforce and, for hires, terminations, and job changes, back into it.

  • HRIS admins
  • HR / People operations
  • Payroll teams
  • IT identity & provisioning
  • Workforce management / time & attendance analysts
  1. Two-way sync of Employee and Work Assignment data (position, department, location, org unit) into Postgres so provisioning, internal apps, and analytics read current worker and org data in SQL while HR keeps editing in Dayforce.

  2. Push new hires (Employee, Employment Status, Work Assignment) from an ATS or onboarding tool into Dayforce with POST once a candidate is hired, pre-fetching valid XRefCodes for department, position, location, and pay group.

  3. React to Dayforce Event Notifications for hire, rehire, and terminate to provision or disable IdP and app access and update downstream records as the changes post.

  4. Replicate Compensation Summary and pay data into a warehouse for headcount, labor-cost, and compensation reporting without manual BI exports.

  5. Sync time data by posting raw clock entries from a third-party scheduling tool into Dayforce, or pulling Employee Punches and Schedules into a workforce-analytics database.

  6. Two-way sync of Employee and Work Assignment (position, department, location, org unit) into Postgres so provisioning, internal apps, and analytics read current worker and org data in SQL while HR keeps editing in Dayforce.

All Ceridian Dayforce integrations

Pick the system you need to keep in sync with Ceridian Dayforce. Each page covers the sync setup, field mapping, and common workflows for that pair.

Database · 50

How it works

Set up Ceridian Dayforce in minutes, without APIs.

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate Ceridian Dayforce with its native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Ceridian Dayforce connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Ceridian Dayforce objects to sync — Stacksync auto-detects the schema, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Ceridian Dayforce
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Ceridian Dayforce database
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp

FAQ

Ceridian Dayforce connector FAQ

What can I sync with the Ceridian Dayforce connector?

Ceridian Dayforce's core objects — Employee (HR / Person Details), Employment Status, Work Assignments, Compensation Summary & Pay Adjustments and custom fields — can sync with any of 302 other systems. Every integration is real-time and bidirectional, with field-level mapping and conflict resolution.

How does Stacksync connect to Ceridian Dayforce?

Via REST API (Dayforce RESTful Web Services, v1/v2), JSON payloads, authenticated with HTTP Basic authentication with a dedicated Web Services user plus the client namespace (Company ID), or an OAuth 2.0 access token from the Dayforce identity endpoint (POST dfid.dayforcehcm.com/connect/token, client_id Dayforce.HCMAnywhere.Client). Token-based auth is recommended, and the Web Services role with the Read Data subfeature must be enabled on the account.. Changes are detected as follows — no CDC stream. Broad change detection uses delta polling on GET Employees with filterUpdatedStartDate/filterUpdatedEndDate and filterUpdatedEntities to pull only records changed in a window. Dayforce also has native Event Notifications (the Notification Publisher) for lifecycle events — hire, rehire, terminate, and workflow validation — delivered by push to a receiver service or by querying unacknowledged notifications; the publisher runs roughly hourly and each notification must be acknowledged.. Stacksync manages rate limits, retries, and schema changes automatically.

Is the Ceridian Dayforce connector two-way?

Yes. Changes made in Ceridian Dayforce propagate to the connected system and vice versa, in milliseconds. One-way flows are also supported when a direction should stay read-only.

How long does a Ceridian Dayforce integration take to set up?

Most Ceridian Dayforce integrations go live in minutes: authenticate Ceridian Dayforce and the other system, pick objects and fields, and enable the sync. No code and no infrastructure to manage.

Is Ceridian Dayforce data secure in transit?

Stacksync is SOC 2 Type II, ISO 27001, GDPR and HIPAA compliant. Ceridian Dayforce data is encrypted in transit, and a zero-persistent-storage architecture means records are not retained after a sync operation.

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.