- “Can we integrate with ATS X?” — see the capability matrix for what each integration supports across our four integration models.
- “Where are the partner’s API docs?” — see the 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 | ATS → inploi | Open roles in the ATS become live listings; closed roles are expired. |
| Submitting applications | inploi → ATS | Completed applications are posted to the ATS against the correct job. |
| Application workflow sync | ATS → inploi | Each job’s application workflow is read from the ATS and recreated on the careers site. |
| Disposition data 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 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 | Public |
| Cornerstone OnDemand | Direct | csod.dev | Customer/partner portal |
| Dayforce | Direct | developers.dayforce.com · help.dayforce.com | Developer network (registration) |
| Talent Funnel | Direct | status.talent-funnel.com | Status page public; API docs on request |
| Talos360 | Direct | talosats.statuspage.io | On request; status page public |
| Tribepad | Direct | docs.tribepad.com · learn.tribepad.com/apis | Portal, API key required |
| Harri | Direct | developer.harri.com | Members only |
| Pinpoint | Direct | developers.pinpointhq.com | Public |
| Eploy | Direct | eploy.com/resources/developers | 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 | Public |
| SAP SuccessFactors | Via Kombo | kombo.dev/integrations/successfactors | Reached through Kombo |
| Workday | Via Kombo | docs.kombo.dev | Reached through Kombo |
| Eploy (via Kombo) | Via Kombo | docs.kombo.dev | Reached through Kombo |
Related pages
Capability matrix
What each ATS integration supports across the four models.
Feature integration requirements
Which integration models each inploi feature requires.
Kombo integration
How inploi reaches ATSs through the Kombo unified API.