Legacy HTTP version of the APIs will be deprecated

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
nquinn
User
Posts: 5
Joined: Fri Apr 04, 2014 12:31 pm

Legacy HTTP version of the APIs will be deprecated

Post by nquinn » Fri Apr 04, 2014 2:51 pm

Hi All:

I am new to this forum and Bullhorn APIs. And am working on a legacy project worked on by an earlier developer who is no longer with us. We recently received an update notification

"The purpose of this communication is to notify you that the Bullhorn Legacy HTTP version of the APIs will be deprecated and cease to function as of June 1, 2014. "

with a hyper link http://www.bullhornstaffing.com/Bullhor ... 0bgIXRk%3D

On looking up the code, this is what is used for Candidate Register
https://www.bullhornstaffing.com/Bullho ... chFile.cfm

Looks like the CFM talked about in the update. Will these links need to be changed? if so is this a minor URL change or a major change? Where can I find documentation related to the deprecated APIs?

Thanks

Any help will be appreciated.

nquinn
User
Posts: 5
Joined: Fri Apr 04, 2014 12:31 pm

Re: Legacy HTTP version of the APIs will be deprecated

Post by nquinn » Wed Apr 23, 2014 8:49 am

Hi Support:

Can some one please respond to the above questions?

Thanks

s.emmons
User
Posts: 333
Joined: Wed Dec 31, 1969 8:00 pm

Re: Legacy HTTP version of the APIs will be deprecated

Post by s.emmons » Thu May 01, 2014 2:35 pm

Hi nquinn,

I apologize for the delayed response.

That particular API call (AttachFile.cfm) is being deprecated on June 1st, so you will need to update that call completely using a newer version of our APIs. This call can't be replaced with a simple URL change.

You can find documenation for our SOAP based WebServices 2.5 or our REST API here: http://developer.bullhorn.com/documentation
Sam Emmons
Enterprise Team Lead
BULLHORN
US Support 617-478-9126

nquinn
User
Posts: 5
Joined: Fri Apr 04, 2014 12:31 pm

Re: Legacy HTTP version of the APIs will be deprecated

Post by nquinn » Tue May 20, 2014 6:15 pm

Hi Sam:

Looks like we are using web services 1.1. Is there a guide to upgrading from SOAP API Version 1.1 to SOAP API Version 2.5. I suspect there is a lot more to it than just changing out the .cfm extensions? Also, is there a phone number where I can get phone support on this topic?

Let me know.


s.emmons wrote:Hi nquinn,

I apologize for the delayed response.

That particular API call (AttachFile.cfm) is being deprecated on June 1st, so you will need to update that call completely using a newer version of our APIs. This call can't be replaced with a simple URL change.

You can find documenation for our SOAP based WebServices 2.5 or our REST API here: http://developer.bullhorn.com/documentation

nquinn
User
Posts: 5
Joined: Fri Apr 04, 2014 12:31 pm

Re: Legacy HTTP version of the APIs will be deprecated

Post by nquinn » Wed May 21, 2014 3:40 pm

Hi Sam:

Can you please let me know on the above? Is there a guide to upgrading from SOAP API Version 1.1 to SOAP API Version 2.5. I suspect there is a lot more to it than just changing out the .cfm extensions?

Thanks

s.emmons
User
Posts: 333
Joined: Wed Dec 31, 1969 8:00 pm

Re: Legacy HTTP version of the APIs will be deprecated

Post by s.emmons » Mon Jun 09, 2014 5:04 pm

Hi nquinn,

Are you sure you're using SOAP 1.1? The link you referenced in your original post calls out the Legacy AttachFile.cfm operation, which you will need to update now by June 30th.

There isn't much documentation on upgrading from 1.1 to 2.5, as it's mainly just repointing to a different WSDL. The main differences between the versions are:

- Session response has a different structure (I responded on that here: http://supportforums.bullhorn.com/viewt ... 84e7862e4b
- Bug fixes
- Exposure to edit history
Sam Emmons
Enterprise Team Lead
BULLHORN
US Support 617-478-9126

htphuong82
User
Posts: 20
Joined: Wed May 21, 2014 4:23 am

Re: Legacy HTTP version of the APIs will be deprecated

Post by htphuong82 » Thu Jun 26, 2014 6:25 am

Guys,

How to get new jar file for soap api 2.5?
I have this bullhorn-client-1.0-jar-with-dependencies.jar but it seems too old to get edit history.

Thanks,
Phuong
Phuong
Developer

s.emmons
User
Posts: 333
Joined: Wed Dec 31, 1969 8:00 pm

Re: Legacy HTTP version of the APIs will be deprecated

Post by s.emmons » Thu Jun 26, 2014 8:41 am

Sam Emmons
Enterprise Team Lead
BULLHORN
US Support 617-478-9126

htphuong82
User
Posts: 20
Joined: Wed May 21, 2014 4:23 am

Re: Legacy HTTP version of the APIs will be deprecated

Post by htphuong82 » Thu Jun 26, 2014 9:47 pm

Thanks Sam for your very quick response.

I am trying to get new APIs in order to get Placement Edit History, it seems impossible now.
Phuong
Developer

Locked