> ## Documentation Index > Fetch the complete documentation index at: https://docs.inploi.com/llms.txt > Use this file to discover all available pages before exploring further. # ATS integrations > A working register of the applicant tracking systems inploi integrates with, how each one is reached, and where to find the partner's own API documentation. This page is a reference layer for **Sales, Customer Success, and Engineering**. It lists every applicant tracking system (ATS) inploi integrates with, how inploi connects to it, and where each partner's own API documentation lives. It answers two recurring questions quickly: * **"Can we integrate with ATS X?"** — see the [capability matrix](/integrations/ats/capability-matrix) for what each integration supports across our four integration models. * **"Where are the partner's API docs?"** — see the [documentation register](#documentation-register) below. This is internal-facing reference material. It is not part of the candidate-facing careers-site documentation, and it describes inploi's integration capability rather than instructing a customer to build anything themselves. ## The four integration models Every ATS integration is described against the same four data flows. Each has its own detailed page: | Model | Direction | What it does | | -------------------------------------------------------------------- | ------------ | --------------------------------------------------------------------------------------- | | [Job import](/integrations/ats/job-import) | ATS → inploi | Open roles in the ATS become live listings; closed roles are expired. | | [Submitting applications](/integrations/ats/application-submissions) | inploi → ATS | Completed applications are posted to the ATS against the correct job. | | [Application workflow sync](/integrations/ats/workflow-sync) | ATS → inploi | Each job's application workflow is read from the ATS and recreated on the careers site. | | [Disposition data sync](/integrations/ats/disposition-sync) | ATS → inploi | Outcomes and statuses flow back into inploi for reporting. | ## How inploi reaches an ATS There are three transport models. Which one an ATS uses matters, because it affects what is possible and who maintains the connection. | Transport | What it means | | ------------- | ---------------------------------------------------------------------------------------------------------------------- | | **Direct** | inploi has built and maintains a custom integration against the ATS's own API. | | **Via Kombo** | inploi reaches the ATS through the [Kombo](/integrations/ats/kombo) unified API rather than connecting to it directly. | | **Via feed** | inploi ingests jobs from an XML or CSV feed. Typically jobs-only, with no application write-back. | ## Documentation register Partner API documentation is **referenced, never copied**. Always open the partner's own docs at query time and cite the source URL — the links below are the entry points. "Access" describes how reachable that documentation is. | ATS | Transport | Partner API documentation | Access | | -------------------- | --------- | -------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------- | | Ashby | Direct | [developers.ashbyhq.com](https://developers.ashbyhq.com/) | Public | | Cornerstone OnDemand | Direct | [csod.dev](https://csod.dev/) | Customer/partner portal | | Dayforce | Direct | [developers.dayforce.com](https://developers.dayforce.com/) · [help.dayforce.com](https://help.dayforce.com/) | Developer network (registration) | | Talent Funnel | Direct | [status.talent-funnel.com](https://status.talent-funnel.com/) | Status page public; API docs on request | | Talos360 | Direct | [talosats.statuspage.io](https://talosats.statuspage.io/) | On request; status page public | | Tribepad | Direct | [docs.tribepad.com](https://docs.tribepad.com/docs/getting-started) · [learn.tribepad.com/apis](https://learn.tribepad.com/apis) | Portal, API key required | | Harri | Direct | [developer.harri.com](https://developer.harri.com/) | Members only | | Pinpoint | Direct | [developers.pinpointhq.com](https://developers.pinpointhq.com/) | Public | | Eploy | Direct | [eploy.com/resources/developers](https://www.eploy.com/resources/developers/api-documentation/) | Public | | Element Suite | Direct | Link to confirm | Unknown | | Fourth | Direct | Link to confirm | Unknown | | Access Group | Via feed | Link to confirm | Feed only | | JobTrain | Via feed | Link to confirm | CSV / API on request | | Kombo (aggregator) | Via Kombo | [docs.kombo.dev](https://docs.kombo.dev/ats/introduction) | Public | | SAP SuccessFactors | Via Kombo | [kombo.dev/integrations/successfactors](https://www.kombo.dev/integrations/successfactors) | Reached through Kombo | | Workday | Via Kombo | [docs.kombo.dev](https://docs.kombo.dev/ats/introduction) | Reached through Kombo | | Eploy (via Kombo) | Via Kombo | [docs.kombo.dev](https://docs.kombo.dev/ats/introduction) | Reached through Kombo | Where a cell reads "Link to confirm", the partner documentation URL has not yet been verified. Do not invent one — confirm the source before citing it, then update this register. ## Related pages What each ATS integration supports across the four models. Which integration models each inploi feature requires. How inploi reaches ATSs through the Kombo unified API.