One platform, endless possibilities.

Most take a couple of minutes: authorise Arbi from the Connections tab, pick the job or pipeline it should write to, and the first sync runs straight away. A few platforms let every customer name their own fields, so those need a mapping step first and someone from our side walks you through it.

The directory above is the live list, covering the applicant tracking systems and CRMs most hiring teams already run. It is read straight from the platform, so what you see here is what is connectable today rather than a page someone remembered to update.

Yes. Candidates, notes, and interaction history push from Arbi into your ATS, and stage changes come back the other way. A candidate moved to interview in your ATS reads as interviewing in Arbi without anyone retyping it, which is what keeps two systems from disagreeing about the same pipeline.

Arbi matches them before it writes anything and marks them in search results, so you can see who is already in play instead of sourcing them a second time. Where a match exists the interaction is logged against that record, so the integration never leaves you deduplicating afterwards.

No. Connecting an integration is an authorisation a recruiting operations lead can complete on their own. You will need admin rights in the other platform, and on a few systems candidate creation has to be enabled on your plan before Arbi can write to it.

Tell us. Request Integration goes to the team that builds them, and what customers ask for is what decides the order they get built in. If you need something sooner than the roadmap allows, our API covers the same reads and writes the built integrations use.

Only what the integration needs: candidate records, the jobs or pipelines you point it at, and the activity Arbi logs against them. Every scope is listed on the authorisation screen before you approve it, and you can narrow what a connection is allowed to touch after the fact.

Connections are held as revocable tokens rather than stored passwords, traffic is encrypted in transit, and every write lands in an audit trail you can export. Arbi is SOC 2 Type II certified and supports SSO and SAML, role based permissions, and data residency controls.