Lindsay,
Thanks for the follow up and I will hope for the addition to the roadmap in the future.

Lindsay,
I know we can update that field directly through the Bullhorn SOAP API's. It's just cumbersome to have to use separate APIs and Credentials just to update this one field. Is it on the roadmap to allow for the update of the smsOptIn field via REST.

When trying to update the Candidate (and most likely Contact and Lead) smsOptIn field I receive the following error. "errorMessage": "Unable to perform action due to missing entitlement for property smsOptIn", "errorMessageKey": "errors.entitlements.missingActionEntitlement", "errorCode": 403 Which ...

Laura, Thanks for the reply and in the case of Categories there is definitely the potential for it to be a "To-many" relationship. On the lead record there is a purposed field for Client Corporation ID since there can only be one. However, with a Contact it is a "To-many" relationship even though th...

I am looking to understand why the Lead to Contact and Contact to Lead association is a "To-many" relationship in the Bullhorn API. It does not seem possible to create multiple contacts to one lead, nor multiple leads to one contact (Same for Candidates) through the Bullhorn User interface (or throu...