• Automations
  • Agents
  • Topics
  • Quake Core
  • Pricing
Book Demo
Integration iconClient Attraction Integration iconCandidate Marketing Integration iconShadow AI Integration iconThe Engine Integration iconHybrid Agents Integration iconRecruitment IPaaS
  • Home
  • Quake Core
  • Automations
  • Agents
  • Pricing

Topics

  • Client Attraction
  • Candidate Marketing
  • Shadow AI
  • Quake Core
  • Hybrid Agents
  • IPaaS
  • Privacy Policy
  • Terms & Conditions
  • DPA
  • Security Overview
  • API Docs

Bullhorn

The backbone of your agency. Quake Agents like "The Matchmaker" and "The Broadcaster" live inside Bullhorn, reading and writing data in real-time to ensure your Single Source of Truth is always accurate, compliant, and making money.

Bullhorn


get__candidates

Empowers "The Resourcer" agent to instantly mine your existing database for hidden gold. Instead of wasting budget on external job boards, this action identifies high-quality candidates you already own who match current live roles, significantly increasing your Return on Data.


get__jobs

Gives your Digital Workforce full visibility into your active revenue pipeline. By retrieving all open Job Orders, "The Matchmaker" agent can prioritize high-fee, urgent roles and instantly route the best incoming talent to the jobs that matter most to your bottom line.


post__candidates

Automates the onboarding of new talent. Whether a candidate applies at 3 AM via your website or is sourced from LinkedIn, "The Admin" agent uses this action to create a pristine, standardized Candidate record in Bullhorn instantly, freeing your consultants from hours of manual data entry.


post__jobs

Allows your agents to instantly log new revenue opportunities. If "The Business Developer" agent spots a hiring signal on the market, it can speculatively create a Job Order in Bullhorn, ready for a consultant to call and convert, ensuring you never miss a lead.


post__oauth_token

Security token refresh. Handles the complex OAuth 2.0 handshakes in the background, ensuring your agents maintain a secure, encrypted tunnel into Bullhorn 24/7 without ever timing out.


createCandidate
Creates a new Candidate using Bullhorn `PUT /entity/Candidate` semantics.

Advanced candidate creation for complex compliance scenarios. This ensures that when "The Screener" captures sensitive data like Right to Work or Security Clearance, it is mapped precisely to the correct fields in Bullhorn, ensuring your database remains audit-ready from Day 1.


createClientContact
Creates a new ClientContact using Bullhorn `PUT /entity/ClientContact` semantics.

The engine room of strategic Business Development. When a candidate you placed lands a senior role, this action allows "The Broker" agent to automatically flip them from a "Candidate" to a "Client Contact," instantly creating a new hiring manager lead for your sales team.


createClientCorporation
Creates a new ClientCorporation (company) using Bullhorn `PUT /entity/ClientCorporation` semantics.

Maps the market automatically. When your agents detect a new company hiring in your sector, they use this action to create the Client Corporation record in Bullhorn, building a target list of prospective clients while your consultants sleep.


createJobOrder
Creates a new JobOrder using Bullhorn `PUT /entity/JobOrder` semantics.

Allows your agents to instantly log new revenue opportunities. If "The Broker" agent spots a hiring signal on the market, it can speculatively create a Job Order in Bullhorn, ready for a consultant to call and convert, ensuring you never miss a lead.


deleteCandidate
Hard or soft deletes a Candidate using Bullhorn `DELETE /entity/Candidate/{entityId}`. Behaviour depends on entity configuration.

The nuclear option for "The Cleaner" agent. Used strictly for GDPR "Right to be Forgotten" requests, this action permanently removes candidate data upon request, ensuring your agency remains legally compliant and immune to fines without human intervention.


deleteClientContact
Hard or soft deletes a ClientContact using Bullhorn `DELETE /entity/ClientContact/{entityId}`. Behaviour depends on entity configuration.

Keeps your CRM lean and efficient. "The Cleaner" uses this to purge duplicate or obsolete Client Contact records, ensuring your marketing team isn't wasting budget emailing ghosts or people who left the industry 5 years ago.


deleteClientCorporation
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.

Standard Bullhorn API interaction enabling Quake agents to read or write data with enterprise-grade security.


deleteJobOrder
Hard or soft deletes a JobOrder using Bullhorn `DELETE /entity/JobOrder/{entityId}`. Behaviour depends on entity configuration.

Keeps your system clean. "The Cleaner" uses this action to automatically remove duplicate or cancelled job orders, ensuring your "Open Jobs" report reflects reality, not history.


entity_options

Context awareness. This allows your agents to "read" your bespoke picklists (e.g., custom Skills or Industries) so they can categorize candidates using your specific business language, not just generic terms.


get_countries
Pull the list of Countries supported in Bullhorn

Standard Bullhorn API interaction enabling Quake agents to read or write data with enterprise-grade security.


get_settings

Standard Bullhorn API interaction enabling Quake agents to read or write data with enterprise-grade security.


get_states_text
retrieve BH address States from the api

Standard Bullhorn API interaction enabling Quake agents to read or write data with enterprise-grade security.


getCandidate
Gets one or more Candidates by ID using Bullhorn `GET /entity/Candidate/{entityId}` semantics.

Provides your agents with a 360-degree view of a specific candidate. It retrieves not just the CV, but the entire history of the relationship. This allows "The Success Partner" to personalize outreach based on previous notes, placements, and interactions, ensuring every automated touchpoint feels deeply human.


getClientContact
Gets one or more ClientContacts by ID using Bullhorn `GET /entity/ClientContact/{entityId}` semantics.

Standard Bullhorn API interaction enabling Quake agents to read or write data with enterprise-grade security.


getClientCorporation
Gets one or more ClientCorporations by ID using Bullhorn `GET /entity/ClientCorporation/{entityId}` semantics.

Retrieves deep intelligence on your clients. Before a consultant makes a sales call, the agent pulls the full history of the Client Corporation—previous fees, active jobs, and key decision-makers—arming your team with the data they need to win the pitch.


getJobOrder
Gets one JobOrder by ID

Extracts the DNA of a specific vacancy. Your agents read the full job description, salary banding, and client requirements to ensure that "The Screener" voice agent asks the right qualifying questions. This guarantees that only 100% relevant candidates are ever presented to your consultants.


job_meta
get the job's settings

Understanding the rules of engagement. This action allows agents to read the custom fields and mandatory requirements of your specific Bullhorn configuration, ensuring that no job is ever processed with missing compliance data.


search
Search for any record in bullhorn

The brain of your search strategy. This allows agents to perform complex, multi-layered queries across your entire Bullhorn ecosystem. It enables "The Resourcer" to find the needle in the haystack—such as "Java Developers in London with SC Clearance who we haven't spoken to in 6 months"—re-engaging talent that your competitors missed.


updateCandidate
Updates an existing Candidate using Bullhorn `POST /entity/Candidate/{entityId}` semantics.

Keeps your database living and breathing. This action allows "The Success Partner" and "The Screener" to write back real-time updates—such as "Interview Booked," "Not Interested," or "Left Voicemail"—directly to the candidate record. This ensures your human team always has a real-time "Single Source of Truth" without ever manually updating a status.


updateCandidateWithoutIdInPath
Bullhorn supports `POST /entity/{entityType}` for some advanced behaviours. This operation is modelled generically but typical updates should use `POST /entity/Candidate/{entityId}`.

Standard Bullhorn API interaction enabling Quake agents to read or write data with enterprise-grade security.


updateClientContact
Updates an existing ClientContact using Bullhorn `POST /entity/ClientContact/{entityId}` semantics.

Maintains data hygiene. When "The Broker" detects a contact has been promoted or changed numbers, it automatically updates their record, ensuring your team is always dialing the right number.


updateClientCorporation
Updates an existing ClientCorporation using Bullhorn `POST /entity/ClientCorporation/{entityId}` semantics.

Standard Bullhorn API interaction enabling Quake agents to read or write data with enterprise-grade security.


updateJobOrder
Updates an existing JobOrder using Bullhorn `POST /entity/JobOrder/{entityId}` semantics.

Automates pipeline progression. As candidates move through the interview stages, your agents automatically update the Job Order status, ensuring your forecasting reports are 100% accurate without consultants having to spend Friday afternoon "cleaning up their pipeline".


  • Linkedin
  • X icon
  • Youtube icon

Privacy Policy Terms and Conditions DPA Security Overview API Docs Login

2026 Quake. All rights reserved.