Connect Bullhorn to TalentDesk

TalentDesk reads your jobs, candidates and submissions to power your pipeline board, and writes back only the things you do on it - stage moves, placements and notes you approve. It never deletes anything in Bullhorn. Credentials are encrypted at rest and used only for your workspace.

• 1Client IDA code that identifies TalentDesk to Bullhorn. Bullhorn Support creates it when you ask for REST API credentials.
• 2Client SecretThe password that goes with the Client ID. Bullhorn sends it securely - treat it like a bank PIN.
• 3API UsernameA dedicated Bullhorn login used only for the connection (an API user or service account) - not your own login.
• 4API PasswordThe password for that API user.
• 5Data centre (swimlane)Which Bullhorn cluster your account lives on, e.g. rest91. Support includes it - and if you cannot find it, TalentDesk can detect it automatically from the API username.

Ask Bullhorn Support (or your Bullhorn account manager) for REST API credentials for a third-party integration. This is a routine request - they handle it constantly - but allow 5 to 10 business days. Kick it off before anything else.

One extra question worth asking in the same message: whether your account restricts API access by IP address. If it does, mention that a cloud-hosted integration needs access and Support will set it up.

Sign in to TalentDesk and the setup wizard resumes right where you left off (or head to Settings, then Connections). Paste in the five values, TalentDesk tests the connection instantly, and your jobs and candidates start syncing within minutes.

Credentials are stored encrypted and never shown again after entry. Access is read-plus-approved-writes only. To revoke TalentDesk at any time, rotate the API user password in Bullhorn - the connection stops immediately. Your TalentDesk trial does not burn down while you wait for Bullhorn - the wait is normal and expected.