Head to head · Recruiting candidates · October 2026 research run

Greenhouse vs Zoho Recruit

Greenhouse scores 64.8 (B) on agent readiness against Zoho Recruit's 59.8 (C), and leads in 4 of 7 scored categories. Zoho Recruit leads on reliability and payments & pricing. Both do recruiting candidates.

Which one, for what

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

  • Schema & documentation, 79 against 46
  • Security & auth, 85 against 65
  • Maintenance & community, 65 against 48

Also in its favour

  • A hosted endpoint, with nothing to install

Watch for

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

Zoho Recruit C

Good for Small businesses and staffing agencies on Zoho that want an agent to read and write candidates, job openings, applications and interviews with narrow scopes, and teams that want a free edition with API access.

Ahead on

  • Reliability, 76 against 71
  • Payments & pricing, 35 against 0

Also in its favour

  • Free to start without a card

Watch for

No OpenAPI description found. The public repository zoho/recruit-oas is empty

Score by category

CategoryWeight this runGreenhouseZoho RecruitEdge
Reliability16%207176Zoho Recruit +5
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.27946Greenhouse +33
Agent ergonomics13%16.26364Zoho Recruit +1
Security & auth14%17.58565Greenhouse +20
Payments & pricing10%12.5035Zoho Recruit +35
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.86548Greenhouse +17
Transparency & trust7%8.87977Greenhouse +2
Negative events≤1500
Total64.8 · B59.8 · C

Facts side by side

FactGreenhouseZoho Recruit
KindHTTP APIHTTP API
VendorGreenhouse Software, Inc.Zoho
Hosted endpointhttps://harvest.greenhouse.io/v3no (local only)
TransportsHTTPHTTP
AuthOAuthOAuth
PricingPaidFreemium
x402nono
LicenceProprietary service under Greenhouse's Master Subscription Agreement. The docs repository for the older APIs on GitHub is Apache-2.0Proprietary service under Zoho's Terms of Service
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-07none
Terms last updated2026-02-012022-03-02
Privacy policy last updated2026-05-282025-12-22
Customer content may train modelsyesyes
Terms restrict automated accessnot found in the textnot 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

Verdicts

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.

Zoho Recruit

OAuth scopes narrow to one module and one operation, the docs have an llms.txt index with a Markdown page per endpoint, and the Free edition includes 5,000 API credits a day. No OpenAPI description, official SDK, SLA or dated API changelog was found, and the documented token refresh puts the client secret in the URL.

Before you call either

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

Zoho Recruit

  1. Use the api_domain returned with the token, or the regional host (recruit.zoho.com, recruit.zoho.eu, recruit.zoho.in and others). Tokens from one data centre fail on another
  2. Send Authorization: Zoho-oauthtoken <token> and refresh hourly. Put refresh parameters in the POST body, not the URL
  3. Pass fields on list calls and page with page and per_page (200 at most) until more_records is false
  4. Create through /{module_api_name}/upsert with duplicate_check_fields so a retry updates instead of duplicating
  5. Move a candidate with PUT /{module_api_name}/status, not upsert. Pass trigger: [] on writes to skip workflows, approvals and blueprints

Questions

Which is better for AI agents, Greenhouse or Zoho Recruit?

Greenhouse scores 64.8 (B) on agent readiness against Zoho Recruit's 59.8 (C), and leads in 4 of 7 scored categories. Zoho Recruit leads on reliability and payments & pricing.

Do Greenhouse and Zoho Recruit need an API key?

Both use an OAuth sign-in.

Can an agent call Greenhouse and Zoho Recruit without installing anything?

Greenhouse has a hosted endpoint at https://harvest.greenhouse.io/v3. No hosted endpoint is listed for Zoho Recruit.

Other comparisons with Greenhouse or Zoho Recruit

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.