When working with data, you will invariably run in to errors. The Bullhorn REST API is no different. API’s can be quite unforgiving and require data to be handled in very specific ways. For example, if the Bullhorn field is a numeric field, i.e. expects a number only, trying to save letters or characters to this field will generate an error.
That’s easy you might think, just ensure only numbers are passed to the field. When we initially set up our Bullhorn Plugin and other Bullhorn Integrations that is exactly what we do. The data passed is in the perfect format, however, what happens if in a years time you change the field slightly within Field Mapping. This field change may break integrations you may have that communicate with this field.
There are lots of other reasons for error within the Bullhorn API, maybe we are passing too many characters to a field, the field lacks permission, the field is of a wrong data type, the values expected have been changed, the API has detected a traffic spike, the access token has expired, the list goes on.
Imagine a registration form on your website, that spans multiple pages communicating with 100 fields within Bullhorn (yes, we have created many forms that large for customers). Our client comes to us one day stating that their form has stopped working. Our first response; “have you changed any fields?”, sometimes they know at that point immediately what has happened and we can update our code quickly and easily to reflect this change. Other times however, another team member has made a change somewhere and not alerted anyone.
To find the error, we would have to go through each field one by one to see where the error lies. That can be a slow and painful process.
Up steps our Bullhorn REST API Error Management. Our WordPress Plugin will do the hard work for us and save a message explaining what has caused the error. We can then either go back to the client or make a quick code change and the form is up and running again.
You know us by now, we didn’t just stop there. Our Bullhorn to WordPress Plugin and other Bullhorn Products are able to recognise certain error messages and respond to them immediately. Has the token expired? Generate a new one. Has the API paused traffic due to a traffic spike detection? Wait a few seconds then continue running the script again.
Not only are our Bullhorn solutions awesome from the outset, we ensure that everything continues to work smoothly going forwards. If you need any of our services, get in touch with us.
