How to get your Bullhorn OAuth2 Client ID, OAuth2 Client Secret, API Username and API Password: Step-by-step guide

Updated: April 24, 2023

April 24, 2023

If you're building an integration with Bullhorn, you'll need an OAuth2 Client ID, OAuth2 Client Secret, API Username and API Password from your customer's Bullhorn account to authenticate requests.

This guide shows you (or your customers) how to generate one from Bullhorn's account settings.

Why this is required?

Bullhorn requires every connected application to use its own API user, client ID, client secret, and approved redirect URI. The redirect URI cannot be updated through the Bullhorn web interface, so Bullhorn Support must be contacted to approve and configure the redirect URI.

Steps your customer must complete

1. Create an API User in Bullhorn

The customer must create a dedicated API user for the application they want to connect.

During this process, Bullhorn will provide:

• Client ID
• Client Secret

These credentials will later be used when creating the connection in Unified.

Note: A new API user is required each time a new application is connected to Bullhorn.

2. Contact Bullhorn Support

After creating the API user, the customer must contact Bullhorn Support and request that the redirect URI for the API user be updated.

The customer should provide:

• The API user or application they created
• The Unified redirect URI

Example request:

Please update the redirect URI for our Bullhorn API user to the following Unified redirect URI: https://api.unified.to/oauth/code

3. Wait for Bullhorn to approve and apply the Redirect URI change

Bullhorn does not currently allow redirect URIs to be configured through the Bullhorn web UI.

Because of this, the redirect URI change must be completed by Bullhorn Support before the connection can work.

Important Notes

• Every customer must request the redirect URI change individually for their own Bullhorn account.
• This is a Bullhorn limitation and cannot be configured directly in the Bullhorn UI or programmatically via Unified.
• This is a one-time setup
• If you create a new API user in the future, you will need to go through this process again

Generating a Bullhorn OAuth2 Client ID, OAuth2 Client Secret, API Username and API Password is the first step. The harder part is building pipelines that stay reliable as customers add more systems.

Unified.to gives you options: deliver data via API, streaming webhooks, database sync, or even as MCP tools for AI agents. One integration layer that adapts to your architecture instead of forcing tradeoffs.

Book a demo to see how we simplify integration delivery across 1323 integrations and 37 categories.