Page 1 of 1

Handle Escaped Values in Query Endpoint

Posted: Thu Mar 30, 2017 2:27 pm
by Kazemi
We need to query for a corporate user. Let's say we're searching using someone's name, which for this example is Joe O'Brien. Using the /query endpoint, how should we escape the name in the url properly?

Here are a couple examples we've tried:
https://rest32.bullhornstaffing.com/res ... "name='Joe O'Brien'"
https://rest32.bullhornstaffing.com/res ... "name='Joe O\'Brien'"

In both cases, Bullhorn is interpreting the apostrophe in O'Brien as the end of the name field, and the latter part of the name, "Brien", is seen as extraneous and causes a 400 response.

Re: Handle Escaped Values in Query Endpoint

Posted: Thu Apr 06, 2017 7:43 pm
by Kazemi
Hi Bullhorn team, any updates?

Re: Handle Escaped Values in Query Endpoint

Posted: Fri Apr 07, 2017 3:50 pm
by Kazemi
Through trial and error, we found the solution to be using double apostrophes. E.g.,

https://rest32.bullhornstaffing.com/res ... "name='Joe O''Brien'"

Your documentation fails to reflect this.