Hi there, I can confirm that we do require OAuth and system level access is not allowed. There are a few different ways of authenticating. One is REST-backed custom components: http://bullhorn.github.io/REST-Backed-Custom-Components/. Also, in your Login call, if you don't want to store the username...

Hi there,

We do require updated access tokens and it is not possible to use permanent authorization. I recommend taking a look at http://bullhorn.github.io/Getting-Started-with-REST/ and utilizing a refresh token to generate a new access token.

Hi there,

API usernames are not to be used to login to the Bullhorn UI. For more information about using and formatting API calls please see this information: http://bullhorn.github.io/rest-api-docs/.

Hi Adam,

The best way to accomplish this would be to match the Value List of this field to your site, and then have the site send us the value that was selected so we can insert that into the record.

You can use the layout to grab the settings against a respective entity for example see this call below: GET rest-services/[redacted]/meta/JobOrder?layout=ListRow&BhRestToken[redacted] For example if you ran: rest-services/[redactred]/meta/Candidate?fields=* The "names" pulled back can be inserted i...

Hi Amir,

For this issue I recommend creating a support ticket due to the complex and detailed nature of the issue. If you are not an Account/Support Contact, please have one create a ticket for you and they can provide your contact info and permission to work with you.

Hi Patrick, This issue is due to trying to return too much data due to the to-many fields as the error suggests. We have a hard limit in REST of returning 200 to-many associations per call. When you include three or more to-many fields we restrict the return based on the number of to-many fields req...

Dear Team, I am trying to extract Candidate ID field from the entity Placement. Below is the API used, https://rest99.bullhornstaffing.com/rest-services/rzro1/search/Placement?fields=id,candidate(id),dateAdded&BhRestToken=387e3166-66ba-454d-ba9f-69ecfc6dfc85 {"query": "id:19884"} Result: { "total":...

Note: Other than for /meta/{entityType}, the fields=* syntax is now deprecated because of negative performance impact. Calls using this syntax will be blocked . Many of our systems integrations depend on this call. When can we expect these calls to be blocked? This is expected to be in place by 12/...

Currentl we are using meta API with param "fields=*" for getting property of metatype (curl https://rest.bullhornstaffing.com/rest-services/e999/meta/Candidate?fields=*). now bullhorn restrict * value for getting all fields. Is there any API for getting all field in entity. There is not. Field=* wi...

When a Lead is converted to a Contact, the Lead's status is updated to "Converted". If you have an event subscription configured to look for Lead updates then you just need to look for the status updating to Converted and can work off that.

This will only affect fields=*

Hi Bharath,

Our API uses epoch format (with milliseconds). The following website is useful for obtaining dates in this format: https://currentmillis.com/. This should allow you to successfully encode/decode your API calls and results.

Hello,

Integer fields in Bullhorn can only contain numerals. Anything other than an integer will be disregarded and not saved.