Token expiration not what the docs say....

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

Moderators: StaffingSupport, s.emmons, BullhornSupport

Post Reply
MojoNixon
User
Posts: 2
Joined: Sun Apr 14, 2013 7:11 pm

Token expiration not what the docs say....

Post by MojoNixon » Mon Jul 01, 2013 6:44 pm

I am trying to understand token expiration on Bullhorn. The docs say that token's expire in 10 mins.

When I do a GET / ping .. Bullhorn returns a sessionExpires that is 30 mins away from the last query/ping. By the way.. the docs says that the PING returns unix time.. but I have to truncate the last 3 digits to get it to convert to proper UNIX time

so.. it appears that the token will expire 30 mins after the last request on the session.

Has anyone else noticed this?

Thanks

s.potnis
User
Posts: 16
Joined: Wed Dec 31, 1969 8:00 pm

Re: Token expiration not what the docs say....

Post by s.potnis » Mon Jul 08, 2013 11:12 am

Hello MojoNixon,

Is this only occuring when you do a GET call?

Thanks,
Soniya Potnis
Enterprise Support Analyst

mpeterson
User
Posts: 5
Joined: Fri Aug 16, 2013 8:18 am

Re: Token expiration not what the docs say....

Post by mpeterson » Fri Aug 16, 2013 8:20 am

The session token expires in 10 minutes. That means you need to use it to get a session within 10 minutes. The actual session defaults to 30 minutes but you can set that to a different value with the ttl (time to live) query parameter.

Post Reply