How to configure Bullhorn Redirect URI for creating a connection

April 8, 2026

When connecting Bullhorn to Unified, each customer must complete a one-time setup in their own Bullhorn account.

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****'

Note: if you are using CNAME (custom domain) the redirect URI will look like this https://YOUR_CUSTOM_DOMAIN/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.

4. Create the Connection in Unified

Once Bullhorn Support confirms that the redirect URI has been configured on your customer's account, you can then proceed with creating a Bullhorn connection.

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 for each of your customers using Bullhorn
• If the customer creates a new API user in the future, they will need to go through this process again.