1
Integration
28
Endpoints
Available integrations
Bullhorn
List candidates
List job orders
Create a new candidate
Create a new job order
Obtain access token
Create Candidate
Creates a new Candidate using Bullhorn `PUT /entity/Candidate` semantics.
Create ClientContact
Creates a new ClientContact using Bullhorn `PUT /entity/ClientContact` semantics.
Create ClientCorporation
Creates a new ClientCorporation (company) using Bullhorn `PUT /entity/ClientCorporation` semantics.
Create JobOrder
Creates a new JobOrder using Bullhorn `PUT /entity/JobOrder` semantics.
Delete Candidate
Hard or soft deletes a Candidate using Bullhorn `DELETE /entity/Candidate/{entityId}`. Behaviour depends on entity configuration.
Delete ClientContact
Hard or soft deletes a ClientContact using Bullhorn `DELETE /entity/ClientContact/{entityId}`. Behaviour depends on entity configuration.
Delete ClientCorporation
Hard or soft deletes a ClientCorporation using Bullhorn `DELETE /entity/ClientCorporation/{entityId}`. Note that ClientCorporation is listed as immutable for hard delete in official docs, so behaviour may be restricted.
Delete JobOrder
Hard or soft deletes a JobOrder using Bullhorn `DELETE /entity/JobOrder/{entityId}`. Behaviour depends on entity configuration.
GET Options
GET Countries
Pull the list of Countries supported in Bullhorn
Get Settings
Get States
retrieve BH address States from the api
Get Candidate by ID
Gets one or more Candidates by ID using Bullhorn `GET /entity/Candidate/{entityId}` semantics.
Get ClientContact by ID
Gets one or more ClientContacts by ID using Bullhorn `GET /entity/ClientContact/{entityId}` semantics.
Get ClientCorporation by ID
Gets one or more ClientCorporations by ID using Bullhorn `GET /entity/ClientCorporation/{entityId}` semantics.
Get JobOrder by ID
Gets one JobOrder by ID
get JobOrder Meta
get the job's settings
Search Bullhorn
Search for any record in bullhorn
Update Candidate
Updates an existing Candidate using Bullhorn `POST /entity/Candidate/{entityId}` semantics.
Bulk update Candidates (multi-entity semantics not modelled)
Bullhorn supports `POST /entity/{entityType}` for some advanced behaviours. This operation is modelled generically but typical updates should use `POST /entity/Candidate/{entityId}`.
Update ClientContact
Updates an existing ClientContact using Bullhorn `POST /entity/ClientContact/{entityId}` semantics.
Update ClientCorporation
Updates an existing ClientCorporation using Bullhorn `POST /entity/ClientCorporation/{entityId}` semantics.
Update JobOrder
Updates an existing JobOrder using Bullhorn `POST /entity/JobOrder/{entityId}` semantics.