Bullhorn REST API does not return duplicate records

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

Moderators: StaffingSupport, s.emmons, BullhornSupport

Post Reply
Posts: 3
Joined: Wed Aug 16, 2017 6:05 pm

Bullhorn REST API does not return duplicate records

Post by gunasma » Wed Nov 29, 2017 6:44 pm


In our bullhorn environments we query for a candidate email before we decide if we need to insert/update a candidate record.

The following code snippet uses the Rest SDK provided by bullhorn to query if a candidate email exists

String email = "someCandidateEmail@mail.com"
SearchParams params = ParamFactory.searchParams();
String luceneQuery =
"(email:" + email + " OR email2:" + email + " OR email3:" + email + ")"
+ " AND isDeleted:0";
Set<String> fieldSet = new HashSet<String>();

ListWrapper<Candidate> results = bhData.search(Candidate.class, luceneQuery, fieldSet, params);

We are recently identified an issue in how this query behaves.

Behavior 1 :

Sometimes a query to find a record that was recently created, does not work and due to this we are creating duplicate records.

Here is an example

On 10/20/2017 9:03 AM, 2 consecutive applies came in with the email address A.

During the second apply, the record created during the first iteration should have been picked up, but instead it did not . As a result of this we believed the second apply to be a new candidate and created a duplicate record.

This happens when the consecutive applies are back to back with little to no time in between them

We expect first record gets picked up properly irrespective of the time interval in between applies.

Can someone shed some light on the issue?

Posts: 7
Joined: Wed Dec 06, 2017 1:38 pm

Re: Bullhorn REST API does not return duplicate records

Post by xventola » Thu Dec 07, 2017 9:06 am

Hi gunasma,

This is Xander from Bullhorn Support.

Are you receiving these new candidates through a job board or applicant portal that you custom coded? If so when you see these duplicates created, do they appear to be applies to the same position?

What is likely happening here is candidates are double clicking the submit or apply button which is sending two versions of the candidate to Bullhorn. The way Bullhorn's turnkey job board prevents this is by locking the submit/apply button so once it is clicked once it cannot be clicked again.

Let me know if you have any further questions.

Post Reply