Search found 11 matches
- Mon Aug 15, 2016 12:47 pm
- Forum: Bullhorn APIs
- Topic: Filter by id not working for primarySkills in Candidate - 02309319
- Replies: 5
- Views: 10536
Re: Filter by id not working for primarySkills in Candidate - 02309319
Hello max_max_mir, I wanted to pass along what I believe needs to be done here. Can you try the below when bringing these back. This would be a GET. https://rest2.bullhornstaffing.com/rest-services/xxxxx/entity/Candidate/275166?fields=primarySkills&query={skill.id < 250}&BhRestToken=xxxxx Please let...
- Wed Jul 06, 2016 6:51 pm
- Forum: Bullhorn APIs
- Topic: Bug in REST API - 02281004
- Replies: 4
- Views: 8183
Re: Bug in REST API - 02281004
Hey Max, I spoke to our Engineering Team about this and have confirmed this is not a typo in the documentation. Even though there are a few different parameters to update when looking at the LoginRestrictions, this is looked at like it is all 1 field in the API. The CorporateUser structure is a litt...
- Wed Jul 06, 2016 6:46 pm
- Forum: Bullhorn APIs
- Topic: Cannot sort Note by id - 02281006
- Replies: 3
- Views: 6069
Re: Cannot sort Note by id - 02281006
Hey Max, If something specific comes up on it I will report it here but there is no specific reason that I know of other than it just being structured this way for the Note Entity. It is probably because the Note entity is a little more complex then the other main entities that have their own lists ...
- Tue Jul 05, 2016 11:03 am
- Forum: Bullhorn APIs
- Topic: Documentaion Error? George Boole is probably turning in his grave - 02281017
- Replies: 1
- Views: 3909
Re: Documentaion Error? George Boole is probably turning in his grave
Hello Max,
Yes you are correct here. The correct terminology should be something like Ternary here. I will bring this up with our documentation team and work on updating. Thank you for the notice here.
Yes you are correct here. The correct terminology should be something like Ternary here. I will bring this up with our documentation team and work on updating. Thank you for the notice here.
- Tue Jul 05, 2016 10:46 am
- Forum: Bullhorn APIs
- Topic: Candidate.employmentPreference not SCALAR - 02281016
- Replies: 2
- Views: 5566
Re: Candidate.employmentPreference not SCALAR
Hello,
This field is working as intended also. employmentPreference was built this way on purpose to return values in an array. The employeeType field is built the same way.
This field is working as intended also. employmentPreference was built this way on purpose to return values in an array. The employeeType field is built the same way.
- Tue Jul 05, 2016 10:34 am
- Forum: Bullhorn APIs
- Topic: Bug? 0 maxLength for countryCode and countryName on meta/Candidate - 02281005
- Replies: 2
- Views: 5130
Re: Bug? 0 maxLength for countryCode and countryName on meta/Candidate
Hello,
These fields are meant to return that way when searching meta because they are read only and cannot be modified via the API. This is why the maxLength returns as 0.
These fields are meant to return that way when searching meta because they are read only and cannot be modified via the API. This is why the maxLength returns as 0.
- Tue Jul 05, 2016 10:25 am
- Forum: Bullhorn APIs
- Topic: Cannot sort Note by id - 02281006
- Replies: 3
- Views: 6069
Re: Cannot sort Note by id
Hello, The sort reference field should be noteID for this to work. I did a call like below and could returned sorted results. https://rest3.bullhornstaffing.com/rest-services/xxxxx/search/Note?query=isDeleted:false AND dateAdded:[1361635821000 TO *]&fields=id&count=500&start=0&useV2=true&BhRestToken...
- Tue Jul 05, 2016 9:53 am
- Forum: Bullhorn APIs
- Topic: Bug in REST API - 02281004
- Replies: 4
- Views: 8183
Re: Bug in REST API
Hello,
The reason why this is referenced as SCALAR is because all of the fields are lumped as 1 when getting pulled from the API. By Design it functions as 1 field even though you have to set a few values within the Login Restrictions data type.
The reason why this is referenced as SCALAR is because all of the fields are lumped as 1 when getting pulled from the API. By Design it functions as 1 field even though you have to set a few values within the Login Restrictions data type.
- Tue Jul 05, 2016 9:02 am
- Forum: Bullhorn APIs
- Topic: Career Portal login transferred to REST API - 02281003
- Replies: 2
- Views: 6491
Re: Career Portal login transferred to REST API
Hey Dave,
Yes you can get this information no problem. I would just have the Bullhorn client submit a Bullhorn ticket requesting this as we need authorization from the client to provide that information to you.
Yes you can get this information no problem. I would just have the Bullhorn client submit a Bullhorn ticket requesting this as we need authorization from the client to provide that information to you.
- Wed May 18, 2016 9:00 am
- Forum: Bullhorn APIs
- Topic: Create a new Task using Rest API - 02246352
- Replies: 2
- Views: 5481
Re: Create a new Task using Rest API
Hello, Can you try capitalizing the Task you have within the request URL? I would also suggest removing the client contact ID because once the task is created you will want to perform a PUT entity to associate the task to a particular record. For example it would look something like the below: https...
- Fri Apr 08, 2016 10:01 am
- Forum: Bullhorn APIs
- Topic: I want to use the API on development server before shifting it to live.
- Replies: 1
- Views: 3659
Re: I want to use the API on development server before shifting it to live.
Hello, Are you currently working with a company that uses Bullhorn and trying to test the API within their environment? Can you let me know who the company is and what environment you are working in? If it is a test environment, you might just have to change the endpoint you are using in corresponde...