--- title: "Dayforce API" description: "Dayforce API: the per-tenant REST API for payroll, time and recruiting, the public candidate portals where postings live, and one call for them." canonical: https://jobspipe.dev/sources/dayforce --- # Dayforce API The Dayforce API is a per-tenant REST API for payroll, benefits, time and recruiting, authenticated with each customer's credentials against their own instance, not a public postings endpoint; Dayforce Recruiting publishes to public candidate portals. JobsPipe does not collect Dayforce; the same employers' openings reach one search endpoint through the boards JobsPipe does collect, in one record shape across 30+ sources. > Dayforce has no public cross-employer jobs API, and JobsPipe does not collect Dayforce. This page explains what Dayforce exposes and how to reach the same employers through the boards JobsPipe does collect. **Canonical URL:** https://jobspipe.dev/sources/dayforce ## 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 (LinkedIn, Indeed, Y Combinator, Naukri, Workday, Greenhouse, Workable, SmartRecruiters, Ashby, Lever, Paylocity). ## Why Dayforce jobs data is confusing The Dayforce API (formerly Ceridian Dayforce) is a per-tenant REST API for payroll, benefits, time and recruiting, authenticated with each customer's credentials against their own Dayforce instance. It is not a public endpoint that lists postings across companies. Dayforce Recruiting publishes to public candidate portals under the customer's Dayforce domain, or to custom careers domains. There is no list endpoint for tenants and no cross-tenant feed. JobsPipe does not collect Dayforce. Employers that run Dayforce usually also post the same roles to LinkedIn and Indeed, and larger ones run Workday, Greenhouse, Workable, SmartRecruiters, Ashby, Lever or Paylocity alongside it. JobsPipe collects all of those boards, so filter POST /v1/jobs/search by company_name_partial_match_or to reach them. ## Workarounds ### Use the Dayforce REST API Reads one customer's data with their credentials. Not a path across employers. ### Scrape individual Dayforce career sites Possible per employer you already know. Public HTML, no directory. ### What JobsPipe offers instead JobsPipe does not collect Dayforce. Search the same employers by name across the boards JobsPipe does collect (LinkedIn, Indeed, Workday, Greenhouse, Workable, SmartRecruiters, Ashby, Lever and Paylocity); sources[0].provider on each record names the board it came from. ## 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? Dayforce Recruiting publishes to public candidate portals under the customer's Dayforce domain, or to the customer's custom careers domain. The pages are public HTML, so you can read them per employer you already know. There is no directory of portals and no cross-tenant feed, so discovery is on you. ### Is Dayforce the same as Ceridian? Yes. Its API is a per-tenant REST API for payroll, benefits, time and recruiting, authenticated with each customer's credentials against their own Dayforce instance, and it does not list postings across companies. ### Can Dayforce Recruiting data be read across employers? No. Every Dayforce API call runs against one customer's own instance with credentials that customer issues, so recruiting data is readable only for that tenant. There is no list endpoint for tenants and no cross-tenant feed, which means a multi-employer product would need separate credentials from each Dayforce customer. ### Is there a list of companies using Dayforce? No. Dayforce has no list endpoint for tenants. Employers that run Dayforce usually also post the same roles to LinkedIn and Indeed, and larger ones run Workday or Greenhouse alongside it, all boards JobsPipe collects, so a company_name_partial_match_or search on POST /v1/jobs/search reaches a known employer, with sources[0].provider naming each record's board. ## Does Dayforce have an API? The Dayforce API (formerly Ceridian Dayforce) is a per-tenant REST API for payroll, benefits, time and recruiting, authenticated with each customer's credentials against their own Dayforce instance. It is not a public endpoint that lists postings across companies. Dayforce Recruiting publishes to public candidate portals under the customer's Dayforce domain, or to custom careers domains. There is no list endpoint for tenants and no cross-tenant feed. ## What JobsPipe returns for Dayforce Nothing under "source_or": ["dayforce"]: JobsPipe does not collect Dayforce. Employers that run Dayforce usually also post the same roles to LinkedIn and Indeed, and larger ones run Workday, Greenhouse, Workable, SmartRecruiters, Ashby, Lever or Paylocity alongside it. JobsPipe collects all of those boards, so filter POST /v1/jobs/search by company_name_partial_match_or to reach them. 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. ## 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 this source and 30+ others, already normalized and deduplicated. Try it right now - no key, no signup: ```bash curl -X POST https://api.jobspipe.dev/v1/sandbox/jobs/search \ -H "Content-Type: application/json" \ -d '{"job_title_or":["software engineer"],"limit":5}' ``` 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