This is internal-facing reference material for discovery, scoping, and support triage. It is a first-pass mapping and should be confirmed against the capability matrix and the
api integration library before relying on it. Where a requirement is unconfirmed, it is flagged in the notes column rather than assumed.Requirements by feature
Each feature is mapped to the four integration models it depends on. Required means the feature cannot function without that model; — means it is not needed.How to read a row
- Job import only is the minimum for a careers site: search, job pages, job alerts, the candidate agent, and organic distribution all work as soon as vacancies are flowing in.
- Submitting applications unlocks the apply-through-inploi features: static flows, and (as an input) analytics and the scoring agent.
- Workflow sync is what separates dynamic flows (workflow read from the ATS) from static flows (built in inploi).
- Disposition is what makes analytics reflect real downstream outcomes rather than just applications submitted.
Related pages
Capability matrix
What each ATS supports across the four integration models.
ATS integrations register
Transport model and partner API documentation per ATS.