Integration

Greenhouse integration

Applicant tracking system (ATS) and recruiting API. Manage job postings, candidates, applications, interviews, and hiring workflows. Essential for HR tech integrations, recruiting automation, and talent acquisition systems.

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Greenhouse.Built from the 33 Greenhouse tools below, on the connection you add once.

Common Greenhouse use cases

  • pipeline view
  • application review
  • user lookup
  • org structure
  • candidate review
  • offer approval
  • hiring decision
  • candidate evaluation
  • job board
  • job display

What you can do with Greenhouse

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Application, 7 operations

  • advance_applicationAdvance applicationPOSTMoves an application to the next stage in the hiring pipeline.
  • get_applicationGet applicationGETRetrieves detailed information about a specific application.
  • list_applicationsList applicationsGETLists all applications with filtering by job and status.
  • move_applicationMove applicationPOSTMoves an application to a specific stage within the same job.
  • reject_applicationReject applicationPOSTRejects an application with optional reason and notification.
  • transfer_application_to_jobTransfer application to jobPOSTTransfers an application to a different job.
  • unreject_applicationUnreject applicationPOSTUnrejects a previously rejected application.

Candidate, 6 operations

  • create_candidateCreate candidatePOSTCreates a new candidate record with required application.
  • delete_candidateDelete candidateDELETEPermanently deletes a candidate record.
  • get_candidateGet candidateGETRetrieves detailed information about a specific candidate.
  • get_candidate_activity_feedGet candidate activity feedGETRetrieves a candidate's activity feed with notes, emails, and activities.
  • list_candidatesList candidatesGETLists all candidates in the ATS with filtering options.
  • update_candidateUpdate candidatePATCHUpdates a candidate's profile information.

Offer, 4 operations

  • get_current_offer_for_applicationGet current offer for applicationGETRetrieves the current active offer for a specific application.
  • get_offerGet offerGETRetrieves detailed information about a specific offer.
  • list_offersList offersGETLists all job offers with status, date, and resolution filtering.
  • list_offers_for_applicationList offers for applicationGETLists all offers associated with a specific application.

Department, 2 operations

  • get_departmentGet departmentGETRetrieves detailed information about a specific department.
  • list_departmentsList departmentsGETLists all departments in the organization.

Interview, 2 operations

  • get_scheduled_interviewGet scheduled interviewGETRetrieves detailed information about a specific scheduled interview.
  • list_scheduled_interviewsList scheduled interviewsGETLists all scheduled interviews with date and time filtering.

Job, 2 operations

  • get_jobGet jobGETRetrieves detailed information about a specific job posting.
  • list_jobsList jobsGETLists all job postings with filtering by status, department, and office.

Job stage, 2 operations

  • get_job_stages_for_jobGet job stages for jobGETLists all interview stages for a specific job.
  • list_job_stagesList job stagesGETLists all job stages across all jobs.

Office, 2 operations

  • get_officeGet officeGETRetrieves detailed information about a specific office.
  • list_officesList officesGETLists all offices in the organization.

Scorecard, 2 operations

  • get_scorecards_for_applicationGet scorecards for applicationGETRetrieves all interview scorecards for a specific application.
  • list_scorecardsList scorecardsGETLists all interview scorecards with date filtering.

User, 2 operations

  • get_userGet userGETRetrieves detailed information about a specific Greenhouse user.
  • list_usersList usersGETLists all Greenhouse users (recruiters, hiring managers, etc.).

Rejection reason, 1 operation

  • list_rejection_reasonsList rejection reasonsGETLists all configured rejection reasons.

Source, 1 operation

  • list_sourcesList sourcesGETLists all candidate sources (job boards, referrals, etc.).

Greenhouse API rate limits

Rate limits vary by endpoint and plan. Limits are per 10 seconds as indicated by X-RateLimit-Limit response header.

These are the limits Greenhouse documents, not ones LiveContext measured. They can change and often depend on your plan, so check the Greenhouse documentation for current values.

Use Greenhouse from Claude Code, Cursor or Codex

Connect Greenhouse in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Greenhouse operations become tools the client can call, next to every other integration you connected.

Claude Code
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"
Codex (~/.codex/config.toml)
[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"
Cursor, Claude Desktop and other JSON configs
{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Greenhouse

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect Greenhouse once

    Add your Greenhouse connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.

  3. Describe the job in chat

    The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Greenhouse integration FAQ

What can you do with the Greenhouse integration?

LiveContext exposes 33 operations on Greenhouse, covering application, candidate, offer and department. Common uses include pipeline view, application review and user lookup.

What are the Greenhouse API rate limits?

Rate limits vary by endpoint and plan. Limits are per 10 seconds as indicated by X-RateLimit-Limit response header. Limits are set by Greenhouse and can depend on your plan.

Popular integrations

Browse the whole catalog