Head to head · Recruiting · October 2026 research run

Bullhorn vs Lever

Bullhorn and Lever score within a point of each other on agent readiness, 46.4 (D) and 45.5 (E). Lever leads on reliability and security & auth. Both do recruiting.

Best recruiting and applicant tracking systems for AI agents · All 106 recruiting comparisons

Which one, for what

Bullhorn D

Best for An integration built for a staffing agency that already runs on Bullhorn, with Bullhorn's permission for AI use in writing, and needs candidates, job orders, submissions and placements.

Ahead on

  • Schema & documentation, 47 against 22
  • Agent ergonomics, 64 against 48
  • Maintenance & community, 76 against 7

Watch for

The API Fair Use Policy of 17 December 2025 bars connecting third-party AI or LLM tools, or MCP, without Bullhorn's explicit written permission

Lever E

Best for An agent working inside a company that already runs Lever, for reading the pipeline, adding candidates, moving stages, writing notes and feedback and scheduling externally managed interviews.

Ahead on

  • Reliability, 85 against 50
  • Security & auth, 53 against 28

Watch for

No public price, free tier or self-serve signup. OAuth apps are registered with Lever and tested against a Lever Sandbox account

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Maintenance & community Bullhorn +69

Bullhorn 76

The REST API change log's newest entry is the June 2026 release (2026.6), dated to its month. Bullhorn's own packages are newer. @bullhorn/bullhorn-types v1.143.0 was tagged on 9 October 2026 (adds the WebResponse entity types), 27 days before this check (30). Five releases of the vendor's own libraries in the 90 days from 7 August, sdk-rest 2.6.3 (12 August, new entities), 2.7.0 (29 September, dependency versions, and the credentials object's text output now masks the password and client secret), 3.0.0 (29 September, Spring 7 and Java 17) and @bullhorn/bullhorn-types 1.142.0 (28 September) and v1.143.0 (9 October), all five in full (20). Closed service with a public change log, a developer ticket form and forums named in the guide. We could not read the help centre (6, the earlier partial, kept). Current official libraries in Java and TypeScript (15). @bullhorn/taurus 3.9.8 dates from 22 April 2026, and sdk-rest moved to Spring 7 and Java 17 in September (5). 30+20+6+15+5 = 76.

Lever 7

The newest dated API change was on the updates page at hire.lever.co, which now answers robots.txt with a redirect to its sign-in page, so the 7 October reading (30 April 2026) is struck. The other dated sources of Lever's own were looked for. lever/postings-api's last change is a README merge on 23 April 2026, 195 days before 4 November, and lever/integrator-resources' on 27 February 2025, neither tagged (0). No dated entry in the window from 6 August (0). Closed service with no changelog readable today. The Postings README sends requests to a help-centre ticket form or the repository's issues (4). No official SDK, and no Lever-published MCP server found (0). No packages to assess. The example repository has CodeQL and dependency review workflows and was last changed in February 2025 (3). 0 + 0 + 4 + 0 + 3 = 7.

Reliability Lever +35

Bullhorn 50

Read with the hosted rubric, for the REST API. Statuspage at status.bullhorn.com, read from its history page on 5 November 2026, with 94 components by product and cluster (Bullhorn ATS/CRM and its CLS clusters, a Sandbox component) and no REST API component (15, the reading for a vendor page with no component for the product). The history page covers 1 September to 5 November 2026. It lists 37 incidents across all products, 24 minor, six major, four critical and three with no impact. On Bullhorn ATS/CRM the one full outage was on 21 October, when users on every cluster could not log in from 1.35 pm to 6.10 pm ET, which we read as one major (10). The 1 September Greenshades integration fault and the 15 October Daxtra Search & Match fault touch one integration or function, so they count as minor. 7 to 31 August is not on the page and gets no credit of its own. No numeric rate limit is in the API reference. The partner FAQ gives an allowance of 200,000 calls a month, and the guide says login rates are strictly limited without a figure (5, the earlier partial, kept). The error table says to wait 1 second on 429 and retry until successful, which is backoff guidance alone. No idempotency keys or safe-retry guidance for writes was found (10). No SLA was found on the public site (0). The API is generally available at version 2.0 (10). 15+10+5+10+0+10 = 50.

Lever 85

Graded on the hosted lines for the Data API and the Postings API. Statuspage at status.lever.co lists Integration API & Webhooks, Hire, Career Site and Visual Insights for the global and EU data centres, plus partner, sandbox and third-party groups (20). From 6 August to 4 November 2026 its history feed records four incidents. Offer letter conversion failed on 7 August (offer letters only). A 15-minute outage on 12 August caused failed page loads on hire.lever.co. 500 errors on 21 August, posted against the Hire component, had a fix within 17 minutes. A server rotation caused 504s on page loads at hire.eulever.co for 45 minutes on 25 August. Each names one function, the web app or one region, so all read as minor (20). hire.lever.co, the developer documentation host, answers robots.txt with a redirect to its sign-in page, read as a refusal, so the 7 October readings from it are struck, among them the Data API's request limits and backoff guidance. The Postings API README (cloned) limits application POSTs to 2 a second, a documented limit with a number, though no Data API limit can be read (15). The same README documents the 429 and says to queue and retry every application POST that receives one, with no Retry-After header, backoff interval or idempotency key, which is retry guidance alone (10). The SLA, re-read, commits to 99.9% uptime for all customers with automatic service credits (10). The readable docs carry no beta or preview label, and the Postman collection and README use the production /v1 and /v0 paths (10). 20 + 20 + 15 + 10 + 10 + 10 = 85.

Schema & documentation Bullhorn +25

Bullhorn 47

No OpenAPI file or other machine-readable contract is shown or linked on the docs pages (0). /meta/{entityType} describes fields only to an authenticated caller of the API, and the TypeScript interfaces in @bullhorn/bullhorn-types are package source, so neither is a published contract. The docs are one HTML page built from Markdown sources in a public GitHub repository, and www.bullhorn.com/llms.txt is a product index that links to the developer site. No Markdown is served for agents (4). Each operation states its purpose with parameter tables, and the entity guide describes 91 entities field by field (12). Parameters are marked required or optional and entity fields carry types and lengths, but query and where are free-form Lucene and JPQL strings (9). Every operation has a curl example and a sample response. Errors are a table of ten status codes with no bodies (9). Login takes a version parameter, and a change log lists releases from 2024.5 to 2026.6 (13). 0+4+12+9+9+13 = 47.

Lever 22

hire.lever.co, the developer documentation host, answers robots.txt with a redirect to its sign-in page, read as a refusal, so the 7 October readings from it are struck. What remains is in Lever's GitHub repositories. No OpenAPI file found. The Postman collection in lever/integrator-resources is the only machine-readable description of the Data API, 81 requests in 24 groups, unchanged since 16 April 2021 (5, the earlier partial kept). No llms.txt, and www.lever.co/llms.txt returned 404 on 7 October (0). The Postings API README says what the API does and does not do, and when to send candidates to Lever's hosted form instead, while only 6 of the collection's 81 requests carry a description (6). The README's tables name parameters and mark the required ones without types, and the collection gives example bodies only (4). The README gives example calls and the success and error bodies, and the collection has no saved responses or error list (7). Versioned paths /v0 and /v1, but the dated updates page is struck and no other changelog was found, so the line isn't met (0). 5 + 0 + 6 + 4 + 7 + 0 = 22.

Security & auth Lever +25

Bullhorn 28

OAuth 2.0 authorisation code grant with a client ID and secret issued by Bullhorn, ten-minute access tokens and rotating refresh tokens, exchanged for a BhRestToken session. No scopes were found, so a session carries all the rights of the API user (20). The guide shows the username, password, client secret and access token as URL query parameters, and BhRestToken may be sent in the query string, which takes 10 off (10). Access follows the API user's entitlements per entity and action, readable at /entitlements. No read-only mode or confirmation step for deletes or /massUpdate was found (8). Candidate CVs and notes are untrusted text, and no guidance on handling them was found. The fair use policy requires written permission before any AI tool is connected, which is a contract term and not a mitigation (0). EntityEditHistory records field changes and events carry the user and transaction. No per-call API log for the operator was found (5). The GDPR commitment statement, re-read on 5 November 2026, reports annual SOC 1 Type 2 and SOC 2 Type 2 audits and says many services hold SOC 2 Type 2 or ISO 27001 without naming them. No report, security.txt, disclosure policy or bug bounty was found, and www.bullhorn.com/security describes only the Salesforce-based Talent Rover product. A SOC 2 claim with no report or disclosure route scores 5. 10+8+0+5+5 = 28.

Lever 53

hire.lever.co, the developer documentation host, answers robots.txt with a redirect to its sign-in page, read as a refusal, so the 7 October readings from it are struck, among them the scope list and the per-endpoint key settings. The example OAuth app in lever/integrator-resources runs the OAuth 2.0 authorisation code flow with requested scopes, and the Postman collection authenticates with an API key as the Basic auth username (30). The Postings API README documents its key in the key query parameter for application POSTs (-10). Scopes narrow what an OAuth app can reach, and the collection's nine DELETE requests show no confirmation step (8). Resumes, notes and application answers are written by outside parties and no prompt-injection guidance was found (3). The collection includes an Audit Events request and sends perform_as to attribute writes to a user (8). SOC 2 and ISO 27001 per the security page (re-read), and a vulnerability disclosure policy at security@employinc.com in SECURITY.md with no acknowledgement time. No bug bounty and no security.txt (14). 20 + 8 + 3 + 8 + 14 = 53.

Agent ergonomics Bullhorn +16

Bullhorn 64

Every read must name its fields, with nested sub-fields and a count per to-many association, and fields=* is blocked outside /meta (22). start and count paging with a default of 20 and a maximum of 500 (300 on some calls), Lucene search, JPQL where clauses and orderBy (20). Errors are status codes with one-line meanings, and the reference shows no error body to branch on (8). No idempotency keys. The only retry guidance is one second on 429, and the event queue can re-read a batch by lastRequestId (4). Official Java and TypeScript libraries exist, but a first call takes four requests (data centre lookup, authorisation code, token, REST login) and the base URL differs per customer (10). 22+20+8+4+10 = 64.

Lever 48

hire.lever.co, the developer documentation host, answers robots.txt with a redirect to its sign-in page, read as a refusal, so the 7 October readings from it are struck, among them field selection, expand and the Data API's pagination. The Postings API takes limit and mode, and nothing readable sizes Data API responses (5). Postings lists page with skip and limit and filter by location, commitment, team, department and level, with grouping (20). The README gives an HTTP status with a body of {ok:false, error:<string>}, with no list of codes. Kept as a partial (12). No idempotency keys. The README says candidates are merged by email address, which limits duplicate people on a retried application. Kept as a partial (5). Postings applications need only name and email, the Postman collection sends perform_as with a user id on writes, and there is no official SDK. Kept as a partial (6). 5 + 20 + 12 + 5 + 6 = 48.

Score by category

CategoryWeightBullhornLeverEdge
Reliability16%5085Lever +35
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%4722Bullhorn +25
Agent ergonomics13%6448Bullhorn +16
Security & auth14%2853Lever +25
Payments & pricing10%88even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%767Bullhorn +69
Transparency & trust7%6771Lever +4
Negative events≤1500
TotalD 46.4/100E 45.5/100

Facts side by side

FactBullhornLever
KindHTTP APIHTTP API
VendorBullhorn, Inc.Employ, Inc.
Hosted endpointhttps://rest.bullhornstaffing.com/rest-serviceshttps://api.lever.co/v1
TransportsHTTPHTTP
AuthOAuthOAuth or key
PricingPaidPaid
x402nono
LicenceProprietary service under a Bullhorn customer or partner agreement that is not published, with a public API Fair Use Policy. The sdk-rest Java library and the @bullhorn/taurus and @bullhorn/bullhorn-types packages are MIT per npm and the repositoriesProprietary service under Lever's terms of service. The postings-api and integrator-resources repositories on GitHub hold documentation and example code
Read-only variant documentednono
llms.txtnono
Last release2026-10-092026-04-30
Terms last updatedno date given2023-08-25
Privacy policy last updated2026-05-202023-09-25
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingyesyes
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textyes
Popularity13 starsnone
Agent reviews1.8/5 (4)none

How the scores have moved

Verdicts

Bullhorn

The REST API covers 91 documented entities with required field selection, Lucene and JPQL queries and an event queue. Access is by support ticket or a paid partner contract, and the API Fair Use Policy bars connecting third-party AI or LLM tools or MCP without Bullhorn's written permission. No OpenAPI file or numeric rate limit was found.

Lever

Lever's status page posts per-component incidents, and a published SLA commits to 99.9 per cent uptime with automatic credits. Its developer reference now sits behind a sign-in page, leaving a 2021 Postman collection and the Postings API README as the readable docs. Access needs a customer contract or partner approval, with no public price, OpenAPI file or official SDK.

Before you call either

Bullhorn

  1. Confirm the customer holds Bullhorn's written permission for AI or LLM access before any call. The API Fair Use Policy forbids it otherwise
  2. Call /rest-services/loginInfo?username= first to learn the data centre, then use the returned OAuth and REST URLs and follow any 307 redirect
  3. Log in once and reuse BhRestToken until a call returns 401, then use the refresh token. Bullhorn limits login rates and may block frequent logins
  4. Send BhRestToken as a header, never in the URL, and always pass fields. fields=* is blocked outside /meta
  5. On 429 wait one second and retry. Writes have no idempotency key, so read the record back before repeating a PUT

Lever

  1. Send perform_as with a Lever user id on writes, as Lever's Postman collection does for feedback, files, postings and requisitions
  2. Keep Postings application POSTs under 2 a second, and queue and retry any that receive 429, or send candidates to Lever's hosted form
  3. Page Postings API lists with skip and limit, and filter by location, commitment, team, department or level
  4. Send the Postings API key only from a server. It travels in the key query parameter and can land in logs

Questions

Which is better for AI agents, Bullhorn or Lever?

Bullhorn and Lever score within a point of each other on agent readiness, 46.4 (D) and 45.5 (E). Lever leads on reliability and security & auth.

Do Bullhorn and Lever need an API key?

Bullhorn uses an OAuth sign-in. Lever takes an API key or an OAuth sign-in.

Can an agent call Bullhorn and Lever without installing anything?

Yes. Bullhorn has a hosted endpoint at https://rest.bullhornstaffing.com/rest-services and Lever at https://api.lever.co/v1.

Other comparisons with Bullhorn or Lever

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.