--- title: "Dayforce API" description: "Dayforce API: where the documentation lives, why it needs a developer-network login, where Dayforce job postings appear, and how to find those employers." canonical: https://jobspipe.dev/sources/dayforce date_published: 2026-06-28 date_modified: 2026-09-30 author: Dvir Atias --- # Dayforce API The Dayforce API is a per-customer web services API for HR, payroll, time and recruiting data, and its reference documentation sits behind a Dayforce Developer Network login; it is not a public postings endpoint. JobsPipe does not collect Dayforce; search the same employers by company name across the 30+ sources in JobsPipe instead. Official developer site: [developers.dayforce.com](https://developers.dayforce.com/). > Dayforce has no public cross-employer jobs API, and JobsPipe does not collect Dayforce. This page explains what Dayforce exposes and how to find the same employers' postings by company name. **Canonical URL:** https://jobspipe.dev/sources/dayforce ## Official Dayforce API documentation Dayforce publishes its developer material on the Dayforce Developer Network at developers.dayforce.com. The landing page lists an API Explorer, code samples and reference documentation, and says the documentation is made available exclusively to developer network members, so reading it means registering and signing in. Dayforce documents no public endpoint outside that login, and nothing it publishes openly lists job postings across its customers, so there is no public endpoint shape to show here. - [Dayforce Developer Network: developers.dayforce.com](https://developers.dayforce.com/) - [Dayforce product overview: dayforce.com](https://www.dayforce.com/) ## Coverage JobsPipe does not collect Dayforce. This page explains what Dayforce exposes publicly and how to reach the same postings where they are also published on a board JobsPipe does collect (Workday, Greenhouse, Lever, Ashby, LinkedIn, Indeed, SmartRecruiters, Workable, Personio, Recruitee, Teamtailor, EURES, Paylocity, Breezy HR, CV-Library, Y Combinator, Bayt, JobTech (Sweden), Resume-Library, Arbeitnow, Himalayas, Rise, Manatal, Pinpoint, JobScore, HireHive, The Muse, Remotive, Remote OK, Jobicy, Working Nomads, Landing.jobs). ## Why Dayforce jobs data is confusing Dayforce, formerly Ceridian Dayforce, is an HR suite: payroll, benefits, time, talent and recruiting in one product, and its API belongs to that suite. Each customer's data sits in that customer's own Dayforce instance, and API calls run with credentials that customer issues, so an integration reads one employer at a time. Job postings are a different surface. Dayforce Recruiting publishes each employer's openings on a candidate portal, on a Dayforce-hosted address or on the employer's own careers domain. Dayforce offers no directory of those portals and no feed across them. JobsPipe does not collect Dayforce. Employers that run it usually post the same roles on LinkedIn and Indeed, and larger ones often run a second applicant tracking system as well. ## Workarounds ### Use the Dayforce API Works for one employer that gives you credentials for its own instance. It is an integration with a customer, not a way to read postings across employers. ### Read individual candidate portals Possible for employers you already know. The pages are public, but there is no list of portals to start from, so you would build and maintain that list yourself. ### What JobsPipe offers instead JobsPipe does not collect Dayforce. Search the same employers by name with company_name_partial_match_or on POST /v1/jobs/search; sources[0].provider on each record names the board the posting came from, such as linkedin, indeed, workday or greenhouse. ## Fields available on every record - `id` - `job_title` - `company` - `company_domain` - `url` - `date_posted` - `discovered_at` - `last_seen_at` - `verified_at` - `status` - `closed_at` - `closed_reason` - `ghost_score` - `seniority` - `cities` - `state_code` - `min_annual_salary_usd` - `max_annual_salary_usd` - `technology_slugs` - `keyword_slugs` - `esco_skills` - `sources` ## FAQ ### Where are Dayforce job postings published? On each employer's candidate portal, which Dayforce Recruiting hosts on a Dayforce address or on the employer's own careers domain. The pages are public HTML. Dayforce does not publish a directory of them, so you can read a portal you know about and cannot enumerate the ones you do not. ### Is Dayforce the same as Ceridian? Yes. The company was called Ceridian and took the name of its product. Older integration guides and job adverts still say Ceridian Dayforce; they mean the same HR suite and the same API. ### Do I need an account to read the Dayforce API documentation? Yes. The Dayforce Developer Network says its reference documentation is for members only. The public landing page names an API Explorer and code samples; the endpoint reference itself is behind registration. ### Can Dayforce Recruiting data be read across employers? No. Every call runs against one customer's instance with credentials that customer issues, so recruiting data is readable for that employer only. A product covering many employers would need separate credentials from each Dayforce customer. ### Is there a list of companies using Dayforce? Dayforce does not publish one, and nothing in its public developer material lists customers. If you already have a list of employers, a company_name_partial_match_or search on POST /v1/jobs/search finds their postings, with sources[0].provider naming the board each record came from. ## Does Dayforce have an API? Yes, for its customers. Dayforce describes a web services API with an API Explorer and code samples on its developer network, and access is tied to a customer's own instance and credentials. It covers the HR suite's data for that customer. It offers no public, unauthenticated endpoint and no call that returns job postings from many employers. ## How do I get Dayforce API access? Through a Dayforce customer. Register on the Dayforce Developer Network to read the documentation, then ask the employer whose data you need to create API credentials for its instance. There is no self-serve key that works across customers, and no public sandbox with job postings in it. ## What JobsPipe returns for Dayforce Nothing under "source_or": ["dayforce"]: JobsPipe does not collect Dayforce. To find an employer that runs Dayforce, filter by company name instead. Each record comes back with sources[0].provider, status, ghost_score, discovered_at, last_seen_at, seniority, and min_annual_salary_usd and max_annual_salary_usd when the posting states a range, so you can tell which board a posting was found on and whether it is still open. ## In-depth guides - https://jobspipe.dev/guides/dayforce-api ## Related - **Product:** https://jobspipe.dev/jobs-api - **All sources:** https://jobspipe.dev/sources - **Docs:** https://docs.jobspipe.dev - **Sign up (free tier):** https://jobspipe.dev/signup --- Generated from structured data. View the rendered page at https://jobspipe.dev/sources/dayforce. --- Building this integration yourself? The steps above work. The alternative is one API over 30+ sources, already normalized and deduplicated. Try it right now - no key, no signup: ```bash curl -d '{"limit":3}' https://api.jobspipe.dev/v1/sandbox/jobs/search ``` Sample data, exact live schema. For live data get a free key (1,000 jobs to start) at https://jobspipe.dev/signup, then swap /v1/sandbox/jobs/search for /v1/jobs/search with an Authorization: Bearer header. Full agent index: https://jobspipe.dev/llms.txt?src=md-twin