Delay in registering a new Client ID?

Forum for users and developers of Bullhorn's new REST API service.

Moderators: StaffingSupport, s.emmons, BullhornSupport

Post Reply
DaveNorthCreek
User
Posts: 89
Joined: Fri Nov 20, 2015 2:04 pm

Delay in registering a new Client ID?

Post by DaveNorthCreek » Mon May 21, 2018 7:53 pm

Hi Bullhorn,

I have a client who is trying to set up an integration through the REST API (as seen in my previous posting). I am going through the process that has worked for my other clients to get through the initial registration process to get him a refresh token and through to being logged in.

I have his copied/pasted email from "Mick" from Bullhorn Support. It has all the required OAuth information: client id, client secret, API Username, API Password. I plugged that information into my existing code, which creates a url like:

Code: Select all

https://auth.bullhornstaffing.com/oauth/authorize?client_id=**REDACTED**&response_type=code&redirect_uri=www.bullhorn.com&state=test_state
but that gives the result:

Code: Select all

<html>
    <head>
        <title>Bullhorn OAuth Error - Invalid Client Id</title>
    </head>
    <body>
        <h1>Bullhorn OAuth Error</h1>
        <h2>Invalid Client Id</h2>
        <table>
            <tr>
                <td>
            Client Id:
        </td>
                <td>
            **REDACTED**
        </td>
            </tr>
        </table>
    </body>
</html>
(And yes, the code I REDACTED is the same in both locations).

Is there a delay in getting the Client ID registered for use with REST? Could it be a typo?

Next step will be a support ticket, but if someone here can diagnose this problem, that would be quicker for everyone.

Thanks,

Dave
North Creek

DaveNorthCreek
User
Posts: 89
Joined: Fri Nov 20, 2015 2:04 pm

Re: Delay in registering a new Client ID?

Post by DaveNorthCreek » Wed May 23, 2018 3:29 pm

This has been resolved - thanks to Mick!

The issue was that my IP address needed to be whitelisted - another hoop we need to jump through in order to deliver services to Bullhorn clients who need to use the REST API to extend Bullhorn's capabilities.

Post Reply