Using custom objects

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

Moderators: StaffingSupport, s.emmons, BullhornSupport

Post Reply
chuckspencer
User
Posts: 6
Joined: Fri Jul 27, 2018 12:22 pm

Using custom objects

Post by chuckspencer » Thu Sep 13, 2018 1:27 pm

We're attempting to work with Custom Objects per the instructions in this article.
http://bullhorn.github.io/Custom-Objects/

1. We may wish to use client-defined names. The article states that the Bullhorn support team must enable “Use Client Defined Name in REST” on the custom object configuration. Who can do that for us? Initially we'd be working with the Candidate Entity
2. While trying to update using static custom object and field names, we get the following response:

Code: Select all

{
    "errorMessage": "Update Failed: You do not have permission for Candidate Custom Object field customObject9s.",
    "errorMessageKey": "errors.entitlements.customObjectFieldPermission",
    "errorCode": 500,
    "entityName": "Candidate"
}
for a post to this url:
https://rest91.bullhornstaffing.com/res ... ken={valid rest token was here}

with this POST body:

Code: Select all

{
      "customObject9s":
     [
        {"text1":"Brand new custom object here!"}
     ]
}

pmularski
Bullhorn Support Staff
Posts: 900
Joined: Wed Dec 31, 1969 8:00 pm

Re: Using custom objects

Post by pmularski » Wed Sep 26, 2018 2:51 pm

Good Afternoon chuckspencer,

I wanted to touch base on this post. If you have not already had this enabled, please have your client open a ticket with Bullhorn Support. That way, we will be able to update your access directly through the client. Thanks!
Patrick Mularski
Senior Enterprise Support Analyst
B U L L H O R N
Staffing and Recruiting Software, On Target, On Demand
Bullhorn Support Contact Numbers
US: 617-478-9126
UK: 44 800 032 2848
Australia: 61 28 073 5089
International: 617-478-9131

Post Reply