User Templates

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
cdubois
User
Posts: 12
Joined: Wed Dec 31, 1969 8:00 pm

User Templates

Post by cdubois » Tue Nov 27, 2007 2:06 pm

Our configuration employs userTemplates to keep track of certifications information for each candidate. Here's an example:

Code: Select all

<root>
<BHCandidate>
...
  <userTemplate_13681_1>ACLS</userTemplate_13681_1> 
  <userTemplate_13682_1>Test B</userTemplate_13682_1> 
  <userTemplate_13683_1>23423</userTemplate_13683_1> 
  <userTemplate_13684_1>Current</userTemplate_13684_1> 
  <userTemplate_13685_1>2007-11-30 00:00:00.0</userTemplate_13685_1> 
  <userTemplate_13686_1>No</userTemplate_13686_1> 
  <userTemplate_13681_2>CCRN</userTemplate_13681_2> 
  <userTemplate_13682_2>Test A</userTemplate_13682_2> 
  <userTemplate_13683_2>235232</userTemplate_13683_2> 
  <userTemplate_13684_2>Expired</userTemplate_13684_2> 
  <userTemplate_13685_2>2007-11-04 00:00:00.0</userTemplate_13685_2> 
  <userTemplate_13686_2>Yes</userTemplate_13686_2> 
...
</BHCandidate>
</root>
So the pattern is fairly clear here, and it seems the numbering is constant between USERIDs. I am looking to develop a way to allow the user to add, modify and delete these entries. For adding, I was able to get a SUCCESS response with the following xmlData posted to the Profile Update API.

Code: Select all

<root>
<BHCandidate>
<USERID>5</USERID>  <userTemplate_13681_3>CPR</userTemplate_13681_3> 
  <userTemplate_13682_3>Test B</userTemplate_13682_3> 
  <userTemplate_13683_3>222</userTemplate_13683_3> 
  <userTemplate_13684_3>Current</userTemplate_13684_3> 
  <userTemplate_13685_3>2007-11-30 00:00:00.0</userTemplate_13685_3> 
  <userTemplate_13686_3>No</userTemplate_13686_3> 
</BHCandidate>
</root>
Is there anything on the backend of Bullhorn that would get screwed up if I use this method? Are there places inaccessible using the API that need this data as well? Or am I good to go?

Thanks!

kevin
Bullhorn Employee
Posts: 118
Joined: Wed Dec 31, 1969 8:00 pm

Post by kevin » Tue Nov 27, 2007 2:41 pm

I would double check the certificates for the candidate to make sure they are created/updated correctly inside Bullhorn applicaion. Since you are only updating people template information, Bullhorn app should not be impacted.

cdubois
User
Posts: 12
Joined: Wed Dec 31, 1969 8:00 pm

Post by cdubois » Tue Nov 27, 2007 2:43 pm

From first glance, the candidate certification as seen from within Bullhorn matches the data I sent.

Thanks!

Locked