Stop building Greenhouse integrations from scratch. Bindbee gives you a single API to sync candidates, jobs, applications, interviews, offers, and scorecards—without the maintenance headaches.
Bindbee normalizes Greenhouse's data into unified ATS models. One integration, consistent data structure across Greenhouse and every other ATS your customers use.
Authenticate via Magic Link—our drop-in auth component. Your customer provides their Greenhouse API key, and Bindbee handles the rest.
We pull candidate, job, application, interview, offer, and scorecard data from Greenhouse and normalize it to unified ATS models with automatic incremental syncs.
One REST API for Greenhouse and 60+ other HR and ATS systems. Same endpoints, same data structure.
Customers authenticate effortlessly via Magic Link, with an embeddable SDK that enables seamless, in-app connections.
Most customers complete setup in under 10 minutes. Your end-user generates a Greenhouse Harvest API key, authenticates via Magic Link, and initial data sync begins immediately.
Yes. Enable include_custom_fields=true in your API requests. Custom fields appear in the custom_fields object with their original Greenhouse field names, including custom candidate fields, job fields, and application fields.
Yes. Bindbee supports write operations for Greenhouse including candidate creation, job creation (using Greenhouse templates), application creation, interview scheduling, scorecard submission, and offer creation. Use the /meta endpoint to discover the exact payload structure Greenhouse expects.
Bindbee syncs Candidates, Jobs, Applications, Scheduled Interviews, Scorecards, Offers, Job Interview Stages, Departments, Offices, Remote Users, Reject Reasons, Tags, and Attachments from Greenhouse.
Greenhouse has several APIs (Harvest, Ingestion, Job Board). Bindbee handles this complexity internally—you interact with one unified REST API regardless of which Greenhouse API is used under the hood.
Yes. Use query parameters like current_stage, source, candidate, job, credited_to, and reject_reason to filter application results. You can also use modified_after to get only recently updated records.
Bindbee syncs data periodically and provides its own webhook notifications when new data is available. You don't need to configure Greenhouse webhooks directly—Bindbee manages sync scheduling and notifies you of changes.
No problem. Bindbee's unified API returns consistent data regardless of which ATS your customer uses. If one customer runs Greenhouse and another runs Lever, your code stays the same.
No. Bindbee supports unlimited connectors. Each of your customers gets their own connector with isolated data and credentials.
Bindbee's unified model accepts a departments array for flexibility across ATS providers. For Greenhouse specifically, pass at most one department ID. Bindbee validates and translates this correctly.
