ATS IntegrationThe 9 connections your hiring stack actually needs
Search "ATS integration" and you get pages written for software engineers building connectors. Useful if you are shipping an API. Useless if you are a head of talent trying to work out whether the tool in front of you will post to Indeed without a copy-paste ritual every Monday. This is the version for the person signing the contract.
Every integration sits on one of three edges of your ATS
Candidates come in
- Job boards
- Career site
- Referrals
- Sourcing tools
Work happens here
- Screening
- Scheduling
- Interviews
- Scorecards
Decisions go out
- Background checks
- Offer + e-sign
- HRIS
- Payroll
If a vendor can only talk about the middle column, the demo is hiding something.
Here is the pattern I keep seeing. A team buys an ATS on the strength of its screening features, then spends the next six months rebuilding by hand every connection the old system had. Jobs get posted twice. A candidate gets rejected in the ATS and keeps getting nurture emails from a sourcing tool nobody remembered to disconnect. The new hire's record gets typed into payroll a third time, with a typo.
The scale of this is not small. Sapient Insights Group's HR Systems Survey puts the average mid-market organization at roughly 15 HR system integrations spread across 11 to 13 platforms. HR.com's 2025 research on HR technology and integrations found most of those tools sitting on disconnected platforms, with data silos as the top complaint. Your ATS sits in the middle of that mess. It is the system where the most cross-tool handoffs happen.
So the integration question is not a technical footnote at the end of a buying process. It is most of the buying process. This guide covers what the word actually means, the nine connections worth caring about, how the Indeed and LinkedIn integrations really work under the hood, and the six questions that expose a weak connector during a demo. If you are earlier in the process, start with our ATS implementation guide and the ATS migration checklist.
Definitions
What an ATS integration actually is
An ATS integration is a live connection between your applicant tracking system and another tool, where data moves between them on its own. A job you publish in the ATS appears on Indeed. A candidate who applies on Indeed lands in your pipeline with their resume attached. You book an interview and it shows up on four calendars. You mark someone hired and their record appears in your HRIS with a start date already filled in.
That is the honest definition. The dishonest one is broader, which is why the word has lost most of its meaning on vendor websites. A CSV export is not an integration. A Zapier recipe that a vendor did not build and does not support is, at best, an integration you now own. A logo grid on a pricing page tells you nothing about whether the connection is one-way, two-way, or aspirational.
Before you evaluate any specific tool, get clear on which of these four you are being sold.
Four things get called an integration. Only two of them are one.
CSV export
Someone downloads a file and uploads it somewhere else. Marketed as an integration constantly.
One-way push
Your ATS sends data out. Nothing comes back. Fine for posting a job, useless for tracking a result.
Two-way sync
Data moves both directions on a schedule. Good enough for most hiring workflows.
Event-driven
A webhook fires the moment something changes. No polling delay, no stale record, no duplicate.
Level 2 is the realistic bar for most hiring workflows. Level 3 matters when timing does. If your background check vendor returns a clear result at 4:50pm on a Friday and your ATS polls once a day at midnight, you just lost a day on a candidate who has another offer. Webhooks solve that. Nightly syncs do not.
My view is that the level 0 and level 1 connections are worse than nothing, because they create the appearance of automation while quietly requiring a human to remember something every week. People stop remembering. Then the data drifts, and nobody trusts the pipeline numbers.
The shortlist
The nine connections worth caring about
Vendors advertise hundreds. You need nine, and four of those nine apply to every team regardless of size or industry. The rest depend on how you hire.
Nine connections, ranked by who actually needs them
Job boards
Indeed, LinkedIn, niche boards
Calendar
Google Workspace, Microsoft 365
Email + inbox sync
Threaded replies inside the record
Career site
Embedded or hosted, indexable
Assessments
TestGorilla, HackerRank, Codility
Background checks
Checkr, HireRight, Sterling
Chat
Slack or Teams alerts
HRIS + payroll
The hire-to-onboard handoff
SSO + directory
SAML, SCIM deprovisioning
Notice what is not on the list. Video conferencing rarely needs a real integration, because a Zoom or Meet link generated by the calendar invite is enough. Sourcing tools matter for a specific kind of team and almost nobody else. E-signature is often bundled into offer management already. Cut the list to what you will use in the first ninety days, then revisit.
Connection 1
Job boards: what Indeed integration really involves
"We integrate with Indeed" is the single most overloaded claim in ATS sales. Indeed's partner program has three distinct pieces, documented separately in Indeed's partner documentation, and a vendor can support any one of them and still use the same sentence.
Job Sync API
Pushes your open roles to Indeed automatically. This is the piece almost everyone builds. It is also the least valuable of the three, because a free XML feed does roughly the same job.
Indeed Apply
Lets a candidate finish their application inside Indeed and delivers it to your ATS with the resume attached. Removes a redirect step that loses people. This is the piece that changes your apply rate.
Disposition Sync API
Sends status changes back to Indeed when you reject, advance, or hire. Indeed uses that signal to improve how your ads get targeted. Most vendors skip it. It is the one that compounds.
When you ask a vendor about Indeed, ask which of the three. If the answer is vague, it is Job Sync only. That is fine for a small team posting two roles a quarter. It is not fine if you are spending real money on sponsored job ads, because without disposition data Indeed is optimizing your spend on applications rather than on hires.
The same three-layer question applies to every board. Does it post? Does it deliver applications back with the attachment? Does it report outcomes? Our breakdown of what Indeed actually costs employers covers the spend side of this.
Connection 2
LinkedIn: free integration, paid entry ticket
LinkedIn states plainly on its hiring integrations page that it charges no fee for hiring integrations, and that they are included with your Recruiter license at no additional cost. Read that second clause carefully. The integration is free. The license it depends on is not.
Two products do most of the work. Recruiter System Connect puts LinkedIn profile insights next to the candidate record in your ATS and shows which candidates you have already touched, so two recruiters stop InMailing the same person. Apply Connect posts jobs in real time and routes LinkedIn applications into your ATS. There is also Apply with LinkedIn, which pre-fills an application on your own career site from a candidate's profile, and that one does not carry the same license requirement.
The practical trap: teams shortlist an ATS partly because it lists LinkedIn integration, discover during rollout that Recruiter System Connect needs a Recruiter seat at several thousand dollars a year, and quietly drop the feature. Confirm the license requirement before it becomes a surprise line item. If you are already evaluating alternatives to a Recruiter contract, our post on LinkedIn Recruiter alternatives covers what you give up.
Connection 3
HRIS: the handoff where data goes to die
The hire-to-onboard handoff is the integration with the worst reputation, and it earns it. A candidate record in an ATS and an employee record in an HRIS describe the same person using almost no common fields. The ATS knows their source, their interview scores, and their offer history. The HRIS wants a legal name, a tax jurisdiction, a manager, a cost center, and a start date. Only three or four fields overlap cleanly.
So ask what the connector maps, not whether it exists. In practice you want first name, last name, personal email, phone, start date, job title, department, manager, employment type, and location to move without a human. Everything past that is a bonus. Anything missing from that list becomes a form somebody fills in on the new hire's first morning, which is the exact moment you want to be doing something better.
Understanding the boundary helps here. Our comparison of ATS vs HRIS covers which system should own what, and ATS vs CRM covers the sourcing side of the same question.
An ATS where the connections are already built
Prepzo posts to the boards you use, syncs calendars, and keeps the candidate record in one place, so your team stops rekeying data between four tools.
Try Prepzo freeUnder the hood
Native connectors, unified APIs, and middleware
There are three ways a vendor gets you a connection, and they behave differently once you are live.
Native means the ATS vendor wrote and maintains the code for that specific tool. Deepest field coverage, best error handling, slowest to add new ones. Unified API means the vendor plugged into a provider like Merge or Kombo, which normalizes dozens of HR systems behind one shared data model. You get breadth in weeks instead of years, at the cost of any field that does not fit the shared model. Custom fields are the usual casualty. Middleware means Zapier, Workato, or similar, where you build and own the automation yourself.
None of these is wrong. What matters is knowing which one you bought, because it determines who fixes it. When a job board changes its API, a native connector gets patched by your vendor. A unified API gets patched by the API provider, usually fast, since every customer is affected. A Zapier recipe breaks silently and stays broken until someone notices applications stopped arriving. That someone is you.
Custom work is the expensive fourth option. HR.com's integration research and the vendor ecosystem around it consistently put bespoke HR system builds in the four to eight week range per system, before maintenance. That is the number to hold in your head when a salesperson offers to "build it for you."
What goes wrong
Five failure modes I see constantly
Silent failure
The connection dies and nobody is told. Applications stop arriving on a Tuesday and someone spots it the following Monday. Ask what alerting exists when a sync fails. If the answer is a status page, that is not alerting.
Duplicate records
The same candidate applies through the career site and through Indeed and becomes two people. Ask what the deduplication key is. Email alone is not enough when people use a work address once and a personal address later.
One-way sync sold as two-way
Jobs go out. Statuses never come back. Your board analytics stay permanently wrong and you never find out why your cost per hire looks strange.
Field truncation
A unified API flattens a custom field into a note, or drops it. Salary bands and requisition codes are the usual victims. Test with your real field names, not the demo data.
Orphaned access
A recruiter leaves. Their OAuth token still authorizes the calendar sync. Six months later that connection is still running under a deactivated account. This is why SCIM deprovisioning belongs on the list.
Four of these five are invisible during a demo and obvious three months in. That asymmetry is the whole problem with evaluating integrations, and it is why the questions below matter more than the logo grid.
The buying test
How to test integrations before you sign
Do not accept a screenshot. Ask to see the connection work live, on the call, with a job that resembles one of yours. A vendor with a real connector will do this without hesitation. A vendor with a roadmap will offer to schedule a technical follow-up, which is the answer.
Six questions that separate a real connector from a roadmap slide
Show me a job posting to Indeed live, right now, in this call.
When I reject someone here, what does Indeed see and when?
Which fields does your HRIS connector drop when it maps a hire?
Is this connector built by you or resold through a unified API?
What happens to the queue when the other system is down for an hour?
Who pays when a job board changes its API next quarter?
Then run one more test during the trial. Post a real job, apply to it yourself from a job board using a personal email, and time how long the application takes to appear in the pipeline with the resume attached. Reject yourself and check whether that status reaches the board. Twenty minutes of work tells you more than any reference call.
Also check the boring governance items. Ask whether the integration is covered by the vendor's SOC 2 scope, whether candidate data crosses a region boundary, and what the retention policy is on data pushed to third parties. If you hire in the EU this is not optional, and the answers should be immediate. Vendors who have thought about it answer in one sentence.
Right-sizing
How many integrations you actually need
Integration count is a vanity metric. What matters is whether the specific handoffs you perform weekly happen without a human. A twelve-person company hiring four people a year needs a calendar connection and one job board. Everything else is theater.
The honest answer is that most teams over-buy integration breadth and under-buy integration depth. A vendor with 40 shallow connectors will lose to one with 8 that work every time. Pick the second one. Then check our guides on recruitment automation and recruitment metrics to decide what to automate once the plumbing works.
Frequently Asked Questions
What is an ATS integration?
An ATS integration is a live connection between your applicant tracking system and another tool, so data moves between them without anyone retyping it. Common examples are pushing a job to Indeed and LinkedIn, pulling applications back in, booking interviews on Google Calendar, ordering a background check, and handing a new hire to your HRIS on their start date.
What is ATS integration in Indeed?
Indeed runs a partner program with three separate pieces. The Job Sync API pushes your open roles to Indeed. Indeed Apply lets a candidate apply inside Indeed and delivers that application straight into your ATS. The Disposition Sync API sends status changes back to Indeed when you reject, advance, or hire someone. Many tools only build the first one, so ask which of the three your vendor actually supports.
Does LinkedIn charge for ATS integration?
No. LinkedIn states on its hiring integrations page that it charges no fee for the integrations themselves. The catch is licensing: Recruiter System Connect and Apply Connect are included with a LinkedIn Recruiter license, so you need to be paying for Recruiter to switch them on. The integration is free. The seat it rides on is not.
Which ATS has the best job board integrations?
Rather than chase a single winner, check three things for the boards you actually use: whether jobs post automatically or need a manual export, whether applications flow back in with the resume attached, and whether candidate status changes sync back to the board. Most vendors do the first, many skip the third, and the third is what improves your ad targeting over time.
What is the difference between a native integration and a unified API?
A native integration is built and maintained by the ATS vendor for one specific tool. A unified API, from a provider like Merge or Kombo, is a single connector that talks to dozens of systems through one shared data model. Unified APIs give you breadth quickly but flatten fields that do not map cleanly, so custom data sometimes gets dropped. Native connections are deeper and slower to build.
How long does an ATS integration take to set up?
A prebuilt connector with OAuth login usually takes minutes. Job board partnerships can take one to two weeks because the board has to approve the account. Custom work is the outlier: HR.com and Sapient Insights research puts bespoke HR system integrations in the four to eight week range per system, which is why you should count prebuilt connectors during a demo rather than accept a promise to build one.
Do I need integrations if I only hire a few people a year?
Fewer than you think. At under roughly 20 hires a year, a calendar connection and a job board connection cover most of the pain. Background checks and HRIS handoff can stay manual without much cost. Buying an expensive integration platform for six hires is a waste. Buying an ATS that cannot post to Indeed is a different kind of waste.
Resources & Further Reading
Related Guides
- ATS Implementation Guide
What to sequence before the connectors go live
- ATS Migration Checklist
Moving data without losing history
- ATS vs HRIS: Which System Owns What
Where the hire-to-onboard handoff belongs
- Prepzo ATS Pipelines
One candidate record across every stage
External Sources
- LinkedIn: Hiring Integrations
Recruiter System Connect and Apply Connect requirements
- Indeed: Partner Documentation
Job Sync, Indeed Apply, and Disposition Sync APIs
- Sapient Insights Group: HR Systems Survey
Integration counts across mid-market HR stacks
- SHRM: HR Technology
Governance and vendor evaluation guidance
