So, here's what I'm envisioning.... please let me know if this is the right approach.
When our page loads in the iframe, according to the guide linked above, it looks like bullhorn will use a link with the user's credentials from our side so we can identify who they are. Our system should look to see if we have an access token and refresh token saved for them. If so, get a new access token with the refresh token and assuming that all works fine, present them with the screen where they can start selecting their data.
If we don't have anything stored for them for tokens, we need to present them with a login page where they provide their bullhorn credentials and then we start the authorization process as outlined here - http://bullhorn.github.io/Getting-Started-with-REST/
Is that all correct? Thanks.
This is Grant from Bullhorn Support.
This all sounds correct to me. If you run into any issues please reach out to our support team who could provide you with a client ID and secret and add redirect URI's.
Support Phone Numbers:
Bullhorn Support US: 617-478-9126
Bullhorn Support UK: 44 (0)800 131 0842
Bullhorn Support Australia: 61 28 073 5089
Bullhorn Support International: 617-478-9131
On the rest api page it says "Bullhorn customers can obtain OAuth keys for developing applications with the Bullhorn REST API by creating a support ticket via the Bullhorn Resource Center." I'm not exactly sure where this resource center is. From within bullhorn I tried going to Menu>Resources>Contact Support but when I do I get redirected to an sso error page - https://help.bullhorn.com/s/ssoerror Can you give me anymore information on getting this set up so I can work on setting up the oath authorization? Thank you.