Technical Requirements for Developer’s Use of the Bullhorn API:
- Unless granted specific permission, Developer’s applications must use the latest version of the Bullhorn web services APIs for accessing Bullhorn data and the documented methods for building custom components and UI extensions. Documentation is located on the Bullhorn website at: http://developer.bullhorn.com/documentation
- Each Developer application or product must use a unique partner API key provided by Bullhorn. This will enable Bullhorn Customers to control use of each Developer application individually.
- All requests for data should be performed over a secure network connection (HTTPS). Certificates are available from Bullhorn for installation on Partner servers.
End User documentation
- Customer documentation must list any custom components or other UI extensions that must be configured by an administrator, including instructions on how to complete the necessary configuration steps in Bullhorn.
- Customer documentation must list all client configuration requirements, including browser settings, required plug-ins, and browser or operating system restrictions.
- Customer documentation must clearly communicate how the Integrated Partner Service makes use of the data stored in Bullhorn, including specific documentation regarding persistence or transmission of data from the Bullhorn system to an external system or database.
Developer Integration Enablement Requirements
The Bullhorn Developer Integration Enablement process is put in place to facilitate a seamless activation for Bullhorn Customers. Developer agrees to follow the process below to have the Integrated Developer Service provided to Bullhorn Customers for use by the Users:
- Developer will be provided a Bullhorn Test Server to develop against. Developer will develop the solution, leveraging Bullhorn technical resources such as developer forums, open source documentation, and going through a technical validation process. Developer will independently research and configure workflows and use cases. In cases where custom redirect URIs, or issues with the Bullhorn Sandbox, Developer will contact its respective Partner Manager for assistance.
- Once the Developer Integrated Service is built, tested and commercially functional, and free of known bugs, Developer will notify the Bullhorn alliances department.
- Developer will provide Bullhorn with the following information contained within a Developer Validation document:
- Test Server details, including login information
- Set-up instructions to add the Developer Integrated Service into the Bullhorn environment
- Functional description of Developer Integrated Service
- Detailed information on how Developer is leveraging the Bullhorn APIs
Support
Developer will be provided with resources and documentation to use in the process of building and maintaining the integrated service. Limited support may be available depending on the nature of the support need. Developer can open a ticket by completing the form at https://help.bullhorn.com/bhcomm/s/devhfbhform. Developer does not, and shall not, have direct access to Bullhorn support services or development teams, except as otherwise mutually agreed by Bullhorn, in writing.
Bullhorn Branding Guidelines:
Bullhorn and Developer agree to Bullhorns Branding Guidelines:
- Any marketing or sales campaigns that use the Bullhorn name, brand, or logos in any form, must have the express written approval of Bullhorn alliances and marketing in advance of use. Similarly, any press releases and public announcements or claims of partnership with Bullhorn are not permitted without the express written approval the Bullhorn alliances and marketing teams.
- Developer must always market their product using their own proprietary product name and never include the Bullhorn brand in that name. If a Developer’s product is integrated with Bullhorn, through the Bullhorn API, the developer may state their solution is integrated with Bullhorn. Notwithstanding the foregoing, Developer shall not be permitted to contribute to Bullhorn customer or staffing blogs; nor shall Developer be permitted to sponsor Engage conferences.
- Any Developer marketing that uses a Bullhorn trademark must give proper attribution of that trademark by acknowledging Bullhorn’s ownership of the trademark. This attribution must be visibly placed on a trademark page or at the bottom of the page where the trademark is being used.
- In using any kind of Bullhorn trademark in any type of marketing, in print or electronically, Developer must get prior written approval from Bullhorn.
- The Developer must use standard trademark guidelines when using a Bullhorn trademark. These include but are not limited to never using a Bullhorn trademark as an adjective or in the possessive form.
- When available, Developer may use a Bullhorn designated logo to signify their application’s inclusion on the Bullhorn.com or Bullhorn Marketplace Web sites.
- Any free product or service or free trial is subject to Bullhorn’s written authorization.
Bullhorn reserves the right, in its sole discretion, to modify the terms and conditions of this Section (d) at any time and for any reason, upon thirty (30) days’ notice to Partner.
Marketing & Sales Enablement Document Obligations
Developer agrees to provide to Bullhorn, at minimum the following:
- Partner logo
- Partner company description
- Integrated Developer Service description
- Integrated Developer Service screenshots and/or online video
- Developer support details including a phone number and email address
- Contact for leads
Each such document will be subject to the mutual agreement of the Parties.
Data & research
