v1.0.0 to v1.0.0

22 added, 0 removed. Audit A to A.

---

name: ceridian-dayforce

description: |

Ceridian Dayforce integration via Apideck's HRIS unified API — same methods work across every connector in HRIS, switch by changing `serviceId`. Use when the user wants to read or sync employees, departments, payrolls, and time-off records in Ceridian Dayforce. Routes through Apideck with serviceId "ceridian-dayforce".

license: Apache-2.0

alwaysApply: false

metadata:

author: apideck

version: "1.0.0"

serviceId: ceridian-dayforce

unifiedApis: ["hris"]

authType: oauth2

tier: "2"

verified: true

status: beta

+ difficulty: highly_complex

+ partnershipRequired: false

+ sandboxAvailable: true

---

# Ceridian Dayforce (via Apideck)

Access Ceridian Dayforce through Apideck's **HRIS** unified API — one of 58 HRIS connectors that share the same method surface. Code you write here ports to BambooHR, Workday, Deel and 54 other HRIS connectors by changing a single `serviceId` string. Apideck handles auth, pagination, rate limiting, and retries so you don't write per-tenant Ceridian Dayforce plumbing.

> **Beta connector.** Ceridian Dayforce is currently in beta on Apideck. Expect partial resource coverage and occasional mapping gaps. Always verify coverage (see below) and fall back to the Proxy API for unsupported operations.

## Quick facts

- **Apideck serviceId:** `ceridian-dayforce`

- **Unified API:** HRIS

- **Auth type:** oauth2

- **Status:** beta

- **Apideck setup guide:** [Connection guide](https://developers.apideck.com/connectors/ceridian-dayforce/docs/consumer+connection)

- **Gotchas:** [page](https://developers.apideck.com/apis/hris/ceridian-dayforce/gotchas)

- **Ceridian Dayforce docs:** https://developers.ceridian.com

- **Homepage:** https://www.ceridian.com/products/dayforce

+ ## At a glance

+ - **Implementation difficulty:** highly complex — Custom Auth + Multi-Step Per-Consumer Web Services Setup

+ - **Vendor partnership required:** no

+ - **Apideck-managed credentials:** not available — Each consumer supplies their own Web Services user credentials.

+ - **Account type required:** A Dayforce customer account with Web Services enabled.

+ - **Consumer access level:** A Client Admin, who creates a custom role and a dedicated non-employee integration user for the connection.

+ - **Sandbox:** available ([signup](https://developers.dayforce.com/Special-Pages/Registration.aspx)) — Register on the Dayforce Developer Network to test against your own company's environment, or a shared sample environment if you have no namespace.

+ - **Costs:** No charge for web services, provided the integration follows Dayforce's acceptable-use conditions (system-to-system, built without engaging Dayforce resources).

+ - **Rate limits:** Per Dayforce client and per operation; for example 10 lookups a second or 100 a minute, lower for reports.

+ - **Authentication:** Username, password and Company ID of a Dayforce Web Services user; no OAuth redirect.

+ - **Webhooks:** Virtual webhooks - employee created events

+ **Important to know:**

+ - The connection signs in as the integration user, so a password change or expiry on that Dayforce user breaks it until the consumer re-enters the password in Vault; Dayforce advises a non-expiring password policy for these users.

+ > Facts synced from Apideck's connector metadata API — `GET /connector/connectors/ceridian-dayforce` (`overview` field) is the live, authoritative version.

## When to use this skill

Activate this skill when the user explicitly wants to work with **Ceridian Dayforce** — for example, "sync employees in Ceridian Dayforce" or "list time-off requests in Ceridian Dayforce". This skill teaches the agent:

1. Which Apideck unified API covers Ceridian Dayforce (HRIS)

2. The correct `serviceId` to pass on every call (`ceridian-dayforce`)

3. Ceridian Dayforce-specific auth and coverage caveats

For the full method surface (parameters, pagination, filtering), use your language SDK skill:

- [`apideck-node`](../../skills/apideck-node/), [`apideck-python`](../../skills/apideck-python/), [`apideck-dotnet`](../../skills/apideck-dotnet/), [`apideck-java`](../../skills/apideck-java/), [`apideck-go`](../../skills/apideck-go/), [`apideck-php`](../../skills/apideck-php/), or [`apideck-rest`](../../skills/apideck-rest/)

For the raw OpenAPI spec:

- **HRIS:** [https://specs.apideck.com/hris.yml](https://specs.apideck.com/hris.yml) · [API Explorer](https://developers.apideck.com/api-explorer?id=hris)

## Minimal example (TypeScript)

```typescript

import { Apideck } from "@apideck/unify";

const apideck = new Apideck({

apiKey: process.env.APIDECK_API_KEY,

appId: process.env.APIDECK_APP_ID,

consumerId: "your-consumer-id",

});

// List employees in Ceridian Dayforce

const { data } = await apideck.hris.employees.list({

serviceId: "ceridian-dayforce",

});

```

## Portable across 58 HRIS connectors

The Apideck **HRIS** unified API exposes the same methods for every connector in its catalog. Switching from Ceridian Dayforce to another HRIS connector is a one-string change — no rewrite, no new SDK.

```typescript

// Today — Ceridian Dayforce

await apideck.hris.employees.list({ serviceId: "ceridian-dayforce" });

// Tomorrow — same code, different connector

await apideck.hris.employees.list({ serviceId: "bamboohr" });

await apideck.hris.employees.list({ serviceId: "workday" });

```

This is the compounding advantage of using Apideck over integrating Ceridian Dayforce directly: code against the unified HRIS API once, gain access to every connector in it. New connectors Apideck adds become available to your app without code changes.

## Authentication

- **Type:** OAuth 2.0

- **Managed by:** Apideck Vault — Apideck handles the full OAuth dance (authorization code flow, token exchange, refresh). Never ask the user for API keys or tokens directly.

- **User setup:** Users authorize via the Vault modal. Connection state progresses `available → added → authorized → callable`.

- **Token refresh:** automatic. Expired tokens are refreshed transparently on the next API call.

**Setup guide:** Apideck publishes a step-by-step guide for registering an OAuth app / configuring credentials for Ceridian Dayforce — see [https://developers.apideck.com/connectors/ceridian-dayforce/docs/consumer+connection](https://developers.apideck.com/connectors/ceridian-dayforce/docs/consumer+connection). Use that as the authoritative source when walking users through connection setup.

See [`apideck-best-practices`](../../skills/apideck-best-practices/) for Vault setup, connection lifecycle, and handling re-auth flows.

## Verifying coverage

Not every HRIS operation is supported by every connector. Always verify before assuming a method works:

```bash

curl 'https://unify.apideck.com/connector/connectors/ceridian-dayforce' \

-H "Authorization: Bearer ${APIDECK_API_KEY}" \

-H "x-apideck-app-id: ${APIDECK_APP_ID}"

```

See [`apideck-connector-coverage`](../../skills/apideck-connector-coverage/) for patterns around `UnsupportedOperationError` and connector-specific fallbacks.

## Escape hatch: Proxy API

When an endpoint isn't covered by the HRIS unified API, use Apideck's Proxy to call Ceridian Dayforce directly — Apideck injects auth headers and handles token refresh. Set `x-apideck-downstream-url` to the target endpoint on Ceridian Dayforce's own API:

```bash

curl 'https://unify.apideck.com/proxy' \

-H "Authorization: Bearer ${APIDECK_API_KEY}" \

-H "x-apideck-app-id: ${APIDECK_APP_ID}" \

-H "x-apideck-consumer-id: ${CONSUMER_ID}" \

-H "x-apideck-service-id: ceridian-dayforce" \

-H "x-apideck-downstream-url: <target endpoint on Ceridian Dayforce>" \

-H "x-apideck-downstream-method: GET"

```

See [Ceridian Dayforce's API docs](https://developers.ceridian.com) for available endpoints.

## Sibling connectors

Other **HRIS** connectors that share this unified API surface (same method signatures, just change `serviceId`):

[`bamboohr`](../bamboohr/), [`workday`](../workday/), [`deel`](../deel/) *(beta)*, [`hibob`](../hibob/), [`personio`](../personio/), [`adp-ihcm`](../adp-ihcm/) *(beta)*, [`adp-workforce-now`](../adp-workforce-now/) *(beta)*, [`paychex`](../paychex/) *(beta)*, and 49 more.

## See also

- [Apideck connection guide for Ceridian Dayforce](https://developers.apideck.com/connectors/ceridian-dayforce/docs/consumer+connection)

- [HRIS OpenAPI spec](https://specs.apideck.com/hris.yml) · [API Explorer](https://developers.apideck.com/api-explorer?id=hris)

- [`apideck-connector-coverage`](../../skills/apideck-connector-coverage/) — programmatic coverage checks

- [`apideck-best-practices`](../../skills/apideck-best-practices/) — architecture, Vault, pagination, error handling

- [`apideck-node`](../../skills/apideck-node/) — TypeScript / Node SDK patterns

- [Ceridian Dayforce official docs](https://developers.ceridian.com)