Get an audit

Head to head · Recruiting candidates · October 2026 research run

Bullhorn vs Lever

Lever scores 53.6 (D) on agent readiness against Bullhorn's 46.7 (D), and leads in 4 of 7 scored categories. Bullhorn leads on maintenance & community. Both do recruiting candidates.

BullhornBullhorn, Inc. · HTTP API D46.7/100#644 of 722 LeverEmploy, Inc. · HTTP API D53.6/100#541 of 722

Which one, for what

Bullhorn D

Good 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

  • Maintenance & community, 56 against 21

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 D

Good 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, 73 against 53
  • Security & auth, 60 against 31
  • Transparency & trust, 75 against 67

Watch for

No public price, free tier or self-serve signup. OAuth apps and sandbox accounts are issued by Lever staff after a partner application

Score by category

CategoryWeight this runBullhornLeverEdge
Reliability16%205373Lever +20
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.25555even
Agent ergonomics13%16.26465Lever +1
Security & auth14%17.53160Lever +29
Payments & pricing10%12.555even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.85621Bullhorn +35
Transparency & trust7%8.86775Lever +8
Negative events≤1500
Total46.7 · D53.6 · D

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-09-292026-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 stars, 1.7k npm/wknone

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

The Data API covers about 100 operations with read and write OAuth scopes per resource, field selection and a 99.9 per cent uptime commitment. Access depends on a paying customer or partner approval, with no public price, no OpenAPI file and no official SDK. The status page records three critical incidents between 14 July and 21 August 2026.

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 creates and most updates. Opportunity, note, feedback, panel and interview writes reject requests without it
  2. Use the Opportunities endpoints. The Candidates endpoints were deprecated in 2020 and the old candidate id works as the opportunity id
  3. Stay under 10 requests a second per key and back off exponentially on 429 and 503. Application POSTs are limited to 2 a second
  4. Create interviews on a panel with externallyManaged true. Panels made in the Lever app can't be changed through the API
  5. Pass include to trim fields and follow next while hasNext is true. An offset must come from a previous response
  6. Send a full object on PUT to panels and interviews. Missing fields are deleted

Questions

Which is better for AI agents, Bullhorn or Lever?

Lever scores 53.6 (D) on agent readiness against Bullhorn's 46.7 (D), and leads in 4 of 7 scored categories. Bullhorn leads on maintenance & community.

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.

Get an auditSee a sample report