Page 1 of 1

Is email a required/reliable field for Bullhorn Users

Posted: Wed Aug 15, 2018 5:27 pm
by chuckspencer
We're developing a marketplace integration that will entail creating user accounts in our system based on the result of the GET /settings endpoint in the Bullhorn REST api (http://bullhorn.github.io/rest-api-docs/#get-settings). Can we count on the 'email' field in that result to be populated for all users? Is that email required for all Bullhorn corporate users? Is it subject to change?

Re: Is email a required/reliable field for Bullhorn Users

Posted: Tue Aug 28, 2018 9:19 am
by dportnoyBH
Hi Chuck,

This is Dave with Bullhorn's API Support Team, and I will be assisting you with your inquiry into the requirement of the email field for a Bullhorn user.

An email address is not required, unless the client has email integration set up and the new user will need to track emails. At that point, the In-Bound Email setting on the user profile should be enabled. This is not typically the case if you are enabling API users, but is common if you are to set up standard Bullhorn users.

Hopefully this provides the insight you need, but please let us know if you need anything else.