Authenticating Bullhorn public API for jobs

[openupmedia]

Hi,

We are working on an integration for a client. We need to display jobs on their website. It seems that the Bullhorn public API for jobs allows for a simpler rea-only access to job data, without the use of oauth2 authorization, but with the use of a {cls} and {corptoken} value.

We received {cls} and {corptoken} values through the helpdesk, but when we receive 401 response errors when trying to GET https://public-rest{cls}.bullhornstaffing.com/rest-services/{corp token}/search/JobOrder?query=(isOpen:1)&fields=id,title,publishedCategory(id,name),address(city,state),employmentType,dateLastPublished,publicDescription&count=20&sort=-dateLastPublished&start=0

The Helpdesk team member couldn't answer our questions, and suggested that we post them here...

Are we mistaken and does the public api also requires an Oauth2 authorization or something? Or does support still need to activate somthing for the client account?

Thanks,
Tijs

[wRollins]

HI,

Public rest does not require authentication, but only Open AND published Jobs can be returned. Also, there is field limitation to which fields can be accessed. You can add or remove fields with the help of Bullhorn supports via the PLA "publicRESTJobAPIFieldList" . The only Fields that can be added are listed here: http://bullhorn.github.io/rest-api-docs ... bboardpost
We have a doc for public Rest available here for "more" information:
https://bullhorn.github.io/Public-API/
The public API also supports the candidate application process for published jobs. After the set of published jobs is retrieved, candidate applications, also known as web responses, can be sent back to Bullhorn.

[ournalleading]

The Helpdesk agent was stumped and recommended we ask our queries online. Is it just us, or does the public apiphrazle need Oauth2 authentication too? Or is there anything that has to be activated in the client's account by support?

[wRollins]

There are only specific fields and jobs that can be returned through public API. This is mainly used for Job Posting and should only be used to publish those postings. The public API will have a particular BH Support Only user and should have an Admin Level UserType permission to work correctly. Only BH support is able to set this user and usertype on your corporation settings.

[openupmedia]

We didn't get this working either. According to the documentation and the first reply there shouldn't be any authentication required, but in the last comment you mention that you do need a specific user and that only support can create this...
BH support send us to this forum to get support, as the had no idea about this...

Even if we would have a user account, the docs don't mention anything detailed about an authentication.

Our client has multiple special users for the full API connection, used on their old sit. So we ended up implementing that API again instead of waiting to get the public API working...

This has been a very frustrating search imo, the public API for jobs was exactly what we needed and should have been easier to implement...

[felixandrea]

Although Bullhorn has a public API that does not require OAuth2 authentication, some specific configuration may still be needed before starting use.
Some points to note:
Authenticate with {cls} and {corptoken}: You received these values from support, but they still don't seem to work. Additional rice purity test configuration or activation steps may be required on Bullhorn's part for these values to be used.
Error 401 Unauthorized: This error means you are not authenticated to access the resource. This could be because the {cls} and {corptoken} values are not configured correctly or additional authentication factors are needed.

[agelababypp]

All Bullhorn candidate and job records are synchronized with Textkernel.

[Diamondd]

You can try testing the API endpoint from a different network or using a tool like Postman to rule out any network-related issues.

[Dustin]

The Bullhorn public API should not require OAuth2 authorization if {cls} and {corptoken} are configured correctly. However, 401 errors often indicate an issue with permissions or an inactive API configuration for the client account. I recommend confirming with support whether the public API access is fully enabled for your client.

Stick War Legacy

[openupmedia]

That was our reasoning too, but support was useless when we asked about this... One didn't know the public API existed, and another said that we needed to ask for this via the forums

[pmularski]

Greetings Openupmedia,

I apologize for the ambiguity from the team. Were you able to complete your configuration? If not, what step are you stuck on? This is a bit of an old thread, so I'm not sure if this is still up in the air for you.

[openupmedia]

Hi pmularski,

We ended up implementing the full API again.

[pmularski]

Thanks for letting me know openupmedia. Again, I'm sorry for the incorrect information from the team.

[openupmedia]

Thanks for letting me know openupmedia. Again, I'm sorry for the incorrect information from the team.

No worries