Greenhouse

At a Glance

Difficulty

⚠️INVOLVEDPartnership Required + Harvest V3 Integration Review

Authentication

OAuth 2.0OAuth 2.0 Authorization Code Grant against Harvest V3.

Webhooks

Virtual webhooks — Apideck polls Greenhouse and emits ats.applicant.created, ats.applicant.updated, ats.job.created, and ats.job.updated.

Partnership Required

Yes(Required — apply through the Greenhouse Integration Partner Program. There is no self-service developer signup.)

Partnership Application

Greenhouse Integration Partner Program↗

Apideck Credentials

Not available(Not available — Greenhouse requires each integration to run on its own Greenhouse-issued partner credentials, entered once in the Apideck Dashboard.)

Costs

Quote-based — three plans (Core, Plus, and Pro) priced by hiring volume and organizational complexity, with no public price list. No free trial is offered.

Sandbox Availability

Available(Sandbox and demo organizations are granted during partner onboarding; no self-service developer sandbox. Greenhouse accounts include one on Pro plans only.)

Account Type Required

An active Greenhouse account with a Harvest V3 partner integration provisioned.

Consumer Access Level

Site Admin (or a Site-Admin service account) — Harvest V3 list endpoints return 403 for any other user; the connection runs with that user's permissions.

Rate Limits

Fixed 30-second window; no published ceiling — the X-RateLimit-* response headers are authoritative. Exceeding it returns HTTP 429 with Retry-After.

Responsibility matrix

Environments

Testing

Greenhouse issues testing credentials that authorize only sandbox organizations you control. Every create and update the connection makes is a real write to whichever organization authorized it, visible to that organization's recruiters.

Production

Production Client ID and Secret are issued separately by Greenhouse and are the only credentials that authorize a live customer organization. Testing credentials CANNOT be used with production Greenhouse organizations — moving between environments means the application owner swaps the credentials in the Apideck Dashboard, not consumers in Vault.