Short answer
An API on your ATS, access to your own data and someone who can say which fields you really use. We build and maintain the orchestration around it, in your own environment.
What a connection actually is
No migration and no new system. We write orchestration code that reads and writes through the official API of your ATS: pull a vacancy, look up candidates, write a note back. Claude does the language work, the API does the traffic.
That code runs in your own environment. No black box and no per-user licences. If we stop, you carry on.
What we need from you
- API access to the ATS or staffing software, usually through your administrator or vendor.
- A picture of the fields you really fill in, and the ones you can ignore.
- Your own format for screening or submitting, however informally it is written down.
- A contact person who watches and corrects during the build round.
The systems we connect to
OTYS, Bullhorn, Carerix, Recruitee, Easyflex and Salesforce Recruiting. The integrations page says per system what we do and do not claim.
If your package is not there, send a message. If there is an API, it usually works.
What if the data is wrong
That is normal and not a showstopper. We build around the data as it is, and database activation has a first cleanup in scope. Waiting until the ATS is tidy is usually waiting forever.