Get all open jobs from Greenhouse API
Technical guide on Greenhouse API to Get all open jobs from Greenhouse API
Knit's Greenhouse MCP Server gives your AI agents instant, code-free access to every Greenhouse API endpoint-read, write, and automate without OAuth headaches or custom endpoints.
Google for Startups AcceleratorAll the power of AI-ready tools — serverless hosting, mix-and-match APIs, live updates, semantic search, and built-in auth — in a single, plug-and-play platform.
Spin up MCP Servers with zero infrastructure — Knit scales, patches, and monitors everything for you.
Deploy only the API tools you need from any app in a single lightweight server — no bloat, no duplication.
Expose custom endpoints as AI-ready tools alongside Knit's catalog, unifying proprietary logic and third-party apps in one place.
Natural-language search surfaces the right tools for each use case, shrinking token costs and boosting LLM accuracy.
Add or remove tools without downtime; your agents see new capabilities instantly — no server restarts required.
OAuth, SAML, service accounts — Knit manages credentials and refreshes so your team never wrestles with tokens.
Watch an agent automate workflows — all with Knit's plug-and-play MCP Servers.
Every action below is real and already live — not a roadmap item. Browse the full API reference →
This API is used to reject an application for a job. It requires the application ID, job ID, candidate ID, rejection ID, and a note as input. The rejection ID should be obtained from the List Rejection Reasons API. The response indicates whether the operation was successful or not. If not successful, an error message is provided.
This API endpoint retrieves a list of global tags from various Applicant Tracking Systems (ATS) such as Greenhouse, Lever, Workday, SAP SuccessFactors, Ashby, Zoho Recruit, JazzHR ATS, and Recruitee. The request requires an 'accept' header specifying 'application/json'. The response includes a success flag and a data object containing an array of tags, each with an 'id' and 'text'. If the request fails, an error object with a message is returned.
This API endpoint allows adding a tag to a candidate in an ATS (Applicant Tracking System). The request requires the candidate ID, tag text, tag ID, application ID, and job ID. Tags can be added at the application level or candidate level depending on the ATS system. If the tag ID is not available, a dummy ID can be used. The response indicates whether the operation was successful or not.
This API retrieves a list of rejection reasons from various Applicant Tracking Systems (ATS) such as Greenhouse, Lever, SmartRecruiters, TeamTailor, Breezy, Ashby, Zoho Recruit, Recruitee, and Oracle Taleo. The request requires an 'accept' header specifying 'application/json'. The response includes a success flag and an array of rejection reasons, each with a unique 'id' and 'text' description. In case of an error, an error message is provided.
The Get Candidate Tags API retrieves tags associated with a candidate for a specific application and job. It requires three query parameters: candidateId, applicationId, and jobId, all of which are mandatory. The response includes a success flag and a data object containing an array of tags, each with an id and text. If the request fails, an error message is provided.
This API endpoint allows the creation of a note for a candidate. The note may be tied to an application or exist as a global note depending on the ATS (Applicant Tracking System) behavior. The request requires headers specifying 'accept' and 'content-type' as 'application/json'. The request body must include 'candidateId', 'applicationId', and 'note'. The response will indicate success or provide an error message if the operation fails. Supported ATS include Greenhouse, Lever, SAP SuccessFactors, Workable, TeamTailor, Bullhorn, Ashby, SmartRecruiters, Breezy, Zoho Recruit, BambooHR ATS, JazzHR ATS, Recruitee, Oracle Taleo, and Pinpoint.
The Update Application Stage API allows users to update the stage of an application for a candidate in various supported applications such as Greenhouse, Lever, Oracle Cloud HCM, and others. The API requires a POST request with headers specifying 'accept' and 'content-type' as 'application/json'. The request body must include 'applicationId', 'toStageId', 'currentStageId', 'candidateId', and 'jobId' as required fields, with an optional 'subStageId'. The response will indicate success or provide an error message and type if unsuccessful.
This API endpoint allows the creation of an application in an ATS (Applicant Tracking System). The request can either include a candidateId for an existing candidate or a candidate object with details such as firstName, lastName, emails, and phones. The jobId and initialStageId are required fields. The response includes the success status and the IDs of the created application, job, and candidate. If the request fails, an error message is provided.
This API endpoint allows users to add an attachment to an ATS application. The request requires headers specifying the content type and accept type as 'application/json'. The body of the request must include the applicationId, jobId, candidateId, fileName, and fileType. Optional fields include fileContent, fileUrl, and contentType. The response will indicate success and provide the ID and download URL of the uploaded attachment if successful. If unsuccessful, an error message and type will be provided.
Our AI Agent builds it instantly.
Try NowSee how teams put Greenhouse to work as part of a bigger workflow.
Sync application data back to ATS, optimize hiring funnel, and track applicant sources.
Publish jobs to multiple channels and track campaign performance with real-time ATS syncs.
Automate candidate background checks, document uploads and stage updates across ATS applications.
See how leading technology firms are scaling their operations
Amazing Product With Exceptional Support from the team. By using Knit we managed to speed up our development by orders of magnitude.
A brilliant tool to let you seamlessly integrate with many different systems. It is very easy to integrate with and customer support is next level.
Seamless integration experience. Well-documented, self-explanatory APIs, and excellent service and support.
Easy to integrate. Knit's dashboard is intuitive for setting up and testing integrations, and the sandbox is extremely useful during development.
Knit shipped a brand-new Timesheet API in a week and handed us a ready-to-use NetSuite sandbox. That velocity is priceless when you're running payroll in 40+ countries.
4.9 out of 5 stars on G2
Yes — the Greenhouse MCP Server is live and already built, not a roadmap item. It exposes Greenhouse's real actions as AI-ready tools your agent can call directly.
Yes. Its actions cover both reads and writes, so your agent can pull data from Greenhouse and push updates back to it, not just query it.
Knit manages Greenhouse's OAuth, credential storage, and refresh for you — there's no auth to configure yourself before your agent can start calling tools.
Knit absorbs it. We maintain and update the Greenhouse connector on our end, so the MCP Server keeps working without you tracking Greenhouse's changelog.
No. Knit acts as a stateless passthrough — data is processed on our application server and returned directly to your agent, without being stored on Knit's servers.
You choose the model that fits your business — pricing based on integrated accounts, or based on API call volume. Every plan includes a 30-day free trial before billing starts.
Yes — this MCP server exposes Greenhouse's actions as tools your AI agent can call directly, the same underlying capability previously offered as a standalone LLM Tool integration. MCP is the protocol; the tool-calling access is the same.
Yes — any MCP-compatible client or agent framework can connect to this server and call its exposed actions, regardless of which underlying LLM is driving the agent.
Technical guide on Greenhouse API to Get all open jobs from Greenhouse API
Technical guide on Greenhouse API to Get all candidates for a job from Greenhouse API
Learn about the common greenhouse API data models and API end points in this comprehensive greenhouse API directory