Search found 17 matches
- Wed Jul 17, 2013 10:41 am
- Forum: Bullhorn APIs
- Topic: Status: No response.
- Replies: 2
- Views: 6525
Status: No response.
I'm getting a 'Status: No response.' when I attempt to get my Auth code using the instructions found in Getting started with the Bullhorn REST API. Furthermore how do get my 'recommended state value'?
- Sat Jan 12, 2013 2:10 pm
- Forum: Bullhorn APIs
- Topic: Cadidate search
- Replies: 0
- Views: 6967
Cadidate search
I am trying to authenticate and get the ID of our Candidates. If I do a search in the following way: https://rest2.bullhornstaffing.com/rest-services/xxx/search/Candidate?BhRestToken=xxx&fields=*&query=isDeleted:0 I get a list of Candidates and all their associated fields. My first issue is that all...
- Thu Jan 10, 2013 1:37 pm
- Forum: Bullhorn APIs
- Topic: Country Name
- Replies: 4
- Views: 10483
Re: Country Name
Hi Soniya,
Thank you for that list. I assume then that there is no way to pull the Country Name for a Job Order while doing at query.
John
Thank you for that list. I assume then that there is no way to pull the Country Name for a Job Order while doing at query.
John
- Thu Jan 10, 2013 11:33 am
- Forum: Bullhorn APIs
- Topic: Country Name
- Replies: 4
- Views: 10483
Country Name
I'm using the query operation on the JobOrder entity and I would like to know if anyone knows of a way to get the Country Name String for the countryID?
- Thu Jan 10, 2013 11:30 am
- Forum: Bullhorn APIs
- Topic: Getting started
- Replies: 11
- Views: 20328
Re: Getting started
Hi Jason, I went through urlenconding parameters and it was not always so successful. The one thing that I figured out is that spaces absolutely need to be urlencoded. Therefore You might have to play around with the the special characters in the value for $query. I understand that it will be dynami...
- Mon Jan 07, 2013 4:05 pm
- Forum: Bullhorn APIs
- Topic: Getting started
- Replies: 11
- Views: 20328
Re: Getting started
Okay so I'm getting results through my application and the following is what I figured out. Despite what the documentation examples say it looks like all spaces have to be URL encoded therefore the following works: https://rest2.bullhornstaffing.com/rest-services/[corporation_key]/query/JobOrder?BhR...
- Sun Jan 06, 2013 9:22 pm
- Forum: Bullhorn APIs
- Topic: Getting started
- Replies: 11
- Views: 20328
Re: Getting started
So I'm having the best success with the query operation. When I plug my URL in the Google Chrome extension 'Simple REST Client' the query works just fine. When I take the same URL and plug it into my PHP script I get an error that the 'fields' parameter is missing. I am attempting to write a Drupal ...
- Fri Jan 04, 2013 2:22 pm
- Forum: Bullhorn APIs
- Topic: Getting started
- Replies: 11
- Views: 20328
Re: Getting started
I am getting more results using the query operation than the entity. Still not sure if this is the best approach but at least I am getting some results. There are what seem to be some mistakes in the Documentation (BullhornRESTAPI.pdf). 1. On page 29, under 'Required' in the 'where' row the link 'Qu...
- Fri Jan 04, 2013 1:48 pm
- Forum: Bullhorn APIs
- Topic: Getting started
- Replies: 11
- Views: 20328
Re: Getting started
So I've decided to try the API entity operation to get all the jobs. With my corporation_token and my session_key I make the following GET request https://rest2.bullhornstaffing.com/rest-services/[corporation_token]/entity/JobOrder?BhRestToken=[session_key]&fields=* And I receive the following respo...
- Fri Jan 04, 2013 12:16 pm
- Forum: Bullhorn APIs
- Topic: Getting started
- Replies: 11
- Views: 20328
Getting started
Hello, I'm just getting started with using Bullhorn's REST API and I'd like to get the opinion of experienced users what they consider the best approach. To start with my client used the HTTP method previously and the most common things they did via their website are: display all jobs and allow cand...
- Fri Jan 04, 2013 11:20 am
- Forum: Bullhorn APIs
- Topic: error: invalid_client
- Replies: 15
- Views: 29989
Re: error: invalid_client
Omitting the redirect_uri from the the Auth Code step resolved this error.
Thank you Ryan and c.choy for your assistance.
I have a few more questions but will start a new thread for them.
Thank you Ryan and c.choy for your assistance.
I have a few more questions but will start a new thread for them.
- Thu Jan 03, 2013 5:08 pm
- Forum: Bullhorn APIs
- Topic: error: invalid_client
- Replies: 15
- Views: 29989
Re: error: invalid_client
c.choy, thank you for your assistance. I haven't been forwarded your response to the ticket, however I believe that I understood what you meant and which character needed to be altered. However, after renewing my auth_code I get the following error when trying to use it to obtain my access_token: { ...
- Wed Jan 02, 2013 2:48 pm
- Forum: Bullhorn APIs
- Topic: error: invalid_client
- Replies: 15
- Views: 29989
Re: error: invalid_client
Hi Ryan, Yes, Happy New Year to you too! I think I failed to communicate in my last post what was actually happening to me. I do get a different Auth code every time I go to https://auth.bullhornstaffing.com/oauth/authorize?client_id=[client_id]&response_type=code&redirect_uri=[optional redirect_uri...
- Tue Jan 01, 2013 5:04 pm
- Forum: Bullhorn APIs
- Topic: error: invalid_client
- Replies: 15
- Views: 29989
Re: error: invalid_client
Hi Ryan,
It's a very busy time of the year, I totally understand. Thank you for getting back to me.
I tried a couple of times to get a new auth code and always get the same result. Is what you used something totally different?
Thanks,
John
It's a very busy time of the year, I totally understand. Thank you for getting back to me.
I tried a couple of times to get a new auth code and always get the same result. Is what you used something totally different?
Thanks,
John
- Fri Dec 28, 2012 3:32 pm
- Forum: Bullhorn APIs
- Topic: error: invalid_client
- Replies: 15
- Views: 29989
Re: error: invalid_client
Hi Ryan,
I've emailed the details that you requested.
Thanks again,
John
I've emailed the details that you requested.
Thanks again,
John