Token refresh issues

Forum for users and developers of Bullhorn's API service.

Moderators: StaffingSupport, s.emmons, BullhornSupport

connectorsTray
User
Posts: 13
Joined: Wed Oct 02, 2019 8:52 am

Re: Token refresh issues

Post by connectorsTray »

Following up on this Lindsay,

It looks like when we attempt to refresh the token, we randomly get an error when hitting the refresh URL; Network error - no status code. When we again try to refresh with the same token, we then get an error message OAuth token request error: This authentication can no longer be used (invalid refresh token). Please create a new one. - 400: {"error":"invalid_grant","error_description":"Invalid, expired, or revoked refresh token."}.

I've seen other articles such as this one on refresh retries: viewtopic.php?t=23949, but this looks to be different as we cannot reattempt with the same refresh token. Is there something we're missing here?

Thanks
ggaragiola
User
Posts: 26
Joined: Wed Feb 26, 2020 12:43 pm

Re: Token refresh issues

Post by ggaragiola »

Hello,

This is Grant from Bullhorn support.

Can you try just using the following and see if you still get a refresh error:

https://auth-emea.bullhornstaffing.com
https://rest-emea.bullhornstaffing.com
https://api-emea.bullhornstaffing.com

Thank you
connectorsTray
User
Posts: 13
Joined: Wed Oct 02, 2019 8:52 am

Re: Token refresh issues

Post by connectorsTray »

Hi Grant,

We can try that URL, is that to mean that https://auth-emea9.bullhornstaffing.com is an incorrect URL? It's going to take us a couple of days to test this so I'd like some certainty around this!

Thanks
ggaragiola
User
Posts: 26
Joined: Wed Feb 26, 2020 12:43 pm

Re: Token refresh issues

Post by ggaragiola »

Hello,

This is Grant with Bullhron Support.

So I was able to get a refresh token with https://auth-emea9.bullhornstaffing.com. In order for us to really determine what is going on we are going to need the full call to determine if there is a syntax issue or if something else is occuring.

Sharing the call over the API Forum is not something I suggest so I would have Aircall submit a ticket on your behalf to our support team so we can take a closer look at your syntax and the connection to Aircall.

Thank you
DavidPena
User
Posts: 1
Joined: Tue Nov 10, 2020 11:59 pm

Re: Token refresh issues

Post by DavidPena »

JonnectorSray wrote: Sun Aug 23, 2020 12:39 am Thanks for your reply Lindsay,

I will verify with our customer that we are using the correct data centre. Do you have any documentation on using API Username + Password, is this separate to the Oauth mechanism? It would be great to understand what the flow would be for our Partner's users compared with currently where they just log in. We anticipate that it may be difficult for each of our Partner's users to request this API username + password if we understand correctly which is why Oauth may be preferable. Our use cases centre around realtime information retrieval from Bullhorn, it sounds like having a Constant Connection could be beneficial for our use case.

Let us know!
One thing you should be careful about: a refresh token is returned (in addition to the access token) only when the user gives consent explicitly for the requested scopes. Basically, when the approval page is shown. All subsequent flows will only return an access token.
Vaso
User
Posts: 9
Joined: Thu Sep 26, 2013 1:05 pm

Re: Token refresh issues

Post by Vaso »

I am planning to publish a C# .NET Core Console App to Github, including the source, which you could use for testing your Bullhorn API.

I have been developing it for years as one of my client needed to sync some data to Azure SQL Database.

You can then check in Fiddler what is wrong.
Post Reply