Careers Website ATS Integration: How Jobs, Feeds and Applications Flow
Careers website ATS integration explained: how jobs, feeds and applications flow between your applicant tracking system and your careers website.
By the Happydance team. Updated November 2026.
How a careers website connects to an ATS
Your applicant tracking system holds your jobs and candidates. Your careers website holds your brand and your content. The connection between them decides whether candidates find fresh jobs and complete clean applications.
Three flows matter. Jobs flow from the ATS to the careers website. Candidates flow from the careers website to the application. Data flows back: applications, status and source.
- 1. Jobs outThe ATS publishes approved jobs to the careers website.
- 2. DiscoveryCandidates search and filter on the careers website.
- 3. ApplyThe candidate moves to the application, with context.
- 4. Data backApplications, source and consent arrive in the ATS.
Job feed methods
| Method | How it works | Good for | Watch for |
|---|---|---|---|
| Feed (XML or JSON) | The ATS exposes jobs and the careers website reads them on a schedule | Simple, widely supported | Delay between updates |
| API | The careers website asks the ATS for jobs directly | Flexible, fresh | Rate limits and credentials |
| Push or webhook | The ATS tells the careers website when a job changes | Fast updates | Failure handling |
| Manual or file upload | A person uploads jobs | Small or one-off needs | Stale data and effort |
Apply flow options
Redirect
The candidate leaves for the ATS to apply. Simple, but the experience changes.
Embed
The ATS form appears inside the careers website. More consistent, depends on the ATS.
Hosted on the careers website
The careers website collects the application and passes it to the ATS. Most control, most responsibility.
Whichever you choose, test it on a phone, keep the form short and make sure the candidate knows what happens next. See our design best practices.
Tracking and attribution
You cannot improve what you cannot attribute. Pass source, medium and campaign through to the ATS, keep consent records, and agree one definition of an application across tools. Read about employer branding metrics.
Data ownership and security
- Agree which system is the record for jobs and candidates.
- Store as little candidate data on the careers website as you can.
- Capture and pass consent properly.
- Use secure, rotated credentials and least-privilege access.
- Agree data processing terms, hosting location and retention.
- Ask for evidence of security testing.
Supported systems
Supported systems: to be confirmed
The list of supported applicant tracking systems will be published here once confirmed. Ask in a demo about your own system.
If you use Oracle Recruiting, see a careers website for Oracle Recruiting. To compare ATS career pages with a careers website, read careers website vs ATS career page.
Technical checklist
Settle these twelve questions with your ATS owner and provider before you start. Tick each when you have a written answer.
ATS integration technical checklist
Tick each question once you have a written answer. Nothing leaves your browser.
| # | Question |
|---|---|
| 1 | Which system holds jobs, and which holds candidates? |
| 2 | How do jobs reach the careers website: feed, API or push? |
| 3 | How often do jobs update, and what happens on failure? |
| 4 | Which job fields are mapped, including custom fields? |
| 5 | How do closed jobs disappear? |
| 6 | Where does the candidate apply: hosted, embedded or redirected? |
| 7 | How are source and campaign data passed to the ATS? |
| 8 | How is consent captured and passed? |
| 9 | What candidate data does the careers website store? |
| 10 | How are credentials and access managed? |
| 11 | How are errors alerted and who responds? |
| 12 | What is the test and go-live plan, including rollback? |
This is the printable version. Switch on JavaScript to use the live calculator in your browser.
Bring the answers into your RFP, and read our guide to replacing your careers website provider if you are switching. See the platform overview and careers website CMS.
An integration discovery worksheet
Most integration problems are found late because nobody asked early. Complete this worksheet with your ATS owner and IT before you design anything.
| Topic | What to find out | Who knows |
|---|---|---|
| Job data | Which fields exist, how often they change and how jobs close | ATS administrator |
| Locations | How locations are stored, and whether they match names candidates use | ATS administrator and HR operations |
| Apply route | Hosted apply page, embedded form or a redirect, and who maintains it | ATS owner and talent acquisition |
| Tracking | Which source parameters the ATS keeps | Analytics and ATS owner |
| Consent | How consent is captured and passed on | Legal and privacy |
| Security | Access rules, hosting location and review process | IT and security |
| Support | Who is called when jobs stop updating | Both suppliers and your IT team |
Failure modes and what to do about them
| What goes wrong | Likely cause | First check |
|---|---|---|
| New jobs do not appear | Feed delay or filter | Feed time stamp and filter rules |
| Closed jobs still show | Closure not passed or cached | Job status in the ATS and the careers website |
| Apply button leads to an error | Link format or hosted page change | The apply URL for one job |
| Locations look wrong | Free-text location data | Location field in the ATS |
| Source data is missing | Parameters stripped on redirect | The full URL path from click to application |
Agree who fixes what before launch, and document it in one page that your support teams can find.
Who owns what: a simple responsibility table
| Area | Careers website supplier | ATS owner | Your team |
|---|---|---|---|
| Job display and search | Owns | Provides the data | Reviews |
| Apply journey | Shares | Shares | Signs off |
| Source tracking | Passes parameters | Stores them | Reports |
| Security and access | Follows policy | Follows policy | Sets policy |
| Incident response | First contact for the site | First contact for the ATS | Coordinates |
Testing the integration before launch
| Test | How | Pass |
|---|---|---|
| New job | Create a job in the ATS and wait for the next update | It appears on the careers website within the agreed time |
| Changed job | Edit a title or location | The change appears everywhere |
| Closed job | Close a job in the ATS | It disappears and no longer appears in search |
| Apply | Complete an application on a phone | The application appears in the ATS with its source |
| Failure | Simulate a feed delay | The team sees an alert and knows who to call |
How does a careers website connect to an ATS?
Jobs flow from the ATS to the careers website by feed, API or push. Candidates apply through a redirect, an embed or a hosted form, and application data returns to the ATS.
What is a job feed?
A structured list of jobs, usually XML or JSON, that the ATS exposes so another system can read them.
How often should jobs update?
As often as your hiring needs. Ask what happens on failure and how closed jobs are removed.
Where does the candidate apply?
It depends on the apply flow: a redirect to the ATS, an embedded form or a form hosted on the careers website.
Who owns candidate data?
Agree this in writing. Usually the ATS is the record, and the careers website stores as little as possible.
How do I track which source an application came from?
Pass source, medium and campaign into the ATS and agree one definition of an application.
Which ATS systems are supported?
Ask in a demo about your own system. We list supported systems once confirmed.
What should I check before go-live?
Use the technical checklist on this page, then run a test and agree a rollback plan.
What should I check before integrating a careers website with an ATS?
Job fields, locations, the apply route, source tracking, consent, security and who supports each part.
Why do jobs sometimes show as open after they close?
Usually because the closure has not been passed on or a cache has not cleared. Check job status on both sides.
Who is responsible when jobs stop updating?
Agree this in advance. Usually the supplier checks the site side, the ATS owner checks the data side and your team coordinates.
How do I test an ATS integration?
Create, change and close a test job, complete an application on a phone and simulate a feed failure to check alerts and ownership.