Skip to main content
This matrix maps every applicant tracking system (ATS) inploi integrates with against the four integration models. Use it to answer “can we do X with ATS Y?” during discovery, scoping, and support triage.
This matrix is seeded from the ATS compatibility sheet and is intended to be regenerated from the api integration library in a later phase. Treat it as the current best summary of confirmed capability, not a live read of production. When a capability is unconfirmed, it is shown as Not supported rather than assumed — confirm against the code or the partner before relying on it.

​
Legend

Transport shows how inploi reaches the ATS — Direct (custom integration against the ATS API), Via Kombo (through the Kombo unified API), or Via feed (XML/CSV ingestion, typically jobs only).

​
Capability by ATS

​
How to read a row

  • Jobs supported, everything else Not supported is the typical shape of a feed-based integration: inploi ingests vacancies for the careers site, but applications are completed elsewhere and outcomes do not flow back.
  • Partial on Applications or Workflows usually means the ATS API exposes the capability but it is not fully productionised, or it depends on a manual or feed-based step during implementation.
  • The same ATS can appear twice with different transports (for example, Eploy direct versus via Kombo) because the capability set differs by how inploi connects.

Feature integration requirements

Which integration models each inploi feature needs — read alongside this matrix.

ATS integrations register

Transport model and partner documentation links per ATS.

Kombo integration

How the Via Kombo rows are reached.