Search found 42 matches

by DanJSupport
Mon Feb 11, 2019 9:45 am
Forum: Bullhorn APIs
Topic: OpportunityHistory vs OpportunityEditHistory
Replies: 3
Views: 2817

Re: OpportunityHistory vs OpportunityEditHistory

Hi Ivan, Could you explain what you mean? The values for Status should be the same as what is in the history. It's possible that there are some statuses that may have been removed from the field mapping by an Admin, or an API added a different status than is available to users in the App, but for th...
by DanJSupport
Tue Feb 05, 2019 2:16 pm
Forum: Bullhorn APIs
Topic: Query/Search File Attachments
Replies: 1
Views: 1672

Re: Query/Search File Attachments

Hi henryzhao, You are able to use GET /entityFiles to retrieve files associated with a particular record. More information can be found here: http://bullhorn.github.io/rest-api-docs/index.html#file You can also use an entity search to find records by file attachment descriptions like this: /search/C...
by DanJSupport
Tue Feb 05, 2019 1:59 pm
Forum: Bullhorn APIs
Topic: Bullhorn Screen Pop Integration
Replies: 1
Views: 1664

Re: Bullhorn Screen Pop Integration

Hi spencscott, The Open Window links are really only designed to open a record by ID. What you would need to do is have a GET/Search for the phone number to retrieve the ID and then use the result to generate an Open Window link. For example: GET /search/ClientContact?query=mobile:1234567890&&fields...
by DanJSupport
Tue Feb 05, 2019 1:37 pm
Forum: Bullhorn APIs
Topic: Problem with Merging Candidates
Replies: 1
Views: 1577

Re: Problem with Merging Candidates

Hi hnmsystems,

The custom import tool in Bullhorn is not designed to update existing records. You can however do this with REST by first querying the name or other identifying detail of the candidate with a GET /search call then updating the email with a POST /entity call.
by DanJSupport
Tue Feb 05, 2019 1:32 pm
Forum: Bullhorn APIs
Topic: How to request access to the Web Developer API
Replies: 1
Views: 1587

Re: How to request access to the Web Developer API

Hi andyyoung88,

This can be requested by an Account or Support Contact by opening a ticket with Bullhorn Support.
by DanJSupport
Tue Feb 05, 2019 1:31 pm
Forum: Bullhorn APIs
Topic: Where to i will get this redirect_uri client_id client_secret Password
Replies: 1
Views: 1593

Re: Where to i will get this redirect_uri client_id client_secret Password

Hi shital1994,

This can be requested by an Account or Support Contact by opening a ticket with Bullhorn Support.
by DanJSupport
Tue Feb 05, 2019 1:30 pm
Forum: Bullhorn APIs
Topic: Emailing candidates
Replies: 1
Views: 1527

Re: Emailing candidates

Hi Erezarnon,

I'm not sure what you are trying to accomplish. If the email integration is setup (https://help.bullhorn.com/s/topic/0TO0P ... tion-setup) users will be able to see the emails on the records.
by DanJSupport
Tue Feb 05, 2019 1:20 pm
Forum: Bullhorn APIs
Topic: Client IDs
Replies: 1
Views: 1542

Re: Client IDs

Hi David,

We recommend using separate Client ID and Client Secret pairs for each integration. So it would be best for each client to have their own Client ID and Client Secret.
by DanJSupport
Tue Feb 05, 2019 1:04 pm
Forum: Bullhorn APIs
Topic: Candidates Counter
Replies: 1
Views: 1543

Re: Candidates Counter

Hi EngineerX

The most common way to get all the records would be to search on the isDeleted field. For candidates that would look like this:

Code: Select all

GET /search/Candidate?query=isDeleted:0&fields=id&BhRestToken={token}
The response will include a total which is what you're looking for.
by DanJSupport
Tue Feb 05, 2019 12:58 pm
Forum: Bullhorn APIs
Topic: OpportunityHistory vs OpportunityEditHistory
Replies: 3
Views: 2817

Re: OpportunityHistory vs OpportunityEditHistory

Hi Ivan, The OpportunityHistory corresponds to the Status History section in the Opportunity's Activity Tab. It is a tracking of a few key fields such as the status, deal value, win probability and effective date. The OpportunityEditHistory and OpportunityEditHistoryFieldChange correspond to the ful...
by DanJSupport
Fri Dec 21, 2018 11:55 am
Forum: Bullhorn APIs
Topic: Candidates information
Replies: 1
Views: 3499

Re: Candidates information

Hi Tanquoc0309, You could do this with a GET /search call like this: /search/Candidate?query=isDeleted:0&fields=*&start=0&count=100&sort=id&BhRestToken={BhRestToken} However that is pretty inefficient. If you need all of the data from the candidates, a better option would be to request a standard ba...
by DanJSupport
Fri Dec 21, 2018 11:45 am
Forum: Bullhorn APIs
Topic: Unable to get job orders via postman
Replies: 1
Views: 3541

Re: Unable to get job orders via postman

Hi John,

See my reply on your other post: http://supportforums.bullhorn.com/viewt ... 04&t=30452
by DanJSupport
Fri Dec 21, 2018 11:32 am
Forum: Bullhorn APIs
Topic: ResponseUser not populating on CreateJob Order
Replies: 1
Views: 3463

Re: ResponseUser not populating on CreateJob Order

Hi Teberle, Your call looks correct. It's possible that the field mappings within Bullhorn are not setup to display that field correctly. The responseUser field may be hidden or set to an incorrect edit type (it should be set to Picker:Internal). I suggest you reach out to Bullhorn Support to assist...
by DanJSupport
Fri Dec 21, 2018 11:24 am
Forum: Bullhorn APIs
Topic: Unable to get job order via the rest api
Replies: 1
Views: 3543

Re: Unable to get job order via the rest api

Hi John, Before you can make calls into Bullhorn you will need to use the access token to generate a BhRestToken. This documentation explains the authorization process: http://bullhorn.github.io/Getting-Started-with-REST/ Your call is also missing the corp token. When making the call to obtain the B...
by DanJSupport
Fri Dec 21, 2018 11:18 am
Forum: Bullhorn APIs
Topic: ATTEMPT_TO_SET_TO_MANY on AssignedUsers for Job Order Creation
Replies: 1
Views: 4090

Re: ATTEMPT_TO_SET_TO_MANY on AssignedUsers for Job Order Creation

Hi Teberle, The To-Many association fields need to be created after the job is created with a PUT call like this: https://rest34.bullhornstaffing.com/rest-services/{corp_token}/entity/JobOrder/{jobID}/assignedUsers/{userID} See our documentation on PUT Entity: http://bullhorn.github.io/rest-api-docs...