Trouble-shooting FAQ

Have a question about Bullhorn's HTTP based APIs? You've found the right place.

API Update [posted on December 13, 2012]:

This version of the Bullhorn APIs should no longer be used.

All new work should be done using Bullhorn's REST or Web Services APIs. For more information please visit: http://developer.bullhorn.com/documentation

Bullhorn REST API provides a simpler and faster way for developers to build applications that interact with the Bullhorn platform and is used by Bullhorn Inc. to develop features of the Bullhorn ATS/CRM application.

Of the BullhornSTAFFING HTTP API interfaces listed below, our analysis shows that the following are most commonly used by developers:

Resume Parsing API
Published Job Data (XML)
The interface to these will continue to work as is because Bullhorn will replace the back end to use REST API. The URLs for these 2 specific APIs may change in the 2nd half of 2013; developers may require to update their applications to use the new URLs.

Moderators: StaffingSupport, s.emmons

Locked
cseibert
Bullhorn Employee
Posts: 393
Joined: Wed Dec 31, 1969 8:00 pm

Trouble-shooting FAQ

Post by cseibert » Mon Apr 16, 2007 5:07 pm

If you're experiencing a problem with the API, there are a few things that you can do to speed up the process of getting a resolution.

1. Try to reproduce the problem by hitting the Bullhorn API test pages directly at:

http://www.bullhornstaffing.com/BullhornStaffing/API/

This will take your code out of the picture, and give us a clean test case.

2. Post in these forums with the reproducable case. Please be sure to include:
  • 1.The private label ID (PLID). Note: this can NOT be used to access your data without an encryption key.
    2.The URL of the Bullhorn API or test page that you are having problems with. A specific URL is more precise than simply "the job API", of which we have many.
    3. The data you are posting to that Bullhorn API or test page to reproduce the problem.

    We need the above three at an minimum to trouble-shoot an issue.

    Ideally, you would also provide us with:
    4. The expected result.
    5. The actual result.

    ***DO NOT post your encryption key in these forums. That would allow anyone with forum access to query against your data.***
Last edited by cseibert on Mon Jun 11, 2007 11:09 am, edited 1 time in total.

cseibert
Bullhorn Employee
Posts: 393
Joined: Wed Dec 31, 1969 8:00 pm

Invalid encryptedAPIKey error

Post by cseibert » Thu Apr 19, 2007 3:16 pm

If you post to an API and get a "Invalid encryptedAPIKey error", the most likely causes are:

1. You actually have the wrong privateLabelID and/or encryptionAPIKey.
2. You are not URL encoding the key when you post it.

The format we use for keys looks like it is URL encoded, but actually it is not. As will all HTTP posts, whether it's a POST or a GET, you need to URL encode the values getting posted, or they will not decode properly on the API side.

See the base FAQ for examples of how to URL encode in a few different languages.

angelrosely
User
Posts: 1
Joined: Sat Apr 14, 2012 10:38 pm

Re: Trouble-shooting FAQ

Post by angelrosely » Sat Apr 14, 2012 10:50 pm

1. You actually have the wrong privateLabelID and/or encryptionAPIKey.
2. You are not URL encoding the key when you post it. I agree with you!





-------------------------------------------------------------------------------------
Nike Air Max 2012|Coach Shoulder Bag|Coach Poppy Bags

Locked