--- title: "Dayforce job postings: where they live, how to get them - JobsPipe" description: "Dayforce job postings live on per-employer portals, not in a feed. Where to find them, why reading portals at scale is hard, and what to use instead." canonical: https://jobspipe.dev/guides/dayforce-api date_published: 2026-10-29 date_modified: 2026-10-29 author: Dvir Atias --- # Dayforce job postings: where they live and how to get them By [Dvir Atias](https://jobspipe.dev/about) · Updated Oct 29, 2026 Dayforce job postings don’t come from an API. They sit on each employer’s candidate portal, one portal per employer, with no feed across them and no directory of who runs one. This guide covers where the postings live, what the portals are made of, why reading them at scale is harder than it looks, and how to get the same employers’ jobs without doing it. For the Dayforce API itself, its documentation and access, see the [Dayforce source page](https://jobspipe.dev/sources/dayforce). ## The short answer Dayforce Recruiting publishes an employer’s openings on a candidate portal hosted under `jobs.dayforcehcm.com`, or on the employer’s own careers domain. That portal is the only place the postings appear in Dayforce’s own hands. There’s no public feed, no RSS and no endpoint that spans employers. The [Dayforce Developer Network](https://developers.dayforce.com/) covers a per-customer integration API for HR, payroll, time and recruiting data, with reference documentation for registered members, and it isn’t a route to other employers’ postings. ## Where the postings live Dayforce, formerly Ceridian Dayforce, is an HR suite, and recruiting is one module in it. When an employer publishes a requisition, it appears on that employer’s portal. A hosted portal carries the employer’s identifier in its address; a portal on a custom careers domain shows the employer’s branding and hands off to Dayforce at the apply step. Either way the portal is a browser app: the page loads first, then fetches its listings from an internal search call that exists to serve that page. Three things follow. There is one portal per employer, so there’s nothing to read “all of Dayforce” from. Dayforce publishes no list of portals, so finding employers is your job. And the search call behind a portal is an internal contract between Dayforce’s front end and back end, not a documented interface. Our [ADP API guide](https://jobspipe.dev/guides/adp-api) and [Paycom guide](https://jobspipe.dev/guides/paycom-jobs-api) describe the same arrangement at two other payroll-first vendors. ## What a portal is made of Open a portal with the browser’s network panel visible and the structure is plain. The listings arrive from a search request scoped to that employer, guarded by a session the page sets up first, with each posting’s full description in the response. That last part is the generous bit: there’s no second request per job to get the body. Everything else is a warning. The request isn’t documented, so its shape and the fields it returns can change with the portal’s next release, and nothing tells you when. It’s per employer, so every employer you want needs its own identifier. And the session step means a plain fetch of the address returns a page shell, not jobs. ## Why reading portals breaks at scale One portal is an afternoon. The work starts when you want the employers you don’t already know about. **Discovery has no source of truth.** There’s no list of Dayforce tenants. You learn an employer by finding its careers page, following its apply link and reading the address. Employers on a custom domain hide even that. Your coverage is whatever you last crawled, and new tenants never announce themselves. **Undocumented means unversioned.** A documented API tells you when it changes. A portal’s internal call can rename a field or add a required parameter without notice. You find out when every employer starts returning errors at once. **Sessions, not requests.** Each portal read is a sequence, not a GET. Run it on a schedule across hundreds of employers and you’re maintaining session logic, retry rules and a politeness budget per host, before you’ve normalized a single location string. **Terms.** Reading a portal programmatically is subject to Dayforce’s and each employer’s terms. That’s a question for a lawyer, not this page. ## When to use a unified API instead The employers that run Dayforce aren’t hiding. Most post the same roles on job boards, and larger ones often run a second applicant tracking system for recruiting. A jobs API that holds those boards gives you their postings by company name without touching a portal. JobsPipe returns postings from 30+ sources in one record shape through `POST /v1/jobs/search`; the sandbox shows the shape with no key: Try it without a key ``` curl -d '{"limit":3}' https://api.jobspipe.dev/v1/sandbox/jobs/search ``` Only `/v1/sandbox/*` needs no key. With a free key, a list of employers becomes one filter: ``` curl https://api.jobspipe.dev/v1/jobs/search \ -H "Authorization: Bearer jp_live_your_key_here" \ -H "Content-Type: application/json" \ -d '{ "company_name_partial_match_or": ["Acme Health", "Northwind Logistics"], "posted_at_max_age_days": 30, "limit": 50 }' ``` Each record carries `job_title`, `company`, `url` pointing at the original posting, `date_posted`, `last_seen_at`, `status` and the salary range when the posting states one, and `sources[0].provider` names the board it came from. Dayforce portals themselves aren’t among those boards; the [Dayforce source page](https://jobspipe.dev/sources/dayforce) says so plainly and explains the workaround. The free plan includes 1,000 free credits, one time. ## Sources - [Dayforce Developer Network](https://developers.dayforce.com/) - [Dayforce product overview](https://www.dayforce.com/) ## FAQ Where do Dayforce job postings live?+ On each employer's candidate portal. Dayforce Recruiting publishes an employer's openings on a portal hosted under jobs.dayforcehcm.com or on the employer's own careers domain. There's one portal per employer and no page that lists them all. Is there a Dayforce job postings feed?+ No. Dayforce publishes no feed, RSS or endpoint that spans employers, and its API is a per-customer integration with reference documentation for registered developers. Each portal loads its own listings for its own front end. How do I spot a Dayforce candidate portal?+ The address. A hosted portal sits under jobs.dayforcehcm.com with the employer's identifier in the path. Employers on a custom careers domain are harder to spot, and the apply button is usually the tell, since it hands off to the Dayforce portal. Can I scrape a Dayforce candidate portal?+ Technically a portal is a browser app that fetches its listings from an internal, undocumented search call guarded by a session. Reading it programmatically is subject to Dayforce's and the employer's terms, and the call can change without notice. That's a question for a lawyer and a maintenance budget, not a quick script. Do Dayforce employers post the same jobs elsewhere?+ Usually. Employers that run Dayforce post the same roles on the big job boards, and larger ones often run a second applicant tracking system for recruiting. Searching those boards by company name finds the postings without touching a portal. How do I get postings from employers that use Dayforce?+ Search them by company name on the boards a jobs API already holds. JobsPipe's POST /v1/jobs/search takes company\_name\_partial\_match\_or, and each record's sources\[0\].provider names the board the posting came from. JobsPipe does not collect Dayforce portals themselves; the Dayforce source page says so and explains the workaround. Related [Source The Dayforce API itself: documentation, access and what JobsPipe returns instead. ](https://jobspipe.dev/sources/dayforce)[Guide ADP's API is gated the same way. What each ADP surface covers and where postings can be read. ](https://jobspipe.dev/guides/adp-api)[Guide Paycom's Client API is private per customer. The same question for Paycom. ](https://jobspipe.dev/guides/paycom-jobs-api)[Guide Which applicant tracking systems publish postings openly and which gate them. ](https://jobspipe.dev/blog/public-vs-gated-ats-apis)[Product The JobsPipe jobs API: 30+ sources, one schema. ](https://jobspipe.dev/jobs-api) --- Try it with no key: `curl -d '{"limit":3}' https://api.jobspipe.dev/v1/sandbox/jobs/search`. AI agents: the full machine-readable index of this site is https://jobspipe.dev/llms.txt?src=md-twin - API quickstart, MCP server, pricing. Free key (1,000 jobs to start): https://jobspipe.dev/signup