Head to head · Recruiting candidates · October 2026 research run

Bullhorn vs Greenhouse

Greenhouse scores 64.8 (B) on agent readiness against Bullhorn's 46.7 (D), and leads in 5 of 7 scored categories. Bullhorn leads on payments & pricing. Both do recruiting candidates.

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

  • Payments & pricing, 5 against 0

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

Greenhouse B

Good for An agent working inside a company that already runs hiring on Greenhouse and needs to read pipelines, move applications, schedule interviews or draft offer records under scoped OAuth.

Ahead on

  • Reliability, 71 against 53
  • Schema & documentation, 79 against 55
  • Security & auth, 85 against 31
  • Maintenance & community, 65 against 56
  • Transparency & trust, 79 against 67

Watch for

No public price, free tier or trial. Pricing is customised through sales, and the sandbox is a Pro-tier feature

Score by category

CategoryWeight this runBullhornGreenhouseEdge
Reliability16%205371Greenhouse +18
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.25579Greenhouse +24
Agent ergonomics13%16.26463Bullhorn +1
Security & auth14%17.53185Greenhouse +54
Payments & pricing10%12.550Bullhorn +5
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.85665Greenhouse +9
Transparency & trust7%8.86779Greenhouse +12
Negative events≤1500
Total46.7 · D64.8 · B

Facts side by side

FactBullhornGreenhouse
KindHTTP APIHTTP API
VendorBullhorn, Inc.Greenhouse Software, Inc.
Hosted endpointhttps://rest.bullhornstaffing.com/rest-serviceshttps://harvest.greenhouse.io/v3
TransportsHTTPHTTP
AuthOAuthOAuth
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 Greenhouse's Master Subscription Agreement. The docs repository for the older APIs on GitHub is Apache-2.0
Read-only variant documentednono
llms.txtnoyes
Last release2026-09-292026-10-07
Terms last updatedno date given2026-02-01
Privacy policy last updated2026-05-202026-05-28
Customer content may train modelsnot found in the textyes
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 textnot found in the text
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.

Greenhouse

Harvest v3 pairs per-endpoint OAuth scopes with Markdown docs that embed an OpenAPI 3.1 definition for each call, and the beta MCP server blocks every DELETE. Access needs a paying customer account, with no public price, trial or self-serve sandbox, and no numeric rate limit or idempotency key was found in the reviewed documentation.

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

Greenhouse

  1. Request a token from https://auth.greenhouse.io/token with client credentials, then send it as a Bearer token to https://harvest.greenhouse.io/v3. Tokens expire, so repeat on 401
  2. Put filters and per_page on the first list request only. A cursor must be the only query parameter, or the call returns 422
  3. Send the current stage as from_stage_id when moving an application. It guards against stale moves. Other writes have no idempotency key, so check before retrying
  4. Read X-RateLimit-Remaining on every response and wait for Retry-After on 429. The window is 30 seconds
  5. Expect empty list results or 403 unless the token's user is a Site Admin with the needed permissions

Questions

Which is better for AI agents, Bullhorn or Greenhouse?

Greenhouse scores 64.8 (B) on agent readiness against Bullhorn's 46.7 (D), and leads in 5 of 7 scored categories. Bullhorn leads on payments & pricing.

Do Bullhorn and Greenhouse need an API key?

Both use an OAuth sign-in.

Can an agent call Bullhorn and Greenhouse without installing anything?

Yes. Bullhorn has a hosted endpoint at https://rest.bullhornstaffing.com/rest-services and Greenhouse at https://harvest.greenhouse.io/v3.

Other comparisons with Bullhorn or Greenhouse

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.