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.

LiveContext

All integrations

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.

33 toolsBasic authAPI docs

Connect Greenhouse How integrations work

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

POSTadvance_application
Moves an application to the next stage in the hiring pipeline.
GETget_application
Retrieves detailed information about a specific application.
GETlist_applications
Lists all applications with filtering by job and status.
POSTmove_application
Moves an application to a specific stage within the same job.
POSTreject_application
Rejects an application with optional reason and notification.
POSTtransfer_application_to_job
Transfers an application to a different job.
POSTunreject_application
Unrejects a previously rejected application.

Candidate, 6 operations

POSTcreate_candidate
Creates a new candidate record with required application.
DELETEdelete_candidate
Permanently deletes a candidate record.
GETget_candidate
Retrieves detailed information about a specific candidate.
GETget_candidate_activity_feed
Retrieves a candidate's activity feed with notes, emails, and activities.
GETlist_candidates
Lists all candidates in the ATS with filtering options.
PATCHupdate_candidate
Updates a candidate's profile information.

Offer, 4 operations

GETget_current_offer_for_application
Retrieves the current active offer for a specific application.
GETget_offer
Retrieves detailed information about a specific offer.
GETlist_offers
Lists all job offers with status, date, and resolution filtering.
GETlist_offers_for_application
Lists all offers associated with a specific application.

Department, 2 operations

GETget_department
Retrieves detailed information about a specific department.
GETlist_departments
Lists all departments in the organization.

Interview, 2 operations

GETget_scheduled_interview
Retrieves detailed information about a specific scheduled interview.
GETlist_scheduled_interviews
Lists all scheduled interviews with date and time filtering.

Job, 2 operations

GETget_job
Retrieves detailed information about a specific job posting.
GETlist_jobs
Lists all job postings with filtering by status, department, and office.

Job stage, 2 operations

GETget_job_stages_for_job
Lists all interview stages for a specific job.
GETlist_job_stages
Lists all job stages across all jobs.

Office, 2 operations

GETget_office
Retrieves detailed information about a specific office.
GETlist_offices
Lists all offices in the organization.

Scorecard, 2 operations

GETget_scorecards_for_application
Retrieves all interview scorecards for a specific application.
GETlist_scorecards
Lists all interview scorecards with date filtering.

User, 2 operations

GETget_user
Retrieves detailed information about a specific Greenhouse user.
GETlist_users
Lists all Greenhouse users (recruiters, hiring managers, etc.).

Rejection reason, 1 operation

GETlist_rejection_reasons
Lists all configured rejection reasons.

Source, 1 operation

GETlist_sources
Lists 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

Create your workspace
Sign up free. Nothing to install.
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.
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.