Hi DenSter,

Glad that worked for you! I will definitely pass that feedback along to our team who handles documentation for API.

Please let us know if you have any other questions.

Thank you.

Hi DenSter, Are you running your auth call in Postman? You should see the code under the "Headers" within the "Location" output. Additionally, if you are running the call in Postman, be sure that you have the setting "Automatically Follow Redirects" set to "Off". If neither of the above resolves the...

Hi jordstew, There are some limitations around how many results will be returned when you include to-many association fields, and there's a separate limit to how many association entities will be returned. The default on that is 5 and you can request a max of 10 (http://bullhorn.github.io/rest-api-d...

Hi haleymarketingtest, Are you including the ClientContact record ID in your call? It should look something like this: entity/ClientContact/16689?BhRestToken=xxxxx And the body: { "email":"test2@Test071416.com", "firstName": "Testee" } Can you try your call again being sure to include the ID and let...

Hi Aaron, You should be able to pull notes using the following query: search/Note?fields=id,comments&query=note.action={'Left Message'} AND commentingPerson:16579&count=200&start=0 with your action and user ID input in place of what I have here, along with the fields you'd like returned. Can you try...

Hi happyrecruiter,

The / after "myCandidates" looks to be causing the error. Can you try running https://rest91.bullhornstaffing.com/res ... tToken=XXX and let me know if that call works for you?

Thank you.

Hi Mitul,

Can you provide an example (or examples) of the call you're making so I can take a closer look into what may be causing the errors?

Thank you.

Hi Leonardo,

PlacementRateCard is currently not an entity that is accessible via API. To access rate cards and the earn codes associated with them, you'll need to log into Bullhorn directly.

Should this change in the future, our team will be sure to send out an update.

Thank you.

Hi there,

Do you know what this field's name is in Field Mappings (not the label name)? I've attached a screenshot for reference.

Thank you.

-Laura

Hi Kaetlynne,

The best way to do this would be to use the Advanced Criteria Search to include any letter of the alphabet using wildcards (a* b* c*, etc). This should remove any candidates that do not have values in those fields.

-Laura

Hi Michael, Yes, it is possible to make an API call to retrieve all candidates. It would look something like this: search/Candidate?query=isDeleted:0&fields=id,firstName,lastName,email,phone,status&sort=id&count=500&start=1 The call would be dependent on the fields you're pulling for candidates as w...

Hi team, #1 is possible - once the JobOrder is created, the custom object could be modified via API. #2 and #3 would not be possible without a paid customization by our Professional Services team to modify the submission form as it is hard-coded. A customization may also be needed to automatically p...

Hi Jason,

There can only be one Contact or Candidate per Lead and vice versa. It isn't possible via the API or the UI to have more than one in either direction.

-Laura

Hello,

I would recommend submitting this as a ticket to Bullhorn support for further assistance (or having an admin user do so on your behalf), especially if the extension is related to Outlook/Gmail. Our support team would be best equipped to handle resolving this issue for you.

-Laura

Hi Jason, Although it is a To-Many, this only has to do with the array being displayed and saved in REST. The database fields exist as a single value. Much like if the categoryID field was limited to a single value (which can be done in Field Maps), it would still be a To-Many association and an arr...