Hi, One of our common end users reached out to us with a problem. It turns out that we were not syncing all his Bullhorn contacts. We investigated this in depth and it turns out that the issue is that your API returns us resource pages with a size lower than the requested one, whilst there are in fa...

Dave,

Thanks for your feedback.

It would be great if you could indeed submit this as a feature request internally.

Thanks in advance.
Kind regards,
Wout

Hi there,

This was exactly what we needed, thanks for the quick feedback!

Kind regards,
Wout

Thanks for the quick feedback.
This indeed seems to be exactly what we were looking for!

Hi, At the moment we can only set the country by using the technical ID of that country. This in essence is fine, but in the case of high-volume API integration this is not that efficient. More specifically It will mean that - in order for us to be sure that we're always providing a valid country - ...

Hi, I've seen in another post that your API usage limits are documented here: http://bullhorn.force.com/pkb/articles/Documentation/Understanding-Bullhorn-API-Usage-Limits-Versioning-and-Backward-Compatibility. I had a look at this document, but I would still have some questions. We are looking to of...

We see that we are able to list all the end user's fields using your API (for instance for Contacts we use https://rest91.bullhornstaffing.com/rest-services/4tfxcg/meta/ClientContact). However this endpoint doesn't show us which fields are marked as "Hidden" in the Field Mappings admin. We are an in...

Hi, I have 2 questions about these rate limits: 1) I see that there are limitations on the concurrent API sessions and maximum number of API subscriptions. I assume these only on the level of the account and do not apply to the OAuth application itself? As in: can a certain integrator's OAuth applic...