Skip to main content

​
Overview

The StackOne Salesforce-Bullhorn integration leverages Salesforce’s REST API and SOQL queries to provide unified access to Bullhorn data. This guide covers the technical implementation details for integration partners.

​
API Architecture

The integration uses Salesforce’s REST API and SOQL queries to retrieve and manipulate data from Bullhorn instances running on Salesforce.

​
Custom Fields

Custom fields are supported for the Application, Candidate, and Job models.

​
Account-Specific Custom Fields

When connecting a Bullhorn account, customers can specify which model fields they wish to include as custom fields in their Account connection screen.
Salesforce Bullhorn Custom Fields Account Configuration

​
Unified Custom Fields

Request additional fields for unified custom fields (not account-specific) using the proxy[fields] query parameter: 
curl -X GET "https://api.stackone.com/unified/ats/candidates" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  "proxy[fields]=TR1__Reject_Action__c,TR1__Submit_And_Email_Action__c"
Example fields:
  • TR1__Reject_Action__c
  • TR1__Submit_And_Email_Action__c

​
Custom Filtering

Apply additional SOQL filters using the proxy[filter] query parameter: 
curl -X GET "https://api.stackone.com/unified/ats/applications" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  "proxy[filter]=ai_Job_Match_Score__c >= 3"
This enables filtering on custom fields and additional data points beyond the standard unified API capabilities.

​
Applications

The integration supports two application types:

​
Application Types

  1. TR1__Application__c - Shortlist Application
  2. TR1__Job_Board_Application__c - Job Board Application
Applications queries will include both TR1__Application__c and TR1__Job_Board_Application__c models by default.
To only include Applications of the TR1__Job_Board_Application__c type, set the filter[stage] parameter to “null”.

​
Moving Applications

Convert a Job Board Application to a Shortlist Application using the move endpoint: Endpoint: PATCH /ats/applications/:id/move Request: 
{
  "interview_stage_id": "Application"
}
This operation:
  • Creates a new TR1__Application__c record
  • Returns the new record’s ID
  • Updates the TR1__ATS_Stage__c field Only Job Board Applications (TR1__Job_Board_Application__c) can be moved to Shortlist Applications. The interview_stage_id value must be set to “Application”. Other TR1__Application__c records can also be moved using this endpoint, but the behavior is restricted.

​
Passthrough Support

The passthrough property is supported for:
  • Application Move endpoint (PATCH /ats/applications/:id/move)
  • Application Update endpoint (PATCH /ats/applications/:id)
Use the passthrough parameter to update additional Salesforce properties not covered by the unified API: 
{
  "interview_stage_id": "Application",
  "passthrough": {
    "Custom_Field__c": "value",
    "Another_Field__c": 123
  }
}

​
Best Practices

  1. Test custom fields before implementing in production to ensure the field names are correct
  2. Validate SOQL filter syntax using the proxy[filter] parameter against Salesforce documentation
  3. Handle errors gracefully when moving applications - not all application types support this operation