Search found 10 matches

by bashen
Thu Jan 09, 2020 6:09 pm
Forum: Bullhorn APIs
Topic: Update Candidate no longer working
Replies: 7
Views: 2103

Re: Update Candidate no longer working

"No valid input data found to parse"

This is the error you get if the POST body is completely empty. If it was invalid JSON you would get something like a "JSON Processing Error" instead. I would check to make sure however you're sending the POST request is including the JSON body.
by bashen
Wed Jan 08, 2020 5:00 pm
Forum: Bullhorn APIs
Topic: Update Candidate no longer working
Replies: 7
Views: 2103

Re: Update Candidate no longer working

I don't believe the Candidate ID is optional in the POST URL.

What was your original error when you included the Candidate ID in the URL?
by bashen
Fri Nov 22, 2019 4:37 pm
Forum: Bullhorn APIs
Topic: How do I update a field's value to NULL via Rest API?
Replies: 1
Views: 2876

Re: How do I update a field's value to NULL via Rest API?

Setting the value to all-lowercase 'null' (no quotes) should work.

Example:

POST entity/Candidate/123456

Body:

Code: Select all

{
	"customText1": null
}
by bashen
Fri Nov 22, 2019 4:28 pm
Forum: Bullhorn APIs
Topic: How to get the correct default value of date time fields Using Rest API?
Replies: 1
Views: 1636

Re: How to get the correct default value of date time fields Using Rest API?

My guess is that Bullhorn is ignoring the time portion ("01:00PM") when setting the field and only using the day portion ("08/20/2017"). Bullhorn stores their dates in ET (Eastern Timezone). So, this date would be stored as "08/20/2017 12:00 AM ET". The Bullhorn REST API returns dates in UTC time so...
by bashen
Fri Jul 19, 2019 1:07 pm
Forum: Bullhorn APIs
Topic: Get details of event subscriptions
Replies: 5
Views: 2430

Re: Get details of event subscriptions

Just wanted to add that I ran into this too. It seems odd you can't get a list of your current subscriptions via the API. If you do loose track of your subscriptionId, you need to contact Bullhorn support. Like you said, Bullhorn support can provide you will a list of your current subscriptions. It'...
by bashen
Mon Jul 01, 2019 4:24 pm
Forum: Bullhorn APIs
Topic: Why does this return null?
Replies: 1
Views: 1269

Re: Why does this return null?

Try it with single quotes around the name:

query/CorporateUser?where=name='Dani Shambaugh'&fields=name,email

If the name itself contains a single quote, you will need to escape it with another single quote. For example:
query/CorporateUser?where=name='Mike O''Doul'&fields=name,email
by bashen
Wed Sep 26, 2018 4:57 pm
Forum: Bullhorn APIs
Topic: query vs. search - which entity types are supported?
Replies: 2
Views: 3621

Re: query vs. search - which entity types are supported?

Thanks for the reply Patrick. The example you provided for Candidate uses the "search" endpoint, not "query". I have successfully used the "search" endpoint for Candidate but when I try to use the "query" endpoint I get an error. e.g. query/Candidate?where="address.state = 'New York'"&fields=id retu...
by bashen
Wed Sep 19, 2018 4:41 pm
Forum: Bullhorn APIs
Topic: query vs. search - which entity types are supported?
Replies: 2
Views: 3621

query vs. search - which entity types are supported?

Hi all,

Is there any documentation on what entity types are supported for "query" and "search" APIs? I noticed you can't use "query" for Candidates and can't use "search" for PlacementCommission.

Thanks,
brian
by bashen
Mon Sep 17, 2018 11:18 am
Forum: Bullhorn APIs
Topic: Events Count Support in REST
Replies: 2
Views: 3378

Events Count Support in REST

Hi all,

I was looking for the analogous to the "eventsCount" SOAP method in REST. I don't see anything in the documentation. Can I get the events count using the REST API?

thanks,
brian
by bashen
Thu Aug 09, 2018 2:03 pm
Forum: Bullhorn APIs
Topic: Returning HTTP 500 for Bad Requests with Invalid Dates
Replies: 0
Views: 9680

Returning HTTP 500 for Bad Requests with Invalid Dates

Hi all, I was testing updating a custom object in Postman and specifying invalid values in my JSON body. In one case, I specified a custom date field with a decimal value (1533132317.34) and got back the following response. { "errorMessage": "setting property", "errorMessageKey": "errors.errorSettin...